all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: "João Távora" <joaotavora@gmail.com>, "Eli Zaretskii" <eliz@gnu.org>
Cc: Ergus <spacibba@aol.com>, 70408@debbugs.gnu.org
Subject: bug#70408: 30.0.50; Eglot and Project integration
Date: Tue, 16 Apr 2024 15:55:56 +0300	[thread overview]
Message-ID: <8cfba95b-fedd-4b5f-9778-d656601006d1@gutov.dev> (raw)
In-Reply-To: <CALDnm52cp2Mn2YQtK+jh+Pgq0BJMK4BRf1oiDF+8cGuxsUfPvg@mail.gmail.com>

Hi Joao,

On 16/04/2024 15:33, João Távora wrote:
> On Tue, Apr 16, 2024 at 12:42 PM Eli Zaretskii<eliz@gnu.org>  wrote:
> 
>> I think this discussion should include João, so I added him.
> Alright.
> 
> More importantly, I think this discussion should include Dmitry, as this seems
> to me a project.el extension.
> 
> This discussion should be aware of these half-recent developments
> https://github.com/joaotavora/eglot/discussions/1337
> 
> In a few words, Eglot user's main gripe with project.el is project.el's
> inability to help the user define or designate subprojects within
> larger projects.

IIUC Ergus's request is primarily about a situation where an 
"out-of-tree" build is used. Meaning, the directory for build artefacts 
is not a subdirectory of the project root, but -- apparently -- some 
sibling directory of it (e.g. "../build"). So it's somewhat atypical, 
although I suppose the solution from the link above might work with it too.

This bug is split off from an emacs-devel discussion, where I posted a 
draft solution of mine: 
https://lists.gnu.org/archive/html/emacs-devel/2024-04/msg00279.html

I'm curious for any feedback - like would that be good enough for this 
and related cases, or maybe if someone has an even simpler approach in mind.





  reply	other threads:[~2024-04-16 12:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o7aas3sk.fsf.ref@aol.com>
2024-04-15 21:40 ` bug#70408: 30.0.50; Eglot and Project integration Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 11:42   ` Eli Zaretskii
2024-04-16 12:33     ` João Távora
2024-04-16 12:55       ` Dmitry Gutov [this message]
2024-04-16 13:51         ` João Távora
2024-04-16 16:02           ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 20:30             ` João Távora
2024-04-16 21:51               ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-20 11:28           ` Dmitry Gutov
2024-04-20 13:10             ` João Távora
2024-04-16 13:03       ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 16:36       ` Eli Zaretskii

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=8cfba95b-fedd-4b5f-9778-d656601006d1@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=70408@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=spacibba@aol.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.