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 23:11:22 +0000 [thread overview]
Message-ID: <alpine.NEB.2.22.394.2010030045420453.29380@sdf.lonestar.org> (raw)
In-Reply-To: <jwvk0w8gsrz.fsf-monnier+emacs@gnu.org>
Hi Stefan,
>
> In your example recipe, the first line is hidden. I agree that it's
> probably a bad idea *when you enter the minibuffer*. But this same
> display is probably a better choice after the user read the prompt and
> knows what's the current directory, at which point the list of remaining
> completions is likely going to the main focus.
>
Thank you, now I see what you mean. IMO (and I would be extremely
surprised if I were the only one with that opinion) seeing the current
directory disappearing is disturbing (and from a newcomer point of view:
very disturbing), so the prompt an user input should always be displayed
(unless the miniwindow is too small of course).
>
> After `set-window-start`, the redisplay will be inevitably re-started,
> which in turn might decide to scroll and thus
> `run_window_scroll_functions`, etc...
>
> IIRC the reason it won't scroll the second time around is because point
> should be visible (and redisplay would only scroll in order to move
> point within view).
>
I don't know, but I'm not sure about that. If you (set-window-start nil
1) unconditionally in window-scroll-functions, this setting will be obeyed
by redisplay, even if point is not visible anymore. Which, by the way,
explains the need of a recursive call to set-window-start-at-begin.
next prev parent reply other threads:[~2020-10-02 23:11 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.
2020-10-02 22:44 ` Stefan Monnier
2020-10-02 23:11 ` Gregory Heytings via Emacs development discussions. [this message]
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.2010030045420453.29380@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.