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 18:46:43 +0300 [thread overview]
Message-ID: <83v9lyazdo.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm520iiaJfJmNfwSE6sDD4Ph-HaaJtuoV0d7ueALdCJOOiA@mail.gmail.com> (message from João Távora on Fri, 17 Apr 2020 16:35:14 +0100)
> From: João Távora <joaotavora@gmail.com>
> Date: Fri, 17 Apr 2020 16:35:14 +0100
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Juri Linkov <juri@linkov.net>, 40573@debbugs.gnu.org,
> Dmitry Gutov <dgutov@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.
> Once again, I don't want us to have a mode for .dir-locals.el files
> alone. How many times do I have to say that before you understand?
>
> Look Eli, there's no reason to be unpleasant, OK???
I'm not being more unpleasant than you are.
> And you didn't refute ANY of my arguments. You just say you
> don't want something to handle just one file. I and others point
> to you it can be used for more files and YOU ignore it.
>
> So let's get that straight, and let's let this rest for a while.
I already had that straight, more than once. Please respect my
opinions on this. They are expressed in very clear words.
next prev parent reply other threads:[~2020-04-17 15:46 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v9lyazdo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).