[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: |
Sat, 18 Apr 2020 15:35:27 +0300 |
> From: João Távora <joaotavora@gmail.com>
> Date: Sat, 18 Apr 2020 12:57:19 +0100
> Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, Stefan Monnier
> <monnier@iro.umontreal.ca>,
> Juri Linkov <juri@linkov.net>, 40573@debbugs.gnu.org, Dmitry Gutov
> <dgutov@yandex.ru>
>
> > > Anyway, I can surely switch to auto-mode-alist if you
> > > insist, no problem. Do you insist in this?
> > Do I have to insist?
>
> Any problem with doing so? I'll interpret that as a "Yes".
It's actually the other way around: if I don't feel my opinion is
strong enough, I usually say so.
> > In any case, I didn't mean to use auto-mode-alist _instead_ odf adding
> > the cookie automatically, I meant to do it in addition.
>
> Ah, indeed I had misunderstood you. But what's the point
> in having them also in the cookies then? That bit escapes me.
The cookies will take care of newly created/rewritten files,
auto-mode-alist will take care of existing ones that no one has
changed yet. The result is a more complete coverage of the involved
files.
> Anyway, I went and looked at the three files you mention, and
> I discovered they're not "fixed" as I thought. They're defcustom
> and defined way after auto-mode-alist, so we'd have to add-to-list,
No need for such complexity. I meant to mention the standard names in
auto-mode-alist, under the assumption that many/most users don't
change the default names.
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, (continued)
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/17
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/17
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/17
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/17
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/17
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/18
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/18
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/18
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/18
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/18
- 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/18
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/18
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Dmitry Gutov, 2020/04/18
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/19
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Dmitry Gutov, 2020/04/19
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/19
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Dmitry Gutov, 2020/04/19
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Stefan Monnier, 2020/04/18
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, Eli Zaretskii, 2020/04/19
- bug#40573: 27.0.90; flymake-mode broken in scratch buffer, João Távora, 2020/04/19