From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>, 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 10:11:26 -0700 (PDT) [thread overview]
Message-ID: <25e557d9-4b68-470a-96d5-c51552d5fa38@default> (raw)
In-Reply-To: <CADwFkm=-weFXJjk10CQprUNDnHJSyfFGFwxEq8bNyYB_KyDPJA@mail.gmail.com>
> 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.
I don't really understand. Info-summary is a
help command that describes Info. You can invoke
it anywhere - not just in Info, so I don't see
why it would be deprecated and its content given
to describe-mode.
For (a), what do you mean by a "general" help
command? The point of Info-summary is to provide
succinct help about Info.
next prev parent reply other threads:[~2020-04-28 17:11 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
2020-04-28 7:57 ` Eli Zaretskii
2020-04-28 17:11 ` Drew Adams [this message]
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
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=25e557d9-4b68-470a-96d5-c51552d5fa38@default \
--to=drew.adams@oracle.com \
--cc=40915@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).