[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#40573: 27.0.90; flymake-mode broken in scratch buffer
From: |
Eli Zaretskii |
Subject: |
bug#40573: 27.0.90; flymake-mode broken in scratch buffer |
Date: |
Tue, 14 Apr 2020 08:51:28 +0300 |
> From: Juri Linkov <juri@linkov.net>
> Cc: joaotavora@gmail.com, 40573@debbugs.gnu.org, monnier@iro.umontreal.ca,
> dgutov@yandex.ru
> Date: Tue, 14 Apr 2020 02:17:11 +0300
>
> These files need font-locking from emacs-lisp-mode for viewing, and other
> features of emacs-lisp-mode for editing: indentation, commenting, etc.
> i.e. everything from emacs-lisp-mode except code evaluation. This is
> one difference between emacs-lisp-data-mode and emacs-lisp-mode.
>
> Another difference is that distinction between dynamic/lexical binding
> makes no sense for ELisp data files. It's wrong to use "ELisp/d" as
> a mode name for ELisp data files where "/d" indicates dynamic binding.
What do you propose to show as the mode-lighter instead?
> http://git.savannah.nongnu.org/cgit/ee.git/tree/ee-datafile.el
> currently assigns emacs-lisp-mode:
>
> (add-to-list 'auto-mode-alist '("\\.ee\\'" . emacs-lisp-mode))
>
> but could use emacs-lisp-data-mode instead:
>
> (add-to-list 'auto-mode-alist '("\\.ee\\'" . emacs-lisp-data-mode))
>
> There are many other examples of ELisp data files. One is already
> mentioned .dir-locals.el that needs editing features from
> emacs-lisp-mode (indentation, commenting, ...) as well,
> but doesn't need the dynamic/lexical distinction.
How would you propose to identify these files for turning on this
special mode? They don't seem to have a clear-cut set of extensions
and/or file names.
Thanks for the other details, I think this is very useful.
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/12
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/12
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/12
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Juri Linkov, 2020/04/12
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/13
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Juri Linkov, 2020/04/13
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer,
Eli Zaretskii <=
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/14
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/14
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/14
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/14
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/14
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/14
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/14
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Stefan Monnier, 2020/04/14
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Juri Linkov, 2020/04/16
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Stefan Monnier, 2020/04/16