From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#40573: 27.0.90; flymake-mode broken in scratch buffer Date: Sat, 18 Apr 2020 12:57:19 +0100 Message-ID: References: <835ze4lsr1.fsf@gnu.org> <831roslq62.fsf@gnu.org> <87sgh89r78.fsf@mail.linkov.net> <83lfn0j92e.fsf@gnu.org> <87imi39e8w.fsf@mail.linkov.net> <83h7xmipi7.fsf@gnu.org> <878sivdsjn.fsf@mail.linkov.net> <83r1wmd2u0.fsf@gnu.org> <83a73acted.fsf@gnu.org> <837dyecoyb.fsf@gnu.org> <835zdyclfa.fsf@gnu.org> <83zhbab07u.fsf@gnu.org> <83v9lyazdo.fsf@gnu.org> <83r1wmav3h.fsf@gnu.org> <83a739b0sd.fsf@gnu.org> <835zdxaw60.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000dd7d4605a38f5efd" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="12567"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "Basil L. Contovounesios" , 40573@debbugs.gnu.org, Juri Linkov , Stefan Monnier , Dmitry Gutov To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 18 13:58:23 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jPm75-0003B5-AZ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 18 Apr 2020 13:58:23 +0200 Original-Received: from localhost ([::1]:57112 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jPm74-0005Hl-CA for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 18 Apr 2020 07:58:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34668) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jPm6n-0005G0-49 for bug-gnu-emacs@gnu.org; Sat, 18 Apr 2020 07:58:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jPm6k-00037I-6R for bug-gnu-emacs@gnu.org; Sat, 18 Apr 2020 07:58:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58757) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jPm6k-000374-3i for bug-gnu-emacs@gnu.org; Sat, 18 Apr 2020 07:58:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jPm6k-0002eu-0z for bug-gnu-emacs@gnu.org; Sat, 18 Apr 2020 07:58:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 18 Apr 2020 11:58:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 40573 X-GNU-PR-Package: emacs Original-Received: via spool by 40573-submit@debbugs.gnu.org id=B40573.158721105910180 (code B ref 40573); Sat, 18 Apr 2020 11:58:01 +0000 Original-Received: (at 40573) by debbugs.gnu.org; 18 Apr 2020 11:57:39 +0000 Original-Received: from localhost ([127.0.0.1]:42070 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jPm6M-0002e8-Li for submit@debbugs.gnu.org; Sat, 18 Apr 2020 07:57:38 -0400 Original-Received: from mail-il1-f173.google.com ([209.85.166.173]:42248) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jPm6K-0002dU-FB for 40573@debbugs.gnu.org; Sat, 18 Apr 2020 07:57:37 -0400 Original-Received: by mail-il1-f173.google.com with SMTP id t10so4882685ilg.9 for <40573@debbugs.gnu.org>; Sat, 18 Apr 2020 04:57:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LX+Mw7/RnCtOBczq/gnEx0tNwMaibBCztlMJhfkeRM4=; b=Z3YI0W5M4a24x1EpBjUp4aJX2LjyCzpi6IKWkC/rzRbqeSZvDOAcjpZltwss+wYu63 isvk0G7thZ5iwHVc5WfLqrbisKWfgZ4rJgDp8Pdpex1dRaUeoFOipyaJMfE6dbJzbHFs 8UsvmSct8iSG3i7a8Iu9oGoBFxlkn9w6DyiXZXpNAZc9uPLVs8Rco/a/BS/VJVJE826T xk+MKgko6grCzZHawEj1eDgYIoKUqByTv6uoOS16eIXOLpl/VMMMadtplHusUgba6Sde CD2Iq49KtVvetk2DbrfPTFW7jH6AGmPQNJZC9O1ZO7z5/4M4fQVLRSBk64JkSrV4bGeO yd/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LX+Mw7/RnCtOBczq/gnEx0tNwMaibBCztlMJhfkeRM4=; b=OqIUB8YJgm4V/mwvaGT1kLNtBBNqiss9TeIYGZZRoh0kkmyE3oPJ8JiZeq3enuVjqY wfKEDmucZusq8ICGt+thgrgvXaOKftc5lKoGgSXPeH8gyFDr+KKTfRdHUHDxLvNL3wHE a8UJxd3hFGT6vzuo7ia3p/y6+TdfxSQPMK9487RgJlvVk7NmjYDs/ohzqOT9DiP3Mr8v rT3+bsfEYlx0bdm/D2fRSIZVcNfKQHKCfEjgDsheyNR6cRAyv5S56n98vj+5WgNgBL9X U1SReXk22kvWbMAoKraBNyFiiu2JH0z7wz+jlwkqRTzu84Shj7r3Ji54a3MmoqtB2GDQ 4uww== X-Gm-Message-State: AGi0PuZ8pKLbEZzVP7LLQCCxjTKdEGTq1AmLZIWMej+AdQrQCZ2lmne7 GVuDNgP4eeOVvBGreuvzrSlU/VXP0bUGxIlsiGA= X-Google-Smtp-Source: APiQypKGybMw2xcq5kQqxyJhbLFdmgz5hDSf03e9VC/u8fH3oepUD+LGygm3ovqjQZqSoJlPREFjxBm5yR0m48i5mxg= X-Received: by 2002:a05:6e02:6c1:: with SMTP id p1mr7729358ils.137.1587211050776; Sat, 18 Apr 2020 04:57:30 -0700 (PDT) In-Reply-To: <835zdxaw60.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:178564 Archived-At: --000000000000dd7d4605a38f5efd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Apr 18, 2020 at 12:08 PM Eli Zaretskii 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=C3=A3o T=C3=A1vora --000000000000dd7d4605a38f5efd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 in= deed 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.=C2=A0 What'= s
> > the problem with that?
> Existing files was what = I had in mind.

OK. I admit I don't care much a= bout 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 me= ant to do it in addition.

Ah, indeed I had misunde= rstood you.=C2=A0 But what's the point
in having them al= so in the cookies then?=C2=A0 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-mo= de-alist.=C2=A0 And the only way
we to safely do that add-to= -list is to do it from :set=C2=A0 directives
in the defcustom def= inition 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&= #39;d
appreciate you tell me how to do it or what you had in= mind.

> > If you do use and know some o= f these files, I think I've shown
> > how trivial it is = to make them use lisp-data-mode.
>
> Sorry, I don't have ti= me to do that research for now.=C2=A0 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 a= s much as you.

--
Jo=C3=A3o T=C3=A1vora
 --000000000000dd7d4605a38f5efd--