From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stephen Leake <stephen_leake@stephe-leake.org>, emacs-devel@gnu.org
Subject: Re: Add cl-defgeneric project-name; first use case eglot
Date: Mon, 21 Nov 2022 13:50:37 +0000 [thread overview]
Message-ID: <87sfica02a.fsf@gmail.com> (raw)
In-Reply-To: <83a64k4fru.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 21 Nov 2022 15:07:49 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stephen Leake <stephen_leake@stephe-leake.org>
>> Cc: João Távora <joaotavora@gmail.com>
>> Date: Sun, 20 Nov 2022 14:09:49 -0800
>>
>> eglot builds a name for a server using the root directory of the
>> project - in effect:
>>
>> (file-name-base (directory-file-name (project-root (project-current))))
>>
>> That name shows up in the elgot mode line, to tell the user which server
>> the buffer is connected to, in progress report messages, and in the name
>> of the EGLOT log buffer, which is useful for debugging things.
>>
>> If the project root directory happens to have a meaningful name, that's
>> fine. In my use cases, it's usually not meaningful.
>
> So Eglot should allow customization of what is shown on the mode line.
Surely Eglot could offer that: a boolean option controlling whether to
show the project's name in the mode-line. Or a more sophisticated
eglot-mode-line-format in the style of e.g. flymake-mode-line-format so
that multiple other things can be shown or hidden.
As to where Eglot gets the project's human-readable name from, I can't
think of a place other than project.el. As Stephen explained, currently
Eglot guesses it from the name of the root directory, and that guess
isn't suitable 100% of the time.
So Stephen's suggestion sounds pretty reasonable to me.
João
next prev parent reply other threads:[~2022-11-21 13:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 22:09 Add cl-defgeneric project-name; first use case eglot Stephen Leake
2022-11-20 22:14 ` [SPAM UNSURE] " Stephen Leake
2022-11-21 0:37 ` Stephen Leake
2022-11-21 13:07 ` Eli Zaretskii
2022-11-21 13:50 ` João Távora [this message]
2022-11-21 14:17 ` Eli Zaretskii
2022-11-21 21:29 ` João Távora
2022-11-22 9:56 ` Kévin Le Gouguec
2022-11-23 2:34 ` Dmitry Gutov
2022-11-23 8:33 ` Juri Linkov
2022-11-23 13:46 ` Dmitry Gutov
2022-11-27 18:47 ` Kévin Le Gouguec
2022-11-28 1:21 ` 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
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=87sfica02a.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.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).