From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Spencer Baugh <sbaugh@janestreet.com>, 71823@debbugs.gnu.org
Subject: bug#71823: 31.0.50; project-mode-line and eglot duplicate project-name in mode-line
Date: Fri, 28 Jun 2024 18:49:14 +0100 [thread overview]
Message-ID: <CALDnm53aooQJgdYGR3HU89jMeAZVS-8TkD133eL6ttJNZuueKA@mail.gmail.com> (raw)
In-Reply-To: <86wmm9jfk7.fsf@gnu.org>
On Fri, Jun 28, 2024 at 3:41 PM Eli Zaretskii <eliz@gnu.org> wrote:
> João, any comments?
Tiny switches for these customizations is not a good idea. It's complex,
hard to find, and doesn't scale well
For this and other use cases we need something more robust like
in many packages, a user-customizable eglot-mode-line-format. You
can e.g. use flymake-mode-like-format as an idea. Of course,
the default value of eglot-mode-line-format would keep the
Eglot mode-line exactly as it is.
The default value would be something like
("[" eglot-mode-line-menu ":" eglot-mode-line-project-name
eglot-mode-line-outstanding-requests "]")
To fix this problem, users would just remove eglot-project-name from the var
Many users want to get rid of the number of outstanding requests, this
would help them too.
Yet other users want to put the eglot mode-line menu somewhere else but
without the brackets. You get the idea.
Here's the Flymake default value, btw.
João
flymake-mode-line-format is a variable defined in `flymake.el'.
Its value is
(" " flymake-mode-line-exception flymake-mode-line-counters)
Mode line construct for customizing Flymake information.
This variable may be risky if used as a file-local variable.
You can customize this variable.
Probably introduced at or before Emacs version 28.1.
[back]
next prev parent reply other threads:[~2024-06-28 17:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 14:13 bug#71823: 31.0.50; project-mode-line and eglot duplicate project-name in mode-line Spencer Baugh
2024-06-28 14:15 ` Spencer Baugh
2024-06-28 14:40 ` Eli Zaretskii
2024-06-28 17:49 ` João Távora [this message]
2024-06-28 22:08 ` Spencer Baugh
2024-06-29 7:12 ` Eli Zaretskii
2024-06-29 11:59 ` Dmitry Gutov
2024-06-29 12:43 ` Eli Zaretskii
2024-06-30 6:50 ` Juri Linkov
2024-06-30 10:25 ` João Távora
2024-06-29 12:05 ` João Távora
2024-06-29 12:17 ` Dmitry Gutov
2024-06-29 12:21 ` João Távora
2024-06-29 12:41 ` Spencer Baugh
2024-06-29 14:24 ` Spencer Baugh
2024-06-30 0:25 ` João Távora
2024-06-30 12:51 ` sbaugh
2024-06-30 14:53 ` João Távora
2024-06-30 15:05 ` João Távora
2024-07-03 13:17 ` Spencer Baugh
2024-07-03 13:59 ` João Távora
2024-07-03 14:47 ` Spencer Baugh
2024-07-03 14:57 ` João Távora
2024-07-03 15:12 ` Spencer Baugh
2024-07-03 16:03 ` João Távora
2024-07-03 17:10 ` sbaugh
2024-07-05 12:04 ` João Távora
2024-07-15 13:30 ` Spencer Baugh
2024-06-30 16:38 ` Juri Linkov
2024-07-03 13:00 ` Spencer Baugh
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=CALDnm53aooQJgdYGR3HU89jMeAZVS-8TkD133eL6ttJNZuueKA@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=71823@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=sbaugh@janestreet.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).