emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Re: Other details about completion.


From: Juri Linkov
Subject: Re: [PATCH] Re: Other details about completion.
Date: Wed, 06 Apr 2022 19:43:44 +0300
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu)

>> 1) I think it is more intuitive to invert and use the M-S-<arrow>
>> minibuffer-choose-** and M-<arrow> for
>> minibuffer-{previous|next}-completion for not insert commands...
>
> I was a bit surprised at how M-<down> worked -- I had expected it to
> work like M-S-<down> works, really.  But after using it a few times, I
> think it the M-<down> action makes more ergonomic sense, so I'd rather
> keep it the way Juri has it now.

I'm still unsure which is better.  Maybe M-<down> should not be different
from M-<PgDown>?  One of them navigates by lines, and another by screenfuls.
But M-<down> inserts the current completion to the minibuffer,
whereas M-<PgDown> does not.  Or maybe M-<PgDown> should insert the
completion as well.

>> 2) The M-<up>/M-<down> is not intuitive when completions are not in
>> one-column format, and the M-<left>/M-<right> cannot be used because
>> they are already taken..
>
> I agree with that -- I expected M-<down> to work on the visually
> displayed completions, not the logical order.

Unfortunately, M-<left>/M-<right> can't be used for visual navigation
from the minibuffer.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]