GNU bug report logs -
#66405
30.0.50; Should comint-mode call hack-dir-local-variables-non-file-buffer?
Previous Next
To reply to this bug, email your comments to 66405 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66405
; Package
emacs
.
(Sun, 08 Oct 2023 10:17:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Augusto Stoffel <arstoffel <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 08 Oct 2023 10:17:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
It currently doesn't but I think it should, since a comint is
conceptually tied to the current directory.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66405
; Package
emacs
.
(Sun, 08 Oct 2023 10:29:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 66405 <at> debbugs.gnu.org (full text, mbox):
> From: Augusto Stoffel <arstoffel <at> 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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66405
; Package
emacs
.
(Sun, 08 Oct 2023 11:05:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 66405 <at> debbugs.gnu.org (full text, mbox):
On Sun, 8 Oct 2023 at 13:27, Eli Zaretskii wrote:
>> From: Augusto Stoffel <arstoffel <at> 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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66405
; Package
emacs
.
(Sun, 08 Oct 2023 11:44:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 66405 <at> debbugs.gnu.org (full text, mbox):
> From: Augusto Stoffel <arstoffel <at> gmail.com>
> Cc: 66405 <at> 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 <at> 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?
This bug report was last modified 1 year and 46 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.