From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 30397@debbugs.gnu.org, juri@linkov.net
Subject: bug#30397: Random numbers in grep mode-line
Date: Fri, 09 Feb 2018 17:35:11 +0200 [thread overview]
Message-ID: <83zi4i2n2o.fsf@gnu.org> (raw)
In-Reply-To: <3e9d0fd8-b859-4eec-8f34-54185dd6c0f3@default> (message from Drew Adams on Fri, 9 Feb 2018 07:27:55 -0800 (PST))
> Date: Fri, 9 Feb 2018 07:27:55 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: juri@linkov.net, 30397@debbugs.gnu.org
>
> > > But `C-h m' says nothing about this (it should).
> > >
> > > And clicking `compilation-mode' (the parent) in the `C-h m' output
> > > shows that mode's doc, but it too says nothing about this.
> >
> > I don't see modes whose "C-h m" tells anything about mode-line
> > indicators. Do you?
>
> No. And?
>
> How many modes do you see that have mode-line info
> that needs explanation?
From my POV, almost all of those which put there something that is not
just the mode's (abbreviated) name.
> There might well be some others - in that case, feel free to file
> bugs for those too.
Filing a bug doesn't solve the problem.
> If you agree that better help about this would be
> in order, where would you suggest putting that help,
> if not on `C-h m'?
Our current practice is to describe that in the manual. If we decide
to add that to "C-h m", we should do that for all the modes. We
should also consider the discoverability: "C-h m" is not where I would
look for documentation of a mode, only for its keybindings.
next prev parent reply other threads:[~2018-02-09 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<87tvurtbek.fsf@mail.linkov.net>
[not found] ` <<702f1621-529b-47b0-a15d-898a2fd81f79@default>
[not found] ` <<83eflu4hjx.fsf@gnu.org>
2018-02-09 15:27 ` bug#30397: Random numbers in grep mode-line Drew Adams
2018-02-09 15:35 ` Eli Zaretskii [this message]
[not found] ` <<83fu6a4hlh.fsf@gnu.org>
2018-02-09 15:43 ` Drew Adams
[not found] <<<87tvurtbek.fsf@mail.linkov.net>
[not found] ` <<<702f1621-529b-47b0-a15d-898a2fd81f79@default>
[not found] ` <<<83eflu4hjx.fsf@gnu.org>
[not found] ` <<3e9d0fd8-b859-4eec-8f34-54185dd6c0f3@default>
[not found] ` <<83zi4i2n2o.fsf@gnu.org>
2018-02-09 15:59 ` Drew Adams
2018-02-08 21:32 Juri Linkov
2018-02-08 21:48 ` Drew Adams
2018-02-09 9:51 ` Eli Zaretskii
2018-02-08 23:00 ` Noam Postavsky
2018-02-10 21:32 ` Juri Linkov
2018-02-10 22:01 ` Drew Adams
2018-02-11 21:40 ` Juri Linkov
2018-02-12 4:54 ` Drew Adams
2018-02-12 15:47 ` Eli Zaretskii
2018-02-12 21:39 ` Juri Linkov
2018-02-11 20:45 ` Richard Stallman
2018-02-12 16:34 ` Eli Zaretskii
2018-02-09 9:50 ` 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=83zi4i2n2o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30397@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=juri@linkov.net \
/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).