From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: lockywolf@gmail.com, 65905@debbugs.gnu.org
Subject: bug#65905: 30.0.50; Consider changing info buffer names to info<(org)> rather than info<3>
Date: Thu, 14 Sep 2023 08:59:18 +0300 [thread overview]
Message-ID: <837cotmh1l.fsf@gnu.org> (raw)
In-Reply-To: <874jjx94eo.fsf@gmail.com> (message from Kévin Le Gouguec on Wed, 13 Sep 2023 22:58:23 +0200)
> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: Vladimir Nikishkin <lockywolf@gmail.com>, 65905@debbugs.gnu.org
> Date: Wed, 13 Sep 2023 22:58:23 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > It's not? I think it is the same. You wanted a simply way of getting
> > back to a manual that you were reading earlier in the session, which
> > you still have in some Info buffer, no? That's what "C-h R" does: it
> > first looks in the Info buffers already present in the session, and,
> > if not found, then looks for the manual installed on the system. In
> > your case, the first step will succeed.
>
> Speaking for myself: "C-x b PATTERN TAB" is kind of ingrained in my
> muscle memory to switch back to all sorts of buffers I know are open.
> So my brain turns "Switch back to that Info buffer for the FOO manual"
> into "C-x b info TAB", then I stare blankly at the "*info<N>*"
> candidates for a couple of seconds, and pick one at random.
>
> Point taken re. C-h R (which even limits completion to opened manuals
> with C-u, neat), though switching buffers with C-x b is such a generic
> action that I perform dozens of times an hour without thinking twice,
> that I suspect stopping myself from C-x b'ing just for Info buffers is
> going to be hard.
It isn't, rest assured: I walked that way myself.
prev parent reply other threads:[~2023-09-14 5:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 4:09 bug#65905: 30.0.50; Consider changing info buffer names to info<(org)> rather than info<3> Vladimir Nikishkin
2023-09-13 12:58 ` Eli Zaretskii
2023-09-13 14:04 ` Vladimir Nikishkin
2023-09-13 14:57 ` Eli Zaretskii
2023-09-13 15:07 ` Vladimir Nikishkin
2023-09-13 19:09 ` Eli Zaretskii
2023-09-14 1:13 ` Vladimir Nikishkin
2023-09-13 20:58 ` Kévin Le Gouguec
2023-09-14 2:11 ` Vladimir Nikishkin
2023-09-14 5:59 ` Eli Zaretskii [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
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=837cotmh1l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65905@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=lockywolf@gmail.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).