all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Eshel Yaron <me@eshelyaron.com>, Juri Linkov <juri@linkov.net>
Cc: 71466@debbugs.gnu.org
Subject: bug#71466: 30.0.50; Buffer-menu-group-by non-nil resets point when Buffer List is reverted
Date: Mon, 17 Jun 2024 15:27:45 +0300	[thread overview]
Message-ID: <30404984-e7ac-4f92-a194-06438dbf2d03@gutov.dev> (raw)
In-Reply-To: <m1y174uidt.fsf@dazzs-mbp.home>

On 17/06/2024 10:40, Eshel Yaron wrote:
>>> But this will not handle modes that don't use tabulated-list.
>>> For example, reverting an xref buffer with outlines now restores
>>> visibility of outlines, but doesn't restore point.  OTOH, maybe it's
>>> not responsibility of outline-minor-mode to restore point when it's
>>> not on a heading line.
>> For xref I propose a separate patch that keeps point on the same line
>> after reverting the xref buffer:
> LGTM, but FWIW the situation with xref-revert-buffer is not ideal IMO:
> it might be cleaner to leave 'g' bound to the usual revert-buffer and
> set revert-buffer-function to (a slightly modified) xref-revert-buffer.
> That way xref-revert-buffer wouldn't need to duplicate generic parts of
> revert-buffer, such as running revert-buffer-restore-functions.  WDYT?

I'm okay with that.





  reply	other threads:[~2024-06-17 12:27 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=30404984-e7ac-4f92-a194-06438dbf2d03@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=71466@debbugs.gnu.org \
    --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 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.