From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40915@debbugs.gnu.org
Subject: bug#40915: [PATCH] Make leaving Info-summary more intuitive
Date: Tue, 28 Apr 2020 09:37:38 +0200 [thread overview]
Message-ID: <CADwFkm=-weFXJjk10CQprUNDnHJSyfFGFwxEq8bNyYB_KyDPJA@mail.gmail.com> (raw)
In-Reply-To: <83sggo2ik3.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> I'm not sure I understand the expected result. The help buffer
> displayed when you press '?' says:
>
> q Quit Info: reselect previously selected buffer.
>
> So it seems Info behaves as documented? The way to exit the help
> screen and return to the Info manual is by repeatedly pressing SPC
> until you wind up in the original Info buffer.
Sure, the result is formally correct. It's just counter-intuitive.
Normally when I say 'q' in the "*Help*" buffer, I bury it. But here,
'q' buries two buffers.
> I could understand that we'd like to have a single key to quit the
> help screen, perhaps even when 'q' is pressed (which would be a change
> in behavior), but even then it is IMO wrong to completely remove the
> pushing onto unread-command-events, because this command is set such
> that you could read about a key and execute it while still in the help
> screen. IOW, the fact that the key you pres is generally executed
> after exiting the help screen is an important feature: it avoids the
> need to remember the key you found in *Help* and retype it after you
> are back in the Info buffer.
Thanks for explaining the motivation behind that feature.
I'm fine with doing a less invasive change: treat 'q' as a special
case in Info-summary. Many users are hardwired to press 'q' to make a
"*Help*" buffer go away.
However, there is an inconsistency between modes; in view-mode and
special-mode, '?' is bound to describe-major-mode.
Would it be worth it to be more consistent? In other words, doing one of:
(a) make 'Info-summary' into a general help command and use it in more
places, or
(b) deprecate 'Info-summary' in favour of 'describe-mode'.
It seems to me that _if_ we think the 'Info-summary' behaviour is
useful, we would want to ensure more modes can benefit from it. Or,
to put it another way, I don't see why it would be uniquely useful to
Info-mode -- it should be useful either in many more modes or nowhere.
I haven't formed a strong opinion on this, but it would be interesting
to hear what people think.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-04-28 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 22:28 bug#40915: [PATCH] Make leaving Info-summary more intuitive Stefan Kangas
2020-04-28 7:09 ` Eli Zaretskii
2020-04-28 7:37 ` Stefan Kangas [this message]
2020-04-28 7:57 ` Eli Zaretskii
2020-04-28 17:11 ` Drew Adams
2020-04-28 17:17 ` Drew Adams
2020-04-28 17:39 ` Stefan Kangas
2020-04-28 18:43 ` Drew Adams
2020-08-08 12:13 ` Lars Ingebrigtsen
2020-10-07 4:31 ` Lars Ingebrigtsen
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='CADwFkm=-weFXJjk10CQprUNDnHJSyfFGFwxEq8bNyYB_KyDPJA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=40915@debbugs.gnu.org \
--cc=eliz@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.