From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <ghe@sdf.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: A solution to display completion candidates after point in a minibuffer
Date: Sat, 03 Oct 2020 12:04:59 +0300 [thread overview]
Message-ID: <83sgavfzno.fsf@gnu.org> (raw)
In-Reply-To: <alpine.NEB.2.22.394.2010030820130453.22922@sdf.lonestar.org> (emacs-devel@gnu.org)
> Date: Sat, 03 Oct 2020 06:59:16 +0000
> cc: emacs-devel@gnu.org
> From: Gregory Heytings via "Emacs development discussions." <emacs-devel@gnu.org>
>
> >>> 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.
> >
> > Oh, indeed, in that case it would move point instead.
>
> No, that's not what I meant. In that case redisplay does not scroll and
> does not move point. Point simply becomes invisible.
No, redisplay will never accept a result that point is invisible. If
it ever does display such situations, it's a bug that needs to be
fixed.
> It becomes visible again after the next redisplay, a second or two
> later.
If such a situation exists, please describe how to reproduce it,
because it's a bug we need to fix. Emacs should never display a
window where point is not fully visible.
next prev parent reply other threads:[~2020-10-03 9:04 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.
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sgavfzno.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).