Darren Schroeder
Darren Schroeder
Thanks. It seems like it might be a performance impact to check every file for +s +h before deciding to show it in the completion menu. I wouldn't be in...
How would it be "free"? I thought that it would depend on whether we're pulling the metadata for each completion item. I don't see fs::MetadataExt being used really anywhere except...
Looks like we are pulling symlink_metadata() in completions, maybe it has file attributes? https://github.com/nushell/nushell/blob/222c30764859a5c78c11c233ae1c1521356c026b/crates/nu-cli/src/completions/completion_common.rs#L291 Regardless, I'm not sure filtering out +h +s files is worthwhile. If we did, we'd have...
I delete those desktop.ini files all the time and they're +h +s, but i get what you mean. I'm not in favor of this change but maybe others will be?
Sounds like a regression. We move things around a lot. I'm guessing someone refactored and didn't try running banner in config.nu.
it doesn't seem to be multi line but rather when the line wraps at the edge of the screen, right?
right, once it wraps at the screen edge, the entire line is duplicated for every character. i agree it's broken but it's not like you have text on multiple lines...
input isn't meant to capture multi-line text, so if that's what you want, i don't think it's built into it. what i'm saying is that the text wrapping shouldn't create...
I'm not sure. It could be in nushell or reedline or something in the input command.