From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 70136@debbugs.gnu.org, spacibba@aol.com
Subject: bug#70136: 30.0.50; comint-mode doesn't call hack-dir-local-variables-non-file-buffer
Date: Sun, 14 Apr 2024 13:08:55 +0300 [thread overview]
Message-ID: <86zftwmf2g.fsf@gnu.org> (raw)
In-Reply-To: <87r0f8cni7.fsf@gmail.com> (message from Augusto Stoffel on Sun, 14 Apr 2024 11:16:48 +0200)
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: 70136@debbugs.gnu.org, spacibba@aol.com
> Date: Sun, 14 Apr 2024 11:16:48 +0200
>
> On Tue, 2 Apr 2024 at 18:11, Eli Zaretskii wrote:
>
> > Maybe. What kind of directory-specific variables relevant to
> > compilation-mode would make sense?
>
> There are some many. To say just the first that comes to mind:
> compilation-error-regexp-alist.
I must say this is not very convincing.
What bothers me is that .dir-locals.el in a directory is not meant for
compilation-mode and similar modes, so settings there that are not
specific to modes could get in the way in *compilation* and "grep*
buffers. But if this is optional behavior, by default off, I don't
think I'd mind.
next prev parent reply other threads:[~2024-04-14 10:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 5:54 bug#70136: 30.0.50; comint-mode doesn't call hack-dir-local-variables-non-file-buffer Augusto Stoffel
2024-04-02 11:58 ` Eli Zaretskii
2024-04-02 14:03 ` Augusto Stoffel
2024-04-02 15:11 ` Eli Zaretskii
2024-04-14 9:16 ` Augusto Stoffel
2024-04-14 10:08 ` Eli Zaretskii [this message]
2024-04-14 9:27 ` bug#70136: 30.0.50; compilation-mode [was: comint-mode] " Augusto Stoffel
2024-04-14 10:21 ` Eli Zaretskii
2024-04-15 17:10 ` Augusto Stoffel
2024-04-15 18:27 ` Eli Zaretskii
2024-04-16 21:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-17 2:34 ` Eli Zaretskii
2024-04-17 2:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-17 8:31 ` Augusto Stoffel
2024-04-17 13:03 ` Eli Zaretskii
2024-04-17 13:29 ` bug#70436: 30.0.50; Fail to enter the debugger when using prin1 (instead of cl-prin1) Bruno Barbier
2024-04-20 8:24 ` Eli Zaretskii
2024-04-20 8:28 ` Eli Zaretskii
2024-04-20 15:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-25 16:37 ` Eli Zaretskii
2024-04-27 10:29 ` Bruno Barbier
2024-04-27 14:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-20 13:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-17 12:36 ` bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer Eli Zaretskii
2024-04-17 12:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-17 13:16 ` Eli Zaretskii
2024-04-17 17:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-17 18:18 ` Eli Zaretskii
2024-04-17 18:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 6:33 ` Juri Linkov
2024-04-16 12:37 ` Eli Zaretskii
2024-04-17 8:16 ` Augusto Stoffel
2024-04-17 13:00 ` Eli Zaretskii
2024-05-02 6:17 ` Juri Linkov
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=86zftwmf2g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70136@debbugs.gnu.org \
--cc=arstoffel@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 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).