From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 66405@debbugs.gnu.org
Subject: bug#66405: 30.0.50; Should comint-mode call hack-dir-local-variables-non-file-buffer?
Date: Sun, 08 Oct 2023 14:42:34 +0300 [thread overview]
Message-ID: <83lecdxrv9.fsf@gnu.org> (raw)
In-Reply-To: <87edi5nzp8.fsf@gmail.com> (message from Augusto Stoffel on Sun, 08 Oct 2023 13:03:31 +0200)
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: 66405@debbugs.gnu.org
> Date: Sun, 08 Oct 2023 13:03:31 +0200
>
> On Sun, 8 Oct 2023 at 13:27, Eli Zaretskii wrote:
>
> >> From: Augusto Stoffel <arstoffel@gmail.com>
> >> Date: Sun, 08 Oct 2023 12:16:07 +0200
> >>
> >> It currently doesn't but I think it should, since a comint is
> >> conceptually tied to the current directory.
> >
> > Is there a compelling reason why it should (as opposed to a "why not"
> > kind of reason)? Comint exists for many years, so any change in
> > behavior there should have a very good reason.
>
> Yes. We've been improving the editing experience in Comint with input
> fontification and what not, so I think it should also have the right
> project settings. Indentation settings would be one example. Also,
> documentation lookup settings often go in the .dir-locals.el and are
> relevant in a comint as well.
>
> For me personally, it would also make
> https://elpa.gnu.org/packages/buffer-env.html work more smoothly.
So what's our plan for when this happens to break something?
prev parent reply other threads:[~2023-10-08 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 10:16 bug#66405: 30.0.50; Should comint-mode call hack-dir-local-variables-non-file-buffer? Augusto Stoffel
2023-10-08 10:27 ` Eli Zaretskii
2023-10-08 11:03 ` Augusto Stoffel
2023-10-08 11:42 ` Eli Zaretskii [this message]
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=83lecdxrv9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66405@debbugs.gnu.org \
--cc=arstoffel@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).