[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hac
From: |
Eli Zaretskii |
Subject: |
bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer |
Date: |
Wed, 17 Apr 2024 21:18:47 +0300 |
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: arstoffel@gmail.com, 70136@debbugs.gnu.org
> Date: Wed, 17 Apr 2024 13:55:55 -0400
>
> >> That commit I referred to had AFAICT the same effect as the one
> >> discussed here: it made some modes (diff-mode, log-edit-mode, and a few
> >> more) obey dir-locals whereas they didn't before.
> >> And dir-locals existed since several years before that.
> >>
> >> Why would it be more likely for them to have .dir-locals which
> >> accidentally affect grep-mode than diff-mode/log-edit-mode/...?
> >>
> >> AFAICT it risked the exact same backward compatibility problems.
> >
> > So we should risk it again?
>
> Well, that risk paid off because by all accounts it seems that noone
> suffered (and some people benefited), so that argues in favor of taking
> that risk again.
That's not the kind of risk management and mitigation that I'm used
to. It's like saying "crossing that junction on red light went well
and paid off, so let's risk that again on this next junction".
- bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer, (continued)
- 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
- bug#70436: 30.0.50; Fail to enter the debugger when using prin1 (instead of cl-prin1), Bruno Barbier, 2024/04/17
- bug#70436: 30.0.50; Fail to enter the debugger when using prin1 (instead of cl-prin1), Eli Zaretskii, 2024/04/20
- bug#70436: 30.0.50; Fail to enter the debugger when using prin1 (instead of cl-prin1), Eli Zaretskii, 2024/04/20
- bug#70436: 30.0.50; Fail to enter the debugger when using prin1 (instead of cl-prin1), Stefan Monnier, 2024/04/20
- bug#70436: 30.0.50; Fail to enter the debugger when using prin1 (instead of cl-prin1), Stefan Monnier, 2024/04/20
- 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
- bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer, Stefan Monnier, 2024/04/17
- 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
- bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer, Stefan Monnier, 2024/04/17
- bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer,
Eli Zaretskii <=
- bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer, Stefan Monnier, 2024/04/17
- bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer, Juri Linkov, 2024/04/16
- bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer, Eli Zaretskii, 2024/04/16
- bug#70136: 30.0.50; compilation-mode [was: comint-mode] doesn't call hack-dir-local-variables-non-file-buffer, Augusto Stoffel, 2024/04/17
- 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