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
thanks for a great project, I switched recently to the -rs variant as it's so much faster to start compared to the original autojump. I'm a bash user (old habits die hard) and it seems like the autocompletion capabilites of autojump-rs are not working for some reason. I.e. independent of what gets passed to autojump --complete, I always get the same list of 9 responses, which is wrong:
# I could run this as many times as I want, or pass any arbitrary
$ autojump --complete $$
__1__/home/milian/projects/kdab/foo/build-asan
__2__/home/milian/projects/kdab/foo
__3__/home/milian/projects/kdab/foo/build-profile
__4__/home/milian/projects/kf5/src/extragear/kdevelop/kdevelop
__5__/home/milian/projects/src/heaptrack
__6__/home/milian/projects/kdab/rnd/hotspot/build
__7__/home/milian/projects/kdab/foo/testdata
__8__/tmp
__9__/home/milian/projects/kdab/rnd/hotspot
so here already I would expect the result set to take the arg passed to --complete into account and filter by that?
then, when I use the builtin bash completion to actually trigger it, the __N__ prefixes actually make this totally unusable, as I always end up with
$ j something<TAB>
$ j __
here, bash decides to pick the common prefix, __ and enters that, without showing me anything else 🤷
Is this a setup issue on my end? I'm using the 0.5.1-2 package from AUR, if that matters.
Cheers
The text was updated successfully, but these errors were encountered:
hey there,
thanks for a great project, I switched recently to the -rs variant as it's so much faster to start compared to the original
autojump
. I'm a bash user (old habits die hard) and it seems like the autocompletion capabilites ofautojump-rs
are not working for some reason. I.e. independent of what gets passed toautojump --complete
, I always get the same list of 9 responses, which is wrong:so here already I would expect the result set to take the arg passed to
--complete
into account and filter by that?then, when I use the builtin bash completion to actually trigger it, the
__N__
prefixes actually make this totally unusable, as I always end up withhere, bash decides to pick the common prefix,
__
and enters that, without showing me anything else 🤷Is this a setup issue on my end? I'm using the 0.5.1-2 package from AUR, if that matters.
Cheers
The text was updated successfully, but these errors were encountered: