I tend to like it, too (though I can’t tell if that’s just because it’s what I first used and now I just expect it to work that way, now…).
Do you know if there’s a way to go backwards through available options, though? I forget what shift+tab does but its not the inverse of tab and having to cycle all the way through to come back around on a particularly large list of options sure is tedious.
I think that’s just about my only complaint with the default.
Not quite (though I hadn’t realized, before this thread, that such an option existed); I was more thinking of tabbing in the opposite direction for minibuffer-complete.
I sort of lay out everything in the comment at https://midwest.social/comment/24082938 but the short of it is that I realized that minibuffer-completedoes have functionality already built it: it just doesn’t seem to work when trying to to autocompletion in Eval:. So I didn’t realize that it’d work in circumstances like M-x.
Thanks so much for the suggestion, though! 'Appreciate the help.
This only works when the completion buffer is selected though (e.g. via completion-auto-select). I’m not really sure how to get useful backtab behavior in the minibuffer itself.
Edit – These bindings might be worth trying as well if you don’t like the auto selection:
So it’s possible I just never noticed the message noting minibuffer-next/previous-completion but those are pretty cool.
But I think I was more thinking of tabbing in the opposite direction for minibuffer-complete; the situation I’m most often finding myself with such an abundance of options is when I’m exploring available functions and just looking; I rarely want to go one-by-one in such a scenario.
…but what I just discovered is that functionality is already provided (I was confused when I saw that “backtab” was already assigned in minibuffer-local-completion-map); it just doesn’t seem to be there when auto-completing in Eval: (which just responds with “<backtab> is undefined”); which is how I’m most often looking at other available functions. That must be why I thought it never worked.
Welp, I appreciate the info., regardless; I definitely learned a bit more than I knew before. And it’s good to know backtab will actually work in M-x, if I ever find I need it.
I tend to like it, too (though I can’t tell if that’s just because it’s what I first used and now I just expect it to work that way, now…).
Do you know if there’s a way to go backwards through available options, though? I forget what
shift+tabdoes but its not the inverse oftaband having to cycle all the way through to come back around on a particularly large list of options sure is tedious.I think that’s just about my only complaint with the default.
Maybe M-p?
Not quite (though I hadn’t realized, before this thread, that such an option existed); I was more thinking of tabbing in the opposite direction for
minibuffer-complete.I sort of lay out everything in the comment at https://midwest.social/comment/24082938 but the short of it is that I realized that
minibuffer-completedoes have functionality already built it: it just doesn’t seem to work when trying to to autocompletion inEval:. So I didn’t realize that it’d work in circumstances likeM-x.Thanks so much for the suggestion, though! 'Appreciate the help.
Shift-Tab just does the correct thing for me on Emacs 30.2. That might be a newer default though.
I think on an older version something like this should do it:
This only works when the completion buffer is selected though (e.g. via
completion-auto-select). I’m not really sure how to get useful backtab behavior in the minibuffer itself.Edit – These bindings might be worth trying as well if you don’t like the auto selection:
So it’s possible I just never noticed the message noting
minibuffer-next/previous-completionbut those are pretty cool.But I think I was more thinking of tabbing in the opposite direction for
minibuffer-complete; the situation I’m most often finding myself with such an abundance of options is when I’m exploring available functions and just looking; I rarely want to go one-by-one in such a scenario.…but what I just discovered is that functionality is already provided (I was confused when I saw that “backtab” was already assigned in
minibuffer-local-completion-map); it just doesn’t seem to be there when auto-completing inEval:(which just responds with “<backtab> is undefined”); which is how I’m most often looking at other available functions. That must be why I thought it never worked.Welp, I appreciate the info., regardless; I definitely learned a bit more than I knew before. And it’s good to know backtab will actually work in
M-x, if I ever find I need it.