From: Eli Zaretskii <eliz@gnu.org>
To: Theodor Thornhill <theo@thornhill.no>
Cc: 41955@debbugs.gnu.org
Subject: bug#41955: 28.0.50; Monorepos and project.el
Date: Sat, 20 Jun 2020 11:57:26 +0300 [thread overview]
Message-ID: <838sgiw1vt.fsf@gnu.org> (raw)
In-Reply-To: <Ed9I89QkskISV86k-O7_c1f2nFXIk42rFr2ksodmPbq6Is4Njp4xp4osamAFr2tCQHlWrGHaq5QeWvr12uKOBJ2okquU6dyRWCwvj8PrFYc=@thornhill.no> (message from Theodor Thornhill on Sat, 20 Jun 2020 07:48:53 +0000)
> Date: Sat, 20 Jun 2020 07:48:53 +0000
> From: Theodor Thornhill <theo@thornhill.no>
> Cc: 41955@debbugs.gnu.org
>
> Would it help to have facilities of specifying the files in a project
> by starting with an empty project, and then adding the files one by
> one? Also, to be able to say that all the files in a given directory
> (optionally, only files that match some shell wildcard), recursively,
> should be added to a project?
>
> Yeah! I actually suggested something like that. However, this will not fix the issue with programs looking for a
> specific directory for root. Such as eglot and whatever-language-server.
They will need to learn to use the facilities we provide to define a
project in terms other than just the root directory.
next prev parent reply other threads:[~2020-06-20 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 20:42 bug#41955: 28.0.50; Monorepos and project.el Theodor Thornhill
2020-06-20 7:17 ` Eli Zaretskii
2020-06-20 7:48 ` Theodor Thornhill
2020-06-20 8:57 ` Eli Zaretskii [this message]
2020-06-21 1:25 ` Dmitry Gutov
2020-06-22 17:17 ` Felician Nemeth
2020-06-22 21:06 ` Dmitry Gutov
2020-06-20 23:29 ` Juri Linkov
2020-06-21 1:23 ` Dmitry Gutov
2020-06-21 1:48 ` 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=838sgiw1vt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=41955@debbugs.gnu.org \
--cc=theo@thornhill.no \
/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).