From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: diredwolf1@gmail.com, 57080@debbugs.gnu.org
Subject: bug#57080: 28.1; The %m modeline construct does not work for emacs-lisp-mode
Date: Thu, 11 Aug 2022 00:49:55 +1200 [thread overview]
Message-ID: <8f76c5fd3cf4bda02f9b55c3df55a47c@webmail.orcon.net.nz> (raw)
In-Reply-To: <83h72kstxb.fsf@gnu.org>
On 2022-08-10 14:40, Eli Zaretskii wrote:
>> From: Phil Sainty <psainty@orcon.net.nz>
>> (info "(elisp) %-Constructs") states that ‘%m’ and ‘mode-name’
>> are equivalent, which is evidentially wrong.
>
> It also says %m is obsolete, which you didn't mention.
Ah, I didn't even see that -- I'd thought that paragraph was part
of the details for '%%' immediately above, and hadn't read it.
> I won't object to telling there that %m doesn't work with non-
> string mode-name, if that's your suggestion.
I'll do this, and also move the whole description below the '%m'.
next prev parent reply other threads:[~2022-08-10 12:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 16:06 bug#57080: 28.1; The %m modeline construct does not work for emacs-lisp-mode diredwolf
2022-08-09 16:45 ` Eli Zaretskii
[not found] ` <B27E1FE6-E7D2-4551-877B-9B1BC005AE56@gmail.com>
2022-08-09 17:06 ` Eli Zaretskii
2022-08-10 0:23 ` Phil Sainty
2022-08-10 2:40 ` Eli Zaretskii
2022-08-10 12:49 ` Phil Sainty [this message]
[not found] ` <87bdaf86c1edac42a5c004c14364608b@webmail.orcon.net.nz>
2023-03-18 7:30 ` bug#57080: 29.0.60; [PATCH] Updates to mode line construct documentation (was: The %m modeline construct does not work for emacs-lisp-mode) Phil Sainty
2023-03-18 7:46 ` Eli Zaretskii
2023-03-18 8:38 ` bug#57080: 29.0.60; [PATCH] Updates to mode line construct documentation Phil Sainty
2023-03-18 8:54 ` Eli Zaretskii
2023-03-18 9:25 ` Phil Sainty
2023-03-26 11:43 ` Phil Sainty
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=8f76c5fd3cf4bda02f9b55c3df55a47c@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=57080@debbugs.gnu.org \
--cc=diredwolf1@gmail.com \
--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 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).