all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Wed, 07 Dec 2022 15:01:17 +0200	[thread overview]
Message-ID: <83y1rj4bc2.fsf@gnu.org> (raw)
In-Reply-To: <CAOGVwemtXe8b+byh5Lf7zg_NoLziV7puxrZf9j_eM0JFrDX-wA@mail.gmail.com> (message from Len Trigg on Wed, 7 Dec 2022 14:56:25 +1300)

severity 59868 wishlist
thanks

> From: Len Trigg <lenbok@gmail.com>
> Date: Wed, 7 Dec 2022 14:56:25 +1300
> 
> The compilation-search-path variable purports to let the user specify a
> list of directories to search when resolving file names found in
> compilation error messages. As such this very much should be possible to
> specify as a project-specific setting. However, setting this variable in
> per-project .dir-locals.el file does not work. When a compilation buffer
> is created, the local value is not obeyed (I have my dir locals file setting
> this variable regardless of the major mode, and I see the variable being
> set in regular modes just fine - it seems to be just compilation mode with
> the problem). I am not an expert, but it may be due to compilation mode
> calling kill-all-local-variables that prevents this from working as expected.

I don't think this variable is meant to be buffer-local in
*compilation* buffers.  If project.el wants to provide a project-local
value for this search path, it should define a new variable for that,
and then compilation-mode can set its own variable from that.





  reply	other threads:[~2022-12-07 13:01 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 [this message]
     [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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y1rj4bc2.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 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.