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

Previous Next

Full log

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

From: João Távora <joaotavora <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 40573 <at> debbugs.gnu.org, Dmitry Gutov <dgutov <at> yandex.ru>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>, Juri Linkov <juri <at> linkov.net>
Subject: Re: bug#40573: 27.0.90; flymake-mode broken in scratch buffer
Date: Fri, 17 Apr 2020 16:55:07 +0100

[Message part 1 (text/plain, inline)]

On Fri, Apr 17, 2020 at 4:46 PM Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: João Távora <joaotavora <at> gmail.com>
> > Date: Fri, 17 Apr 2020 16:35:14 +0100
> > Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>, Juri Linkov <
> juri <at> linkov.net>, 40573 <at> debbugs.gnu.org,
> >       Dmitry Gutov <dgutov <at> yandex.ru>
> >
> >  > Which code?
> >
> >  The code of the proposed new mode.
> >
> > That has been shown already by Stefan's patch, way back.
>
> And I already rejected it.  If we want to have a mode, let's have a
> mode, to support all the good features discussed lately here.  Like a
> lighter, code that injects the mode into auto-generated files and
> turns on automatically for non-generated ones, etc.  A clean job, IOW.


Can you explain what is dirty about having that mode for a subset
of files that _could_ make use of it and having the user select
it via M-x lisp-data-mode when he thinks it's useful? Can you give
evidence of any benefit to your all-or-nothing stance here?

I've explained, many times, that turning it on automatically for
non-generated files, is impossible to achieve.  Do you disagree
with this statement?  Maybe you do, perhaps you're seeing
something I don't or we're talking about different lisp-data-mode's.

João

[Message part 2 (text/html, inline)]

Previous Next

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