From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
40573@debbugs.gnu.org, Juri Linkov <juri@linkov.net>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#40573: 27.0.90; flymake-mode broken in scratch buffer
Date: Sat, 18 Apr 2020 12:57:19 +0100 [thread overview]
Message-ID: <CALDnm51odquLTCkyKgKBKkdyb7FThcJwzQCV0L6MQYjg7LvRGQ@mail.gmail.com> (raw)
In-Reply-To: <835zdxaw60.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2166 bytes --]
On Sat, Apr 18, 2020 at 12:08 PM Eli Zaretskii <eliz@gnu.org> wrote:
> It isn't internal judging by its symbol, so it would be good not to
> break compatibility, I think.
Most of the code in Emacs doesn't follow the -- naming convention,
yet. There are no mentions to it in ELPA.
But indeed I've found some code in SLIME and SLY that uses it.
I know the maintainers of these packages well (one of them is
me) and will ensure there is no impact.
> > Do you want me to do either of these 2 things?
> If it isn't infeasible, please do.
OK.
> > I just thought it was simpler to add the cookie. What's
> > the problem with that?
> Existing files was what I had in mind.
OK. I admit I don't care much about those, but why not...
> > 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".
> 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.
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,
contradicting the advice near auto-mode-alist. And the only way
we to safely do that add-to-list is to do it from :set directives
in the defcustom definition that mutates the auto-mode-alist
variable. If it's as complicated as I this, I don't think it's worth it.
So, while I don't oppose doing this, if you really insist I'd
appreciate you tell me how to do it or what you had in mind.
> > If you do use and know some of these files, I think I've shown
> > how trivial it is to make them use lisp-data-mode.
>
> Sorry, I don't have time to do that research for now. Hopefully,
> someone else will be able to do that.
Yes, let's be hopeful, though I don't yet know who cares about
this completeness as much as you.
--
João Távora
[-- Attachment #2: Type: text/html, Size: 2971 bytes --]
next prev parent reply other threads:[~2020-04-18 11:57 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
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 [this message]
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=CALDnm51odquLTCkyKgKBKkdyb7FThcJwzQCV0L6MQYjg7LvRGQ@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=40573@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--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).