From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 40573@debbugs.gnu.org, juri@linkov.net, monnier@iro.umontreal.ca,
dgutov@yandex.ru
Subject: bug#40573: 27.0.90; flymake-mode broken in scratch buffer
Date: Fri, 17 Apr 2020 14:49:00 +0300 [thread overview]
Message-ID: <837dyecoyb.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm509VNgcO51azYxwUyDH_M+buUZDHd-7SC8Kd2V0C3MeBw@mail.gmail.com> (message from João Távora on Fri, 17 Apr 2020 11:21:50 +0100)
> From: João Távora <joaotavora@gmail.com>
> Date: Fri, 17 Apr 2020 11:21:50 +0100
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Juri Linkov <juri@linkov.net>, 40573@debbugs.gnu.org,
> Dmitry Gutov <dgutov@yandex.ru>
>
> So I'm thinking of introducing lisp-data-mode later on in
> master, following Stefan's patch. And using it only for `dir-locals.el`
> for now (and for my own files of course).
>
> Is that OK with you?
No. IMO a mode included in the core should handle more that just one
kind of file. We've been through this, at least twice. Why do you
keep pushing? It only adds to aggravation.
next prev parent reply other threads:[~2020-04-17 11:49 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 13:18 bug#40573: 27.0.90; flymake-mode broken in scratch buffer João Távora
2020-04-12 13:48 ` Eli Zaretskii
2020-04-12 14:24 ` João Távora
2020-04-12 14:44 ` Eli Zaretskii
2020-04-12 17:02 ` João Távora
2020-04-12 17:17 ` Eli Zaretskii
2020-04-12 17:50 ` João Távora
2020-04-12 23:58 ` Juri Linkov
2020-04-13 4:36 ` Eli Zaretskii
2020-04-13 23:17 ` Juri Linkov
2020-04-14 5:51 ` Eli Zaretskii
2020-04-14 8:48 ` João Távora
2020-04-14 11:29 ` Eli Zaretskii
2020-04-14 11:48 ` João Távora
2020-04-14 12:38 ` Eli Zaretskii
2020-04-14 12:56 ` João Távora
2020-04-14 15:42 ` Eli Zaretskii
2020-04-14 16:42 ` João Távora
2020-04-14 20:05 ` Stefan Monnier
2020-04-16 21:43 ` Juri Linkov
2020-04-16 23:06 ` Stefan Monnier
2020-04-17 6:49 ` Eli Zaretskii
2020-04-17 10:07 ` João Távora
2020-04-17 10:12 ` Eli Zaretskii
2020-04-17 10:21 ` João Távora
2020-04-17 11:49 ` Eli Zaretskii [this message]
2020-04-17 11:57 ` João Távora
2020-04-17 13:05 ` Eli Zaretskii
2020-04-17 15:20 ` João Távora
2020-04-17 15:28 ` Eli Zaretskii
2020-04-17 15:35 ` João Távora
2020-04-17 15:46 ` Eli Zaretskii
2020-04-17 15:55 ` João Távora
2020-04-17 17:19 ` Eli Zaretskii
2020-04-18 8:26 ` João Távora
2020-04-18 9:28 ` Eli Zaretskii
2020-04-18 10:03 ` João Távora
2020-04-18 11:08 ` Eli Zaretskii
2020-04-18 11:57 ` João Távora
2020-04-18 12:35 ` Eli Zaretskii
2020-04-18 15:10 ` João Távora
2020-04-18 23:36 ` João Távora
2020-04-19 0:05 ` Dmitry Gutov
2020-04-19 9:25 ` João Távora
2020-04-19 13:57 ` Dmitry Gutov
2020-04-19 16:31 ` João Távora
2020-04-19 16:38 ` Dmitry Gutov
2020-04-19 2:44 ` Stefan Monnier
2020-04-19 14:01 ` Eli Zaretskii
2020-04-19 20:17 ` João Távora
2020-04-20 13:41 ` Eli Zaretskii
2020-04-20 14:02 ` João Távora
2020-04-20 16:05 ` Eli Zaretskii
2020-05-01 11:10 ` João Távora
2020-04-18 11:55 ` Basil L. Contovounesios
2020-04-18 12:03 ` João Távora
2020-04-19 0:20 ` Basil L. Contovounesios
2020-04-19 11:41 ` João Távora
2020-04-18 23:42 ` Juri Linkov
2020-04-19 9:16 ` João Távora
2020-04-17 14:44 ` Basil L. Contovounesios
2020-04-17 16:04 ` Stefan Monnier
2020-04-17 6:23 ` Eli Zaretskii
2020-04-18 23:36 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837dyecoyb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40573@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=joaotavora@gmail.com \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.