unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jose A Ortega Ruiz <jao@gnu.org>
Cc: 53398@debbugs.gnu.org
Subject: bug#53398: 29.0.50; narrow-to-region induces buffer recentering
Date: Fri, 21 Jan 2022 11:08:20 +0100	[thread overview]
Message-ID: <87fsphv1t7.fsf@gnus.org> (raw)
In-Reply-To: <87tudy9l8y.fsf@gnus.jao.io> (Jose A. Ortega Ruiz's message of "Thu, 20 Jan 2022 20:59:25 +0000")

Jose A Ortega Ruiz <jao@gnu.org> writes:

>   - start composing a message, e.g. a reply, so that the current window
>     shows only a portion of the buffer, and not the signature
>
>   - with point somewhere on the lower half of the window, C-c C-z
>     (message-kill-to-signature)
>
>   - the text from point to signature is deleted alright, but the buffer
>     contents is recentered, as if one had invoked recenter /twice/, so
>     the window gets scrolled up.  previous behaviour was that the window
>     wouldn't scroll at all, one would just see the contents of the
>     buffer below point change (and show the signature).

I've tried reproducing this in Emacs 29 with various contents in the
buffer and with various window sizes, but `C-c C-z' doesn't seem to do
any recentring for me.

Can you create a test recipe, starting from "emacs -Q", that
demonstrates the problem?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-01-21 10:08 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 [this message]
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
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=87fsphv1t7.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=53398@debbugs.gnu.org \
    --cc=jao@gnu.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).