From: Spencer Baugh <sbaugh@janestreet.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: Dmitry Gutov <dmitry@gutov.dev>,
sbaugh@catern.com, Eli Zaretskii <eliz@gnu.org>,
71823@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#71823: 31.0.50; project-mode-line and eglot duplicate project-name in mode-line
Date: Mon, 15 Jul 2024 09:30:21 -0400 [thread overview]
Message-ID: <ierjzhmvl3m.fsf@janestreet.com> (raw)
In-Reply-To: <874j94gi4g.fsf@gmail.com> ("João Távora"'s message of "Fri, 05 Jul 2024 13:04:15 +0100")
João Távora <joaotavora@gmail.com> writes:
> sbaugh@catern.com writes:
>
>> To be clear, I want a configuration which will have project-name from
>> project-mode-line and no project-name in the eglot mode-line entry.
>
> I understand.
>
>> So that functionality will need to be moved anyway, no matter how we
>> solve this problem.
>
> As I see it (now, not 2 weeks ago) only if the user wants the same as
> you. The reason I changed my mind is that I hadn't realized that section
> was being used for the server-specific menu.
>
>> Are you fine with including the server menu in the main menu? This is
>> something we'd want in both the "make it work by default" or "make it
>> customizable" solutions.
>
> No, I'm not sure of that. One of the reasons is that Eglot currently
> supports only one server, but there are many requests for it to support
> more than one in the future. So I'm not sure that's such a good move,
> whereas if the user decides they don't need the server menu, that's a
> different story.
I see. What about putting an abbreviated server name in the eglot
modeline, replacing the current project-name? That would fit better
with supporting multiple servers anyway: there would be multiple entries
for multiple servers.
I'm not sure what a good source for an abbreviated server name would
be... perhaps we could query something from the LSP server, or put it in
eglot-server-programs?
next prev parent reply other threads:[~2024-07-15 13:30 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
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 [this message]
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=ierjzhmvl3m.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=71823@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--cc=juri@linkov.net \
--cc=sbaugh@catern.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).