unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 57080@debbugs.gnu.org
Subject: bug#57080: 29.0.60; [PATCH] Updates to mode line construct documentation
Date: Sat, 18 Mar 2023 10:54:48 +0200	[thread overview]
Message-ID: <83wn3ebfs7.fsf@gnu.org> (raw)
In-Reply-To: <546c5d0399490a2bb4bcd202693db46b@webmail.orcon.net.nz> (message from Phil Sainty on Sat, 18 Mar 2023 21:38:16 +1300)

> Date: Sat, 18 Mar 2023 21:38:16 +1300
> From: Phil Sainty <psainty@orcon.net.nz>
> Cc: 57080@debbugs.gnu.org
> 
> >> * The %t construct was obsolete but still documented.
> > 
> > So let's move %t to where %m is.
> 
> Since commit 8549f9e89bd9288c4c709d183a5bf8f07dbeed3d (in 2013)
> this construct doesn't do anything at all, and the documentation
> in doc/lispref/modes.texi was removed entirely at that time.
> Is it still useful to document it anywhere at this point?

I thought you were talking about adding it (to the manual or
elsewhere)?  Are you instead suggesting to remove it from the doc
string?  That wasn't clear.

> >   . I'm okay with manual changes, modulo the movement of %m -- it
> >     should stay where it was.
> >   . I'm okay with adding %t to the manual (in the "obsolete" part).
> 
> Per comments above I'm not sure this will be useful, so I'll wait for
> confirmation either way.

What do you suggest instead? remove %t from the doc string?  That's
fine with me, on emacs-29:

> >   . I'm okay with removing %t from the doc string.
> >   . I'm okay with fixing the doc string of global-mode-string.
> >   . All the rest is okay for master.
> 
> 
> Thanks Eli.

Thanks.





  reply	other threads:[~2023-03-18  8:54 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
     [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 [this message]
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=83wn3ebfs7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57080@debbugs.gnu.org \
    --cc=psainty@orcon.net.nz \
    /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).