[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#66317: Project mode-line
From: |
Eli Zaretskii |
Subject: |
bug#66317: Project mode-line |
Date: |
Mon, 16 Oct 2023 22:12:19 +0300 |
> Cc: sbaugh@catern.com, 66317@debbugs.gnu.org
> From: Juri Linkov <juri@linkov.net>
> Date: Mon, 16 Oct 2023 20:01:36 +0300
>
> There is another problem: calling 'project-name' while evaluating
> 'mode-line-format' often changes the coding system mode-line indicator
> from U (utf-8) to raw-text during saving the current buffer.
>
> Here is a backtrace:
>
> - project-name
> - project--value-in-dir (that uses with-temp-buffer)
> - hack-dir-local-variables-non-file-buffer
> - hack-local-variables-apply
>
> Then in the last function the coding system is broken
> in two different ways:
>
> 1. by 'hack-one-local-variable' in `emacs -Q`
How and where?
> 2. by (run-hooks 'hack-local-variables-hook)
> in buffers where flyspell-mode is enabled
> 'flyspell-hack-local-variables-hook' breaks
> the coding system too.
Why?
bug#66317: Project mode-line, Stefan Kangas, 2023/10/03
bug#66317: Project mode-line, sbaugh, 2023/10/15
- bug#66317: Project mode-line, Dmitry Gutov, 2023/10/15
- bug#66317: Project mode-line, Juri Linkov, 2023/10/16
- bug#66317: Project mode-line,
Eli Zaretskii <=
- bug#66317: Project mode-line, Juri Linkov, 2023/10/18
- bug#66317: Project mode-line, Dmitry Gutov, 2023/10/18
- bug#66317: Project mode-line, Juri Linkov, 2023/10/19
- bug#66317: Project mode-line, Dmitry Gutov, 2023/10/19
- bug#66317: Project mode-line, Juri Linkov, 2023/10/23
- bug#66317: Project mode-line, Dmitry Gutov, 2023/10/24
bug#66317: Project mode-line, Dmitry Gutov, 2023/10/18