From: Gregory Heytings via "Emacs development discussions." <emacs-devel@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: A solution to display completion candidates after point in a minibuffer
Date: Fri, 02 Oct 2020 21:30:15 +0000 [thread overview]
Message-ID: <alpine.NEB.2.22.394.2010022139090453.14968@sdf.lonestar.org> (raw)
In-Reply-To: <jwvv9fsea10.fsf-monnier+emacs@gnu.org>
Hi Stefan,
Thanks again for your comments.
>
> Thanks. Indeed, this recipe shows a problem where the prompt is not
> displayed at all right at the beginning of the interaction, so the
> unwary user won't get to see what the prompt says without extra effort.
> At the same time, the text that is displayed (i.e. without the prompt
> but with one more line of candidates) is arguably a better choice when
> the user knows what the prompt says (as would be the case for me when I
> call `insert-file`).
>
Completion candidates are a mere help for the user, they are not essential
for them to know what to do. The prompt (minibuffer-prompt) and their
input are essential for them to know what to do. Why would one more
completion candidate on the last line of the minibuffer be more important,
from the point of view of user-friendliness, than the minibuffer prompt
and their input?
>
> So while I would tend to agree that showing the first line would
> probably be better it's debatable. At least, I don't think this minor
> difference warrants the kind of code you're proposing.
>
It's what icomplete-vertical, ido-vertical and others try hard to do, so
IMO that's a clear sign that this should not be debated. See the ongoing
discussion on making Emacs popular/accessible/user-friendly/... That you
or me, as experienced users, know that after hitting C-x i we are asking
Emacs to insert a file does not mean that a beginner who would start Emacs
in a too deep directory knows this or would be able to figure out what is
happening.
>>> Also this has some problematic aspects: - it focuses all its energy on
>>> showing the text before point, which is often the right choice, but
>>> not always.
>>
>> Indeed, that's not always the right choice, which is why this solution
>> does this if, and only if, the buffer-local variable
>> start-display-at-beginning-of-minibuffer has been set, in
>> minibuffer-setup-hook.
>
> But it depends on other factors than "displaying the minibuffer". It can
> vary over the lifetime of the very same minibuffer.
>
Here I admit I have no idea what you mean. AFAIU, each time the
minibuffer is entered, a new "*Minibuf-N* buffer is created, so setting
that variable would only have an effect on that specific minibuffer, while
the user is completing a command or file name or ... in that specific
minibuffer.
>>> - There's of course a risk of inf-loop if (set-window-start nil (1-
>>> end)) leads to (pos-visible-in-window-p end nil t) returning nil.
>>> How/when could this happen, I'm not completely sure, but it doesn't
>>> seem impossible.
>>
>> In practice it's not possible, unless the width of the Emacs frame is
>> so small that setting window-start near point (at point-1) would still
>> leave point invisible.
>
> It doesn't seem impossible even with a wide window. I think risky
> situations would include cases where point is right after a newline,
> and/or where tall glyphs are involved (either via face settings, or
> images, ...).
>
If you think that's a real risk, it's easy to avoid this by enclosing the
body of set-window-start-at-begin in a "(when (< (+ beg N) end)", with a
suitable N; 1 or 2 should be okay.
>> This I cannot do, alas, I'm not an expert. I tried this solution
>> extensively, on different Emacs versions. Perhaps there are cases
>> where it does not work, but I doubt it.
>
> I'd be uneasy using such code without some vague understanding about
> *why* it works.
>
The code of xdisp.c is rather intricate (to say the least), but if a vague
understanding is enough, I can explain what I understood. After
resize_mini_window(), redisplay_window() is called, and its force_start
part is executed, where run_window_scroll_functions() is called, which
updates startp and therefore w->start. This gives the user the
possibility (and as far as I can see it is the only possibility for the
user, with Lisp functions) to update window-start between
resize_mini_window() and redisplay. So set-window-start works, while
other operations (such as an explicit scroll-up or scroll-down) might not.
>>> I don't understand why the kind of face in use would make a difference
>>> w.r.t needing to use `post-command-hook`.
>>
>> I don't understand it either, alas. An example, which does not work
>> without start-display-at-beginning-of-minibuffer in post-command-hook
>> with Emacs 26.3 (but works without it with Emacs 27.1):
>
> Thanks for the example. I think this highlights the need to better
> understand how/why this works.
>
In fact I think this example demonstrates a (minor) bug in Emacs, given
that the exact same code gives a different behavior with different
versions of Emacs. I could only reproduce this bug with variable width
faces, with which I guess that some rounding approximations happen here
and there.
next prev parent reply other threads:[~2020-10-02 21:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 15:36 A solution to display completion candidates after point in a minibuffer Gregory Heytings via Emacs development discussions.
2020-10-02 16:04 ` Eli Zaretskii
2020-10-02 16:14 ` Gregory Heytings via Emacs development discussions.
2020-10-02 16:20 ` Eli Zaretskii
2020-10-02 16:32 ` Stefan Monnier
2020-10-02 17:17 ` Gregory Heytings via Emacs development discussions.
2020-10-02 19:24 ` Stefan Monnier
2020-10-02 20:18 ` Drew Adams
2020-10-02 21:30 ` Gregory Heytings via Emacs development discussions. [this message]
2020-10-02 22:44 ` Stefan Monnier
2020-10-02 23:11 ` Gregory Heytings via Emacs development discussions.
2020-10-03 0:10 ` Stefan Monnier
2020-10-03 6:59 ` Gregory Heytings via Emacs development discussions.
2020-10-03 9:04 ` Eli Zaretskii
2020-10-04 16:11 ` Gregory Heytings via Emacs development discussions.
2020-10-04 16:21 ` Eli Zaretskii
2020-10-04 16:52 ` Gregory Heytings via Emacs development discussions.
2020-10-04 17:00 ` Eli Zaretskii
2020-10-03 8:25 ` Eli Zaretskii
2020-10-03 8:07 ` Eli Zaretskii
2020-10-02 22:40 ` Gregory Heytings via Emacs development discussions.
2020-10-03 12:31 ` Gregory Heytings via Emacs development discussions.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.NEB.2.22.394.2010022139090453.14968@sdf.lonestar.org \
--to=emacs-devel@gnu.org \
--cc=ghe@sdf.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.