all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jose A Ortega Ruiz <jao@gnu.org>
Cc: larsi@gnus.org, 53398@debbugs.gnu.org
Subject: bug#53398: 29.0.50; narrow-to-region induces buffer recentering
Date: Sun, 23 Jan 2022 18:34:15 +0200	[thread overview]
Message-ID: <83ilual8c8.fsf@gnu.org> (raw)
In-Reply-To: <871r0ycvb8.fsf@gnus.jao.io> (message from Jose A Ortega Ruiz on Sun, 23 Jan 2022 15:42:51 +0000)

> From: Jose A Ortega Ruiz <jao@gnu.org>
> Cc: 53398@debbugs.gnu.org
> Date: Sun, 23 Jan 2022 15:42:51 +0000
> 
> 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).

If point is in the last N lines that would be "covered" by the
enlarged mini-window, then Emacs will recenter to keep point visible.

> (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.)

It does, see the continuation indicator at the right fringe.  You have
computed the alignment to span the entire screen line, but Emacs needs
one more place there to display the cursor.





  parent reply	other threads:[~2022-01-23 16:34 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
2022-01-23 16:12           ` Lars Ingebrigtsen
2022-01-23 16:34           ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ilual8c8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53398@debbugs.gnu.org \
    --cc=jao@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 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.