From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: ghe@sdf.org, 43572@debbugs.gnu.org
Subject: bug#43572: Feature request: make it possible to choose whether the first lines of the minibuffer should be displayed instead of the last ones
Date: Thu, 24 Sep 2020 19:59:10 +0300 [thread overview]
Message-ID: <83ft77t8kh.fsf@gnu.org> (raw)
In-Reply-To: <jwvd02bp1o1.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 24 Sep 2020 12:44:56 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: ghe@sdf.org, 43572@debbugs.gnu.org
> Date: Thu, 24 Sep 2020 12:44:56 -0400
>
> > where [...] denotes the portion of text indicated as "important
> > chunk", and | denotes the position of point. Suppose further than the
> > available screen estate is insufficient to display all of the
> > "important chunk" -- which part would you want to see on display: the
> > part before point? after point? centered at point? something else?
>
> I think either of those would be fine, so it should be decided by the
> usual scrolling constraints (i.e. don't scroll if not needed, obey
> scroll-conservatively, ...).
>
> IOW, by default if scrolling was needed anyway and scroll-conservatively
> is not set, I'd expect "centered at point".
The code which implements automatic scrolling was not written with the
mini-window in mind. In fact, we would like not to allow any
scrolling at all there.
So perhaps relying on scrolling could be fine in normal windows, it
will most probably do the wrong thing in mini-windows. And even in
normal windows, it will probably work only by sheer luck, because the
design there cares about the context of point, and that is not
necessarily what you want with "important chunks".
next prev parent reply other threads:[~2020-09-24 16:59 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 20:57 bug#43572: Feature request: make it possible to choose whether the first lines of the minibuffer should be displayed instead of the last ones Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 15:17 ` Eli Zaretskii
2020-09-23 19:15 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 19:37 ` Eli Zaretskii
2020-09-23 20:15 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 14:24 ` Eli Zaretskii
2020-09-24 14:41 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 15:11 ` Eli Zaretskii
2020-09-24 16:09 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 16:20 ` Eli Zaretskii
2020-09-24 16:40 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 17:03 ` Eli Zaretskii
2020-09-24 21:51 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-25 6:59 ` Eli Zaretskii
2020-09-25 8:34 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-25 9:14 ` Eli Zaretskii
2020-09-25 10:14 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-25 11:17 ` Eli Zaretskii
2020-09-25 11:34 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 22:59 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-25 18:31 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 18:33 ` Stefan Monnier
2020-09-23 18:47 ` Eli Zaretskii
2020-09-23 23:18 ` Stefan Monnier
2020-09-24 14:34 ` Eli Zaretskii
2020-09-24 16:44 ` Stefan Monnier
2020-09-24 16:59 ` Eli Zaretskii [this message]
2020-09-27 21:59 ` Stefan Monnier
2020-09-28 6:20 ` Eli Zaretskii
2020-09-28 13:30 ` Stefan Monnier
2020-09-28 13:44 ` Eli Zaretskii
2020-09-28 16:58 ` Stefan Monnier
2020-10-02 15:40 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-02 16:08 ` Stefan Monnier
2020-10-02 16:11 ` Eli Zaretskii
2020-10-02 16:25 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-02 19:30 ` Eli Zaretskii
2020-10-02 21:49 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-29 14:02 ` Lars Ingebrigtsen
2020-09-23 19:46 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 20:00 ` Stefan Monnier
2020-09-23 22:47 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-23 23:20 ` Stefan Monnier
2020-09-23 23:26 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 2:07 ` Stefan Monnier
2020-09-24 7:45 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 16:26 ` Stefan Monnier
2020-09-24 8:06 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 14:43 ` Eli Zaretskii
2020-09-24 14:52 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 15:20 ` Eli Zaretskii
2020-09-24 14:26 ` Eli Zaretskii
2020-09-24 14:20 ` Eli Zaretskii
2020-09-24 14:27 ` Gregory Heytings via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-24 16:40 ` Stefan Monnier
2020-09-24 16:54 ` Eli Zaretskii
2020-09-27 16:11 ` Eli Zaretskii
2020-09-27 21:52 ` Stefan Monnier
2020-09-28 6:10 ` Eli Zaretskii
2020-09-28 13:24 ` Stefan Monnier
2020-09-28 13:42 ` Eli Zaretskii
2020-09-28 16:56 ` Stefan Monnier
[not found] <<alpine.NEB.2.22.394.2009222215560453.32542@sdf.lonestar.org>
[not found] ` <<jwvwo0ktlge.fsf-monnier+emacs@gnu.org>
[not found] ` <<alpine.NEB.2.22.394.2009232116430453.29439@sdf.lonestar.org>
[not found] ` <<834knnuugm.fsf@gnu.org>
[not found] ` <<jwvimc3p2a0.fsf-monnier+emacs@gnu.org>
[not found] ` <<83h7rnt8s3.fsf@gnu.org>
[not found] ` <<833633nqru.fsf@gnu.org>
[not found] ` <<jwvwo0e6gcb.fsf-monnier+emacs@gnu.org>
[not found] ` <<83r1qmmnxu.fsf@gnu.org>
2020-09-28 15:53 ` Drew Adams
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=83ft77t8kh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43572@debbugs.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.