From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: me@eshelyaron.com, 66317@debbugs.gnu.org, juri@linkov.net
Subject: bug#66317: Project mode-line
Date: Fri, 06 Oct 2023 07:50:02 +0300 [thread overview]
Message-ID: <83cyxs2w3p.fsf@gnu.org> (raw)
In-Reply-To: <456e170e-2934-9f8b-e34a-3076901f8de1@gutov.dev> (message from Dmitry Gutov on Thu, 5 Oct 2023 23:23:17 +0300)
> Date: Thu, 5 Oct 2023 23:23:17 +0300
> Cc: 66317@debbugs.gnu.org, me@eshelyaron.com
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> On 04/10/2023 09:18, Juri Linkov wrote:
> > diff --git a/lisp/bindings.el b/lisp/bindings.el
> > index 207adb3a2a4..70e4087e131 100644
> > --- a/lisp/bindings.el
> > +++ b/lisp/bindings.el
> > @@ -682,6 +682,7 @@ mode-line-end-spaces
> > 'mode-line-buffer-identification
> > " "
> > 'mode-line-position
> > + '(project-mode-line project-mode-line-format)
> > '(vc-mode vc-mode)
> > " "
> > 'mode-line-modes
>
> Speaking of this change from the first patch, do we want to have
> project-mode-line automatically supported in Emacs <= 29, when they
> install the new version from ELPA? Can we safely do that?
>
> Simply altering mode-line-format, as in the original patch, might mess
> up the custom mode-line the user had set up (or installed). How to only
> change the default mode-line is less obvious, but perhaps checking that
> the current value is equal to (get 'mode-line-format 'standard-value)
> would mean altering is okay.
>
> Or otherwise we should say something in the docstring of
> project-mode-line: that it's only directly supported in Emacs 30, and in
> older versions the user need to add the corresponding entry to the
> mode-line-format by hand.
I think supporting it in Emacs 30 is fine. It's a very minor feature,
after all, so let's not invest too much effort in it.
next prev parent reply other threads:[~2023-10-06 4:50 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 6:29 bug#66317: Project mode-line Juri Linkov
2023-10-03 8:07 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-03 16:24 ` Dmitry Gutov
2023-10-03 17:11 ` Juri Linkov
2023-10-03 17:51 ` Dmitry Gutov
2023-10-03 17:58 ` Juri Linkov
2023-10-03 18:04 ` Dmitry Gutov
2023-10-03 18:17 ` Eli Zaretskii
2023-10-04 6:18 ` Juri Linkov
2023-10-04 7:15 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-04 17:06 ` Juri Linkov
2023-10-05 20:03 ` Spencer Baugh
2023-10-05 20:16 ` Dmitry Gutov
2023-10-06 6:46 ` Juri Linkov
2023-10-09 18:45 ` Juri Linkov
2023-10-09 18:57 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-10 6:56 ` Juri Linkov
2023-10-10 11:46 ` Dmitry Gutov
2023-10-11 6:27 ` Juri Linkov
2023-10-04 7:43 ` Eli Zaretskii
2023-10-04 14:34 ` Dmitry Gutov
2023-10-04 17:04 ` Juri Linkov
2023-10-05 20:23 ` Dmitry Gutov
2023-10-06 4:50 ` Eli Zaretskii [this message]
2023-10-06 6:44 ` Juri Linkov
2023-10-06 10:20 ` Dmitry Gutov
2023-10-09 18:10 ` Juri Linkov
2023-10-09 18:22 ` Dmitry Gutov
2023-10-09 18:48 ` Juri Linkov
2023-10-09 18:52 ` Dmitry Gutov
2023-10-10 6:50 ` Juri Linkov
2023-10-10 7:10 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-10 7:18 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-10 10:45 ` Dmitry Gutov
2023-10-10 11:34 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-10 11:42 ` Dmitry Gutov
2023-10-20 9:01 ` Ihor Radchenko
2023-10-20 15:52 ` Dmitry Gutov
2023-10-31 7:34 ` Juri Linkov
2023-11-01 2:03 ` Dmitry Gutov
2023-11-01 7:32 ` Juri Linkov
2023-10-03 12:06 ` Stefan Kangas
2023-10-15 22:42 ` sbaugh
2023-10-16 0:57 ` Dmitry Gutov
2023-10-16 17:01 ` Juri Linkov
2023-10-16 19:12 ` Eli Zaretskii
2023-10-18 17:20 ` Juri Linkov
2023-10-18 18:41 ` Dmitry Gutov
2023-10-19 6:40 ` Juri Linkov
2023-10-19 11:23 ` Dmitry Gutov
2023-10-23 17:23 ` Juri Linkov
2023-10-24 23:48 ` Dmitry Gutov
2023-10-18 18:55 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83cyxs2w3p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66317@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=juri@linkov.net \
--cc=me@eshelyaron.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.