all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: 48747@debbugs.gnu.org
Subject: bug#48747: add project-name generic
Date: Sun, 20 Nov 2022 14:17:34 -0800	[thread overview]
Message-ID: <86o7t1l18h.fsf@stephe-leake.org> (raw)
In-Reply-To: <86eedoi0jw.fsf@stephe-leake.org>

eglot provides a use case:

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. For example, I have
two worktrees of my wisitoken project, one for the main branch, one for
a work branch. The eglot names, and the ones I'd like to see, are:

    default     desired
    "build"     "wisitoken main"
    "build"     "wisitoken work"

Similarly, the name for the ada_language_server worktree is:

    "gnat"      "als main"

I could override project-name that in my projects to provide my desired
name, and eglot will use my desired name.

-- 
-- Stephe





  parent reply	other threads:[~2022-11-20 22:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30 17:38 bug#48747: 28.0.50; add project-name generic Stephen Leake
2021-06-07  2:08 ` Dmitry Gutov
2022-07-15 11:48   ` Lars Ingebrigtsen
2022-07-15 13:09     ` Stephen Leake
2022-11-20 22:17 ` Stephen Leake [this message]
2022-11-20 22:57   ` bug#48747: " Dmitry Gutov
2022-11-21 18:59     ` bug#48747: [SPAM UNSURE] " Stephen Leake
2022-11-22  2:41       ` Dmitry Gutov
2022-11-22 19:02         ` Stephen Leake
2022-11-22 22:20           ` 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=86o7t1l18h.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=48747@debbugs.gnu.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 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.