all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Systematizing back navigation
Date: Tue, 21 Nov 2023 14:35:26 +0800	[thread overview]
Message-ID: <87a5r7ipg1.fsf@yahoo.com> (raw)
In-Reply-To: <70ABA96C-74EE-40B2-BB0F-A0FDAA412BE7@gnu.org> (Eli Zaretskii's message of "Tue, 21 Nov 2023 07:35:24 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> I think you are over-engineering this.  That a key has different
> bindings in different major modes is nothing new in Emacs.  Moreover,
> smartphone apps are also inconsistent in what the Back button does in
> each situation.
>
> So I don't see why we need to worry about this, let alone pretend
> there's some deep internal issue here.  Perhaps you bumped into some
> specific situation, and then tried to generalize it too much.  In that
> case, I suggest to describe the original issue, not its
> generalizations.

I did describe three specific scenarios that I come across frequently:
Info, Help and Gnus Article buffers.  Besides those, there are also
pop-ups displayed by the likes of VC,
dired-mouse-find-file-other-window, and virtually every other caller of
display-buffer.  With these, I'd rather Back dismissed the new window
altogether than switch to whatever window previous-buffer selects.



  reply	other threads:[~2023-11-21  6:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87il5vixat.fsf.ref@yahoo.com>
2023-11-21  3:45 ` Systematizing back navigation Po Lu
2023-11-21  5:35   ` Eli Zaretskii
2023-11-21  6:35     ` Po Lu [this message]
2023-11-21  6:57       ` Eli Zaretskii
2023-11-21 11:43         ` Dmitry Gutov
2023-11-21  6:39   ` Adam Porter
2023-11-21 11:44     ` Dmitry Gutov
2023-11-21 13:15   ` sbaugh
2023-11-21 17:01   ` 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=87a5r7ipg1.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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.