GNU bug report logs - #40573
27.0.90; flymake-mode broken in scratch buffer

Previous Next

Package: emacs;

Reported by: João Távora <joaotavora <at> gmail.com>

Date: Sun, 12 Apr 2020 13:20:02 UTC

Severity: normal

Found in version 27.0.90

Done: João Távora <joaotavora <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #26 received at 40573 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: João Távora <joaotavora <at> gmail.com>
Cc: 40573 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>, Dmitry Gutov <dgutov <at> yandex.ru>
Subject: Re: bug#40573: 27.0.90; flymake-mode broken in scratch buffer
Date: Mon, 13 Apr 2020 02:58:07 +0300
> The only intention I have is to revert the commit you added,
> add an emacs-lisp-data-mode according to Stefan's and Dmitry's
> suggestion, and use that mode for .dir-local.el. I'd also appreciate
> such a mode for other lispy data files I have. Anyway, last time
> I checked, you opposed this (very?) strongly so unless that stance 
> has changed, there's not much for me to work on.

Please add emacs-lisp-data-mode.  I have data buffers in emacs-lisp mode
permanently visited all the time, and in the Buffer List the modes
of these buffers "ELisp/d" are highlighted with the warning face.

It's fine to encourage the users to convert emacs-lisp files
from dynamic (the suffix "/d" in mode name highlighted as a warning)
to lexical (the suffix "/l" unhighlighted).

But the problem is that these files are emacs-lisp data files,
they can't be converted to lexical-binding, they need a special data mode.




This bug report was last modified 5 years and 25 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.