all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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: Tue, 02 Apr 2024 16:03:23 +0200	[thread overview]
Message-ID: <874jcjeuac.fsf@gmail.com> (raw)
In-Reply-To: <86msqc9dsa.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 02 Apr 2024 14:58:45 +0300")

On Tue,  2 Apr 2024 at 14:58, Eli Zaretskii wrote:

> It doesn't sound right to me to do that by default, since comint is
> used for shell-like interpreters, and those tend to change directories
> at will.  Which means that dir-locals for some random directory
> doesn't necessarily take such modes into consideration.

This observation makes sense, but it mostly applies to the good old
'M-x shell', not to 'M-x project-shell', other language interpreters, or
to compilation buffers.

By the way, I now realize that 'M-x compile' doesn't use comint-mode
by default.  Which raises the same question: should compilation-mode
call hack-dir-local-variables-non-file-buffer?

> If you need that for some particular use case, can't you call it from
> comint-mode-hook or something?

Sure, it's an easy customization, but the question is whether it's the
expected default behavior. :-)





  reply	other threads:[~2024-04-02 14:03 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 [this message]
2024-04-02 15:11     ` Eli Zaretskii
2024-04-14  9:16       ` Augusto Stoffel
2024-04-14 10:08         ` Eli Zaretskii
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

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

  git send-email \
    --in-reply-to=874jcjeuac.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=70136@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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.