From: Eli Zaretskii <eliz@gnu.org>
To: Len Trigg <lenbok@gmail.com>
Cc: 59868@debbugs.gnu.org
Subject: bug#59868: 28.2.50; compilation-search-path incompatible with dir-locals
Date: Sat, 10 Dec 2022 16:02:00 +0200 [thread overview]
Message-ID: <83tu23we5j.fsf@gnu.org> (raw)
In-Reply-To: <CAOGVwemGXC+4zbCVffGtVNvq_fMHbOradu+eXQxq7-HunGFn_w@mail.gmail.com> (message from Len Trigg on Sat, 10 Dec 2022 08:11:10 +1300)
> From: Len Trigg <lenbok@gmail.com>
> Date: Sat, 10 Dec 2022 08:11:10 +1300
> Cc: 59868@debbugs.gnu.org
>
> You are ignoring the first sentence in my response, right?
>
> I don't think so - the purpose of my email was essentially to ask why you thought the variable shouldn't be
> buffer-local in *compilation* buffers.
Because from the pattern we use the *compilation* buffer it is clear
that it cannot be buffer-local. The *compilation* buffer is reused by
each new compilation, so local setting there makes no sense.
> In my specific case the project is in R (which is a terrible language for software development) and we are
> using a single top level makefile in the project. It has a target to run linting, which (within each R linter
> invocation) lints from a subdirectory, and the filenames in each lint message are relative to those
> directories. There is not the hierarchy of makefiles that you would often see in say C projects, where
> compilation mode could parse make-issued messages about changing directories etc. It seemed a perfect
> fit for compilation-search-path. I am currently working around it with the following ugliness in my
> .dir-locals.el:
Why cannot you have all the possible directories in the list?
next prev parent reply other threads:[~2022-12-10 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 1:56 bug#59868: 28.2.50; compilation-search-path incompatible with dir-locals Len Trigg
2022-12-07 13:01 ` Eli Zaretskii
[not found] ` <CAOGVwekSSS5+FPecNxdm7TFzXoweB+4jvaKD7z72o0+e25byuA@mail.gmail.com>
2022-12-09 7:06 ` Eli Zaretskii
2022-12-09 19:11 ` Len Trigg
2022-12-10 14:02 ` Eli Zaretskii [this message]
2022-12-10 22:01 ` Len Trigg
2022-12-11 7:14 ` 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
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=83tu23we5j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59868@debbugs.gnu.org \
--cc=lenbok@gmail.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).