all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Systematizing back navigation
Date: Tue, 21 Nov 2023 19:01:00 +0200	[thread overview]
Message-ID: <86msv7xjfz.fsf@mail.linkov.net> (raw)
In-Reply-To: <87il5vixat.fsf@yahoo.com> (Po Lu's message of "Tue, 21 Nov 2023 11:45:46 +0800")

> Thus instead of implementing and installing a prototype of this at a
> venture, I want to ask everyone else's advice, and also for ideas as
> regards when and whether this Back mechanism should act as described in
> the last paragraph.

I'm afraid it's a quite hopeless endeavor to find such a common denominator
that would satisfy even a small fraction of users since endless number of
navigation spaces might be active at the same time.  Much more than even
possible for next-error navigation where we struggled to find a way
to switch between available navigation spaces.  For example, for the
Back button my preference is to navigate in the file system: in a file buffer
typing the Back button goes to the Dired buffer with point on that file name
when the file was visited from Dired, then the next Back button goes up
to the parent directory, etc. like in a typical File Manager.



      parent reply	other threads:[~2023-11-21 17:01 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
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 [this message]

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=86msv7xjfz.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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.