unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 71466@debbugs.gnu.org, me@eshelyaron.com, juri@linkov.net
Subject: bug#71466: 30.0.50; Buffer-menu-group-by non-nil resets point when Buffer List is reverted
Date: Tue, 18 Jun 2024 20:36:39 +0300	[thread overview]
Message-ID: <86tthqp2zc.fsf@gnu.org> (raw)
In-Reply-To: <a052397b-4519-4806-a511-b10d0513c16b@gutov.dev> (message from Dmitry Gutov on Tue, 18 Jun 2024 20:05:14 +0300)

> Date: Tue, 18 Jun 2024 20:05:14 +0300
> Cc: 71466@debbugs.gnu.org, juri@linkov.net
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 18/06/2024 17:46, Eli Zaretskii wrote:
> > But the original xref-revert-buffer didn't do all those other things,
> > did it?  So invoking it directly will be more similar to what that did
> > before.
> 
> The current xref-revert-buffer already does those things - namely invoke 
> revert-buffer-restore-functions. Even though it's a relatively recent 
> phenomenon.
> 
> And it makes sense to provide this feature to the users of 
> xref-revert-buffer, so I don't see why not.

All things being equal, leaving the old names of the functions and
commands should be preferred.  That's all I'm saying.  It's a minor
issue, but the cost of staying more compatible is also minor.





  reply	other threads:[~2024-06-18 17:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10  8:49 bug#71466: 30.0.50; Buffer-menu-group-by non-nil resets point when Buffer List is reverted Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-11 17:05 ` Juri Linkov
2024-06-17  6:35   ` Juri Linkov
2024-06-17  7:40     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-17 12:27       ` Dmitry Gutov
2024-06-17 15:43         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-17 22:24           ` Dmitry Gutov
2024-06-18  7:00             ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-18 12:58               ` Eli Zaretskii
2024-06-18 14:01                 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-18 14:46                   ` Eli Zaretskii
2024-06-18 16:55                     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-18 17:05                     ` Dmitry Gutov
2024-06-18 17:36                       ` Eli Zaretskii [this message]
2024-06-18 17:47                         ` Dmitry Gutov
2024-06-20 16:38                           ` Juri Linkov
2024-06-20 17:35                             ` Dmitry Gutov
2024-06-24  6:27                               ` Juri Linkov
2024-06-24 22:42                                 ` Dmitry Gutov
2024-06-25  6:54                                   ` Juri Linkov
2024-06-25 12:54                                   ` Eli Zaretskii
2024-06-25 23:14                                     ` Dmitry Gutov
2024-06-26 11:25                                       ` Eli Zaretskii
2024-06-26 16:56                                         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 18:33                                           ` Eli Zaretskii
2024-06-26 21:05                                             ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-27  6:39                                               ` Juri Linkov
2024-06-27  7:19                                                 ` Eli Zaretskii
2024-06-27  0:11                                           ` Dmitry Gutov
2024-06-17 12:32     ` Dmitry Gutov
2024-06-17 16:31       ` Juri Linkov
2024-06-17 22:16         ` Dmitry Gutov
2024-06-27  6:43           ` Juri Linkov

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=86tthqp2zc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71466@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=juri@linkov.net \
    --cc=me@eshelyaron.com \
    /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).