From: Michael Hendricks <michael@ndrix.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 31139@debbugs.gnu.org
Subject: bug#31139: [PATCH] Document Narrow indicator in describe-mode
Date: Tue, 17 Apr 2018 18:59:12 +0000 [thread overview]
Message-ID: <CAFHuXuYPqr=tgh4a_EXaj4STw1XnrD2VE2xjxH_0W09mcG=RRg@mail.gmail.com> (raw)
In-Reply-To: <877epckneb.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Hi Noam,
On Thu, Apr 12, 2018 at 5:36 PM Noam Postavsky <npostavs@gmail.com> wrote:
> Narrowing isn't exactly a minor mode though, wouldn't this be
> potentially confusing?
>
You're right that narrowing isn't exactly a minor mode. However,
standard-mode-line-format includes narrowing information as part of
mode-line-modes. So the narrowing indicator is rendered inside the same
parentheses as indicators for true major and minor modes. Since
describe-mode provides documentation for everything else that's inside
those parentheses, it seemed appropriate to document narrowing in the same
place.
When I first started using emacs some years ago, I remember being confused
why "Narrow" was the only thing in the mode list that wasn't mentioned by
describe-mode. I understand it now, but I think others might face similar
confusion with the current behavior. I think this patch would address that.
[-- Attachment #2: Type: text/html, Size: 1373 bytes --]
next prev parent reply other threads:[~2018-04-17 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 17:12 bug#31139: [PATCH] Document Narrow indicator in describe-mode Michael Hendricks
2018-04-12 23:36 ` Noam Postavsky
2018-04-17 18:59 ` Michael Hendricks [this message]
2018-04-19 12:16 ` Noam Postavsky
2018-04-19 13:08 ` Eli Zaretskii
2018-04-19 14:38 ` Michael Hendricks
2018-04-19 14:44 ` Eli Zaretskii
2018-04-24 15:00 ` Michael Hendricks
2018-05-05 9:44 ` 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='CAFHuXuYPqr=tgh4a_EXaj4STw1XnrD2VE2xjxH_0W09mcG=RRg@mail.gmail.com' \
--to=michael@ndrix.org \
--cc=31139@debbugs.gnu.org \
--cc=npostavs@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).