You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know it's impractical to handle all shell expansions, but it would be nice if numberwang recognized ~.
This came up recently when a file I piped to numberwang included the text ~/.ssh/known_hosts and numberwang came back with ~{/.}ssh/known_hosts, which wasn't the expected result at all. Similarly, if both the current directory and the home directory contain a file named foo.txt and the input to numberwang includes the test ~/foo.txt, numberwang will return ~/{foo.txt}. Here's a test case:
Like I said, I think it's impractical to support cases other than ~/foo. As far as I know sh, bash, zsh, csh and fish all work the same for this case. I'm not sure who that leaves (0.01%?), but you could supply an option to disable the behavior for those users.
Quoting is a more interesting problem and I'm not sure what the ideal behavior is there.
I know it's impractical to handle all shell expansions, but it would be nice if numberwang recognized
~
.This came up recently when a file I piped to numberwang included the text
~/.ssh/known_hosts
and numberwang came back with~{/.}ssh/known_hosts
, which wasn't the expected result at all. Similarly, if both the current directory and the home directory contain a file namedfoo.txt
and the input to numberwang includes the test~/foo.txt
, numberwang will return~/{foo.txt}
. Here's a test case:The output I would prefer would be:
Perhaps there could be an option to turn this behavior on or off?
The text was updated successfully, but these errors were encountered: