From: Jose A Ortega Ruiz <jao@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 53398@debbugs.gnu.org
Subject: bug#53398: 29.0.50; narrow-to-region induces buffer recentering
Date: Sun, 23 Jan 2022 15:42:51 +0000 [thread overview]
Message-ID: <871r0ycvb8.fsf@gnus.jao.io> (raw)
In-Reply-To: <875yqaaaym.fsf@gnus.org>
On Sun, Jan 23 2022, Lars Ingebrigtsen wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> So I don't think there's anything in this behavior that isn't
>> expected. If you want to prevent recentering, try setting
>> max-mini-window-height to 1, so that mini-windows aren't resized. (I
>> didn't try it, though.) Or just don't ask the echo-area messages to
>> display so much stuff.
>
> Yes, I don't think there's anything much we could do on the Emacs side
> here -- any function that issues a message while narrowing is in effect
> will lead to recentring with a set-message function like this.
just for my own understanding: are you saying that the fact that the
minibuffer displays more than one line causes a re-centering of my
current buffer? why is that normal? if i M-: (message "a\nb\n"), should
i expect that my current buffer is recentered? (it isn't).
(also, for the record, the message displayed by that custom set-message
does not span more than one line, as far as i can tell.)
next prev parent reply other threads:[~2022-01-23 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 20:59 bug#53398: 29.0.50; narrow-to-region induces buffer recentering Jose A Ortega Ruiz
2022-01-21 7:07 ` Eli Zaretskii
2022-01-21 10:08 ` Lars Ingebrigtsen
2022-01-22 19:13 ` Jose A Ortega Ruiz
2022-01-23 6:08 ` Eli Zaretskii
2022-01-23 12:33 ` Lars Ingebrigtsen
2022-01-23 15:42 ` Jose A Ortega Ruiz [this message]
2022-01-23 16:12 ` Lars Ingebrigtsen
2022-01-23 16:34 ` Eli Zaretskii
2022-01-23 17:04 ` Jose A Ortega Ruiz
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=871r0ycvb8.fsf@gnus.jao.io \
--to=jao@gnu.org \
--cc=53398@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/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).