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
As per the docs, there are four cases where fish understands commandline as path without explicit use of cd:
cases
file completion in fifc
1. starting with .
❌ display fish completions but doesn't trigger find/fd
2. starting with /
✅
3. starting with ~
❌ ~/* works but not ~*
4. ending with /
✅
While 3 is a bug, 1 follows the same logic as other completion rules:
If not all item from fish completion output doesn't belong to any particuluar group (path, process ids, commands etc) we use fish completion instead of a custom command to feed fzf.
So when tabbing on .config fifc won't trigger find/fd completion as fish doesn't path-complete.
The text was updated successfully, but these errors were encountered:
gazorby
changed the title
This fix accounts for 99% use cases, but it doesn't completely fix the problem, for example ~root won't work.
Improve path expansion
Aug 15, 2022
The current fix accounts for 99% use cases, but it doesn't completely fix the problem, for example
~root
won't work.See comment by @kidonng in #16 (comment)_
As per the docs, there are four cases where fish understands commandline as path without explicit use of
cd
:.
/
~
~/*
works but not~*
/
While 3 is a bug, 1 follows the same logic as other completion rules:
If not all item from fish completion output doesn't belong to any particuluar group (path, process ids, commands etc) we use fish completion instead of a custom command to feed fzf.
So when tabbing on
.config
fifc won't trigger find/fd completion as fish doesn't path-complete.The text was updated successfully, but these errors were encountered: