From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: 65905@debbugs.gnu.org
Subject: bug#65905: 30.0.50; Consider changing info buffer names to info<(org)> rather than info<3>
Date: Wed, 13 Sep 2023 22:09:51 +0300 [thread overview]
Message-ID: <83msxpnb40.fsf@gnu.org> (raw)
In-Reply-To: <87il8e14xl.fsf@laptop.lockywolf.net> (message from Vladimir Nikishkin on Wed, 13 Sep 2023 23:07:44 +0800)
> From: Vladimir Nikishkin <lockywolf@gmail.com>
> Cc: 65905@debbugs.gnu.org
> Date: Wed, 13 Sep 2023 23:07:44 +0800
>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> But it's not the same thing, is it?
> >
> > 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.
> >
>
> No, it does not do that. C-h R just prompts for a "Manual name: " in the
> minibuffer, and if I press TAB, shows all the names for all the
> installed manuals in the system.
You are supposed to type "org" and press RET when it prompts. Because
you know you want to go to the Org manual, right?
> It does switch to the previously open buffer, if I happen to remember
> the name of the manual. But if I do not remember whether I was reading
> epa's manual, or pgg's manual (similar features!), I have to go through
> them by trial and error.
Then I don't understand something. Your original request was to name
the buffer "*info*<org>", so that you could type
C-x b *info*<org> RET
to return to it, right? But if you don't remember the name of the
manual, how would you know to type the "<org>" part in the above? And
if you do remember the name of the manual, then how does
C-h R org RET
require more from your memory than
C-x b *info*<org> RET
? What am I missing here?
next prev parent reply other threads:[~2023-09-13 19:09 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 [this message]
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
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=83msxpnb40.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65905@debbugs.gnu.org \
--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).