GNU logs - #15219, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#15219: Emacs Lisp mode and Lisp mode font-locking
Resent-From: Bozhidar Batsov <bozhidar.batsov@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Fri, 30 Aug 2013 09:33:01 +0000
Resent-Message-ID: <handler.15219.B.137785515113723 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 15219 <at> debbugs.gnu.org
Date: Fri, 30 Aug 2013 12:32:05 +0300
From: Bozhidar Batsov <bozhidar.batsov@HIDDEN>
Message-ID: <FA68F294BF5F4BF598190F14B70E82DC@HIDDEN>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="52206695_7c58fd05_99"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--52206695_7c58fd05_99
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I've noticed something odd about the font-locking in Emacs Lisp mode and Lisp mode - keyword args are highlighted using the font-lock-builtin-face and constructs like &optional are highlighted using font-lock-type-face. I guess this was was done way back and hasn't been updated in a while, but I think it might a good idea to revise this. Pretty sure those font faces are intended for different usage. I think it would be great if all Emacs programming modes used the built-in font-lock faces consistently, so that the meaning of certain faces doesn't change from mode to mode. I guess that the two modes might also start using the font-lock-built-in face to highlight their core functions (like car, cdr, mapcar, mapc, etc) - as Clojure mode does. Personally I feel that uses of the keyword face for things that are not special forms (like the when macro) should be replaced with uses of the built-in face.
I've posted this to devel a while back (http://lists.gnu.org/archive/html/emacs-devel/2013-07/msg00592.html) and Michael Heerdegen suggested reporting it as a bug as well.

-- 
Cheers,
Bozhidar

--52206695_7c58fd05_99
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

                <div>
                    <pre><font face=3D=22Trebuchet MS=22>I've noticed som=
ething odd about the font-locking in Emacs Lisp mode and
Lisp mode - keyword args are highlighted using the
font-lock-builtin-face and constructs like &amp;optional are highlighted
using font-lock-type-face. =20

I guess this was was done way back and hasn't been updated in a
while, but I think it might a good idea to revise this. Pretty sure
those font faces are intended for different usage. I think it would
be great if all Emacs programming modes used the built-in font-lock faces=
 consistently,
so that the meaning of certain faces doesn't change from mode to
mode.

I guess that the two modes might also start using the
font-lock-built-in face to highlight their core functions (like car,
cdr, mapcar, mapc, etc) - as Clojure mode does. Personally I feel that us=
es of the keyword face for things that are not special forms (like the wh=
en macro) should be replaced with uses of the built-in face.</font></pre>=
<pre><font face=3D=22Trebuchet MS=22>I've posted this to devel a while ba=
ck (<a href=3D=22http://lists.gnu.org/archive/html/emacs-devel/2013-07/ms=
g00592.html=22>http://lists.gnu.org/archive/html/emacs-devel/2013-07/msg0=
0592.html</a>) and <span style=3D=22font-size: 13px; text-align: -webkit-=
left; =22>Michael Heerdegen suggested reporting it as a bug as well.</spa=
n></font></pre></div><div><div><br></div><div>--&nbsp;</div><div>Cheers,<=
/div><div>Bozhidar</div><div><br></div></div>

--52206695_7c58fd05_99--

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.503 (Entity 5.503)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Bozhidar Batsov <bozhidar.batsov@HIDDEN>
Subject: bug#15219: Acknowledgement (Emacs Lisp mode and Lisp mode
 font-locking)
Message-ID: <handler.15219.B.137785515113723.ack <at> debbugs.gnu.org>
References: <FA68F294BF5F4BF598190F14B70E82DC@HIDDEN>
X-Gnu-PR-Message: ack 15219
X-Gnu-PR-Package: emacs
Reply-To: 15219 <at> debbugs.gnu.org
Date: Fri, 30 Aug 2013 09:33:01 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 15219 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
15219: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D15219
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#15219: Emacs Lisp mode and Lisp mode font-locking
Resent-From: Stefan Monnier <monnier@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Fri, 30 Aug 2013 12:46:02 +0000
Resent-Message-ID: <handler.15219.B15219.13778667294823 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Bozhidar Batsov <bozhidar.batsov@HIDDEN>
Cc: 15219 <at> debbugs.gnu.org
From: Stefan Monnier <monnier@HIDDEN>
Message-ID: <jwv1u5bwe10.fsf-monnier+emacs@HIDDEN>
References: <FA68F294BF5F4BF598190F14B70E82DC@HIDDEN>
Date: Fri, 30 Aug 2013 08:45:15 -0400
In-Reply-To: <FA68F294BF5F4BF598190F14B70E82DC@HIDDEN> (Bozhidar Batsov's
 message of "Fri, 30 Aug 2013 12:32:05 +0300")
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

> I've noticed something odd about the font-locking in Emacs Lisp mode and
> Lisp mode - keyword args are highlighted using the font-lock-builtin-face
> and constructs like &optional are highlighted using
> font-lock-type-face. I guess this was was done way back and hasn't been
> updated in a while, but I think it might a good idea to revise this. Pretty
> sure those font faces are intended for different usage. I think it would be
> great if all Emacs programming modes used the built-in font-lock faces
> consistently, so that the meaning of certain faces doesn't change from mode
> to mode. I guess that the two modes might also start using the
> font-lock-built-in face to highlight their core functions (like car, cdr,
> mapcar, mapc, etc) - as Clojure mode does. Personally I feel that uses of
> the keyword face for things that are not special forms (like the when macro)
> should be replaced with uses of the built-in face.

Which things are special forms and which things are macros is
somewhat arbitrary.  The important thing to know about them is that
they're not functions, so their arguments may not be evaluated in the
usual way.
Also macros are used to introduce new syntactic constructs: in normal
programming languages, something like `when' would be highlighted as
a `keyword', not as a `builtin'.

I'm not completely sure what the `builtin' is used for, usually.
What information is it meant to provide?  I mean, do you consider
`mapcar' "builtin" because it's fast?  Because it's implemented in C?
Because it's predefined (no need for any kind of autoloading/require)?
Is `car' builtin because "if you didn't have it, you'd have to invent
it" (IOW can't be implemented in Elisp)?


        Stefan

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#15219: Emacs Lisp mode and Lisp mode font-locking
Resent-From: Bozhidar Batsov <bozhidar.batsov@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Fri, 30 Aug 2013 13:24:02 +0000
Resent-Message-ID: <handler.15219.B15219.13778690238694 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Stefan Monnier <monnier@HIDDEN>
Cc: 15219 <at> debbugs.gnu.org
Date: Fri, 30 Aug 2013 16:23:37 +0300
From: Bozhidar Batsov <bozhidar.batsov@HIDDEN>
Message-ID: <0103F5523929438C99A2AF40E0ADA510@HIDDEN>
In-Reply-To: <jwv1u5bwe10.fsf-monnier+emacs@HIDDEN>
References: <FA68F294BF5F4BF598190F14B70E82DC@HIDDEN>
 <jwv1u5bwe10.fsf-monnier+emacs@HIDDEN>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="52209cd9_4d32ab86_99"
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

--52209cd9_4d32ab86_99
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Friday, August 30, 2013 at 3:45 PM, Stefan Monnier wrote:
> > I've noticed something odd about the font-locking in Emacs Lisp mode and
> > Lisp mode - keyword args are highlighted using the font-lock-builtin-face
> > and constructs like &optional are highlighted using
> > font-lock-type-face. I guess this was was done way back and hasn't been
> > updated in a while, but I think it might a good idea to revise this. Pretty
> > sure those font faces are intended for different usage. I think it would be
> > great if all Emacs programming modes used the built-in font-lock faces
> > consistently, so that the meaning of certain faces doesn't change from mode
> > to mode. I guess that the two modes might also start using the
> > font-lock-built-in face to highlight their core functions (like car, cdr,
> > mapcar, mapc, etc) - as Clojure mode does. Personally I feel that uses of
> > the keyword face for things that are not special forms (like the when macro)
> > should be replaced with uses of the built-in face.
> > 
> 
> 
> Which things are special forms and which things are macros is
> somewhat arbitrary. The important thing to know about them is that
> they're not functions, so their arguments may not be evaluated in the
> usual way.
> 
> 

Fair point. I guess it makes sense to some extend to consider some macros to be "keywords". 
> Also macros are used to introduce new syntactic constructs: in normal
> programming languages, something like `when' would be highlighted as
> a `keyword', not as a `builtin'.
> 
> I'm not completely sure what the `builtin' is used for, usually.
> What information is it meant to provide? 
> 
> 

Generally the idea behind fontifying built-ins (AFAIK) is to remind programmers that something is part of the core of the language and it'd be unwise to redefine or shadow it. For instance in Clojure mode all methods from the clojure.core namespace are font-locked with the built-in face.
> I mean, do you consider
> `mapcar' "builtin" because it's fast? Because it's implemented in C?
> Because it's predefined (no need for any kind of autoloading/require)?
> Is `car' builtin because "if you didn't have it, you'd have to invent
> it" (IOW can't be implemented in Elisp)?
> 
Normally built-in functions would be those that came with the standard library of the language and are pretty generic in nature.  I guess in Emacs Lisp that would be functions like mapcar, mapc, vector, car, cdr - the building blocks on which everything else rests upon. I guess there are not that much of those and they haven't changed much in a long while. And as the Emacs manual itself states "font-lock-builtin-face is for the names of built-in functions". 
> 
> 
> Stefan
Anyways, I'd be happy to get just a fix for the keywords and &optional (and related) faces, since those are definitely off.


--52209cd9_4d32ab86_99
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


                <div><span style=3D=22color: rgb(160, 160, 168); =22>On =46=
riday, August 30, 2013 at 3:45 PM, Stefan Monnier wrote:</span></div>
                <blockquote type=3D=22cite=22 style=3D=22border-left-styl=
e:solid;border-width:1px;margin-left:0px;padding-left:10px;=22>
                    <span><div><div><blockquote type=3D=22cite=22><div><d=
iv>I've noticed something odd about the font-locking in Emacs Lisp mode a=
nd</div><div>Lisp mode - keyword args are highlighted using the font-lock=
-builtin-face</div><div>and constructs like &amp;optional are highlighted=
 using</div><div>font-lock-type-face. I guess this was was done way back =
and hasn't been</div><div>updated in a while, but I think it might a good=
 idea to revise this. Pretty</div><div>sure those font faces are intended=
 for different usage. I think it would be</div><div>great if all Emacs pr=
ogramming modes used the built-in font-lock faces</div><div>consistently,=
 so that the meaning of certain faces doesn't change from mode</div><div>=
to mode. I guess that the two modes might also start using the</div><div>=
font-lock-built-in face to highlight their core functions (like car, cdr,=
</div><div>mapcar, mapc, etc) - as Clojure mode does. Personally I feel t=
hat uses of</div><div>the keyword face for things that are not special fo=
rms (like the when macro)</div><div>should be replaced with uses of the b=
uilt-in face.</div></div></blockquote><div><br></div><div>Which things ar=
e special forms and which things are macros is</div><div>somewhat arbitra=
ry.  The important thing to know about them is that</div><div>they're not=
 functions, so their arguments may not be evaluated in the</div><div>usua=
l way.</div></div></div></span></blockquote><div><font face=3D=22Trebuche=
t MS=22>=46air point. I guess it makes sense to some extend to consider s=
ome macros to be =22keywords=22.</font>&nbsp;</div><blockquote type=3D=22=
cite=22 style=3D=22border-left-style:solid;border-width:1px;margin-left:0=
px;padding-left:10px;=22><div><div><div>Also macros are used to introduce=
 new syntactic constructs: in normal</div><div>programming languages, som=
ething like =60when' would be highlighted as</div><div>a =60keyword', not=
 as a =60builtin'.</div><div><br></div><div>I'm not completely sure what =
the =60builtin' is used for, usually.</div><div>What information is it me=
ant to provide=3F </div></div></div></blockquote><div><font face=3D=22Tre=
buchet MS=22>Generally the idea behind fontifying built-ins (A=46AIK) is =
to remind programmers that something is part of the core of the language =
and it'd be unwise to redefine or shadow it. =46or instance in Clojure mo=
de all methods from the clojure.core namespace are font-locked with the b=
uilt-in face.</font></div><blockquote type=3D=22cite=22 style=3D=22border=
-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;=22>=
<div><div><div> I mean, do you consider</div><div>=60mapcar' =22builtin=22=
 because it's fast=3F  Because it's implemented in C=3F</div><div>Because=
 it's predefined (no need for any kind of autoloading/require)=3F</div><d=
iv>Is =60car' builtin because =22if you didn't have it, you'd have to inv=
ent</div><div>it=22 (IOW can't be implemented in Elisp)=3F</div><div><br>=
</div></div></div></blockquote><div><font face=3D=22Trebuchet MS=22>Norma=
lly built-in functions would be those that came with the standard library=
 of the language and are pretty generic in nature.&nbsp;</font>&nbsp;I gu=
ess in Emacs Lisp that would be functions like mapcar, mapc, vector, car,=
 cdr - the building blocks on which everything else rests upon. I guess t=
here are not that much of those and they haven't changed much in a long w=
hile. And as the Emacs manual itself states =22<span style=3D=22font-styl=
e: inherit; line-height: 13px; color: rgb(53, 56, 42); font-family: sans-=
serif; =22>font-lock-builtin-face is&nbsp;</span><span style=3D=22color: =
rgb(53, 56, 42); font-family: sans-serif; =22>for the names of built-in f=
unctions=22.</span><span style=3D=22color: rgb(53, 56, 42); font-family: =
sans-serif; =22>&nbsp;</span></div><blockquote type=3D=22cite=22 style=3D=
=22border-left-style:solid;border-width:1px;margin-left:0px;padding-left:=
10px;=22><div><div><div></div><div><br></div><div>        Stefan</div></d=
iv></div></blockquote><div>Anyways, I'd be happy to get just a fix for th=
e keywords and &amp;optional (and related) faces, since those are definit=
ely off.</div>
                =20
                <div>
                    <br>
                </div>
            
--52209cd9_4d32ab86_99--

Message sent to bug-gnu-emacs@HIDDEN:

X-Loop: help-debbugs@HIDDEN
Subject: bug#15219: Emacs Lisp mode and Lisp mode font-locking
Resent-From: Lars Ingebrigtsen <larsi@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Wed, 30 Oct 2019 13:31:01 +0000
Resent-Message-ID: <handler.15219.B15219.157244222812231 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
X-GNU-PR-Message: followup 15219
X-GNU-PR-Package: emacs
X-GNU-PR-Keywords: 
To: Bozhidar Batsov <bozhidar.batsov@HIDDEN>
Cc: Stefan Monnier <monnier@HIDDEN>, 15219 <at> debbugs.gnu.org
Received: via spool by 15219-submit <at> debbugs.gnu.org id=B15219.157244222812231
          (code B ref 15219); Wed, 30 Oct 2019 13:31:01 +0000
Received: (at 15219) by debbugs.gnu.org; 30 Oct 2019 13:30:28 +0000
Received: from localhost ([127.0.0.1]:49516 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1iPo3Q-0003BB-GL
	for submit <at> debbugs.gnu.org; Wed, 30 Oct 2019 09:30:28 -0400
Received: from quimby.gnus.org ([80.91.231.51]:56436)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <larsi@HIDDEN>) id 1iPo3J-0003Av-K7
 for 15219 <at> debbugs.gnu.org; Wed, 30 Oct 2019 09:30:24 -0400
Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie)
 by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.89) (envelope-from <larsi@HIDDEN>)
 id 1iPo3E-0006en-1t; Wed, 30 Oct 2019 14:30:18 +0100
From: Lars Ingebrigtsen <larsi@HIDDEN>
References: <FA68F294BF5F4BF598190F14B70E82DC@HIDDEN>
 <jwv1u5bwe10.fsf-monnier+emacs@HIDDEN>
 <0103F5523929438C99A2AF40E0ADA510@HIDDEN>
Date: Wed, 30 Oct 2019 14:30:15 +0100
In-Reply-To: <0103F5523929438C99A2AF40E0ADA510@HIDDEN> (Bozhidar Batsov's
 message of "Fri, 30 Aug 2013 16:23:37 +0300")
Message-ID: <87eeyuuzrs.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org",
 has NOT identified this incoming email as spam.  The original
 message has been attached to this so you can view it or label
 similar future email.  If you have any questions, see
 @@CONTACT_ADDRESS@@ for details.
 Content preview: Bozhidar Batsov <bozhidar.batsov@HIDDEN> writes: > Anyways,
 I'd be happy to get just a fix for the keywords and &optional (and > related)
 faces, since those are definitely off. The complaint is that :foobar below
 uses font-lock-builtin-face and &optional uses font-lock-type-face in
 emacs-lisp-mode.
 Content analysis details:   (-2.9 points, 5.0 required)
 pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
 [score: 0.0000]
X-Spam-Score: 0.0 (/)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Bozhidar Batsov <bozhidar.batsov@HIDDEN> writes:

> Anyways, I'd be happy to get just a fix for the keywords and &optional (and
> related) faces, since those are definitely off.

The complaint is that :foobar below uses font-lock-builtin-face and
&optional uses font-lock-type-face in emacs-lisp-mode.

(defun foo (bar &optional zot)
  (list :foobar bar))

This is defined in lisp-cl-font-lock-keywords in lisp-mode.el, and I
agree that separate faces should probably be used for those -- keywords
aren't builtins and &optional isn't a type.

:keywords are constants, I guess, but we use font-lock-constant-face for
catch/throw and the like, and I don't think we have anything that
vaguely makes sense for &optional.

Would adding new faces for these make sense?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message received at control <at> debbugs.gnu.org:

Received: (at control) by debbugs.gnu.org; 10 Oct 2021 23:49:37 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Oct 10 19:49:36 2021
Received: from localhost ([127.0.0.1]:56067 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1mZiZU-0005Dv-QI
	for submit <at> debbugs.gnu.org; Sun, 10 Oct 2021 19:49:36 -0400
Received: from mail-pj1-f45.google.com ([209.85.216.45]:35514)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <stefankangas@HIDDEN>) id 1mZiZQ-0005Dg-Uq
 for control <at> debbugs.gnu.org; Sun, 10 Oct 2021 19:49:35 -0400
Received: by mail-pj1-f45.google.com with SMTP id
 d13-20020a17090ad3cd00b0019e746f7bd4so13412889pjw.0
 for <control <at> debbugs.gnu.org>; Sun, 10 Oct 2021 16:49:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:from:mime-version:date:message-id:subject:to;
 bh=LlSgN/r5MsLBEhzPbehRrP8jxe/+8uPHErug2ShDZzE=;
 b=5R9J1GTP4g2Uk1Isr1zUR6LMFO6cJPYszbHp7d6fXtsRE93V6PnLjK42kJC9dtcaol
 K4hrgAmwsdqI2pD3vEMUhgHDlg4iZd5Jd2LPXwwR/SPIZ8hUuNHNj1lph3M3m1jh2aqX
 GZS7QgnBWmXD5TP8rxsEQaQkaC0FCj98+J/V3Xpln864PkSdn9PfA4yXop5u4R5UWiSu
 lCMTn3JPXw+rB5SF5ReFV9a32I3b4WuCzd1YdShSimI37CzvT4b1AN0fjhJI8UUMP+D1
 6WPu53d0rTKlRjdIM1y6IjUxDeF+C4NAuDkliwwbcL7NoNmZF2jj4DQSGMm1CoQYtsmA
 P7mw==
X-Gm-Message-State: AOAM5310KFS985RAybC+W3jB5THepKn5KYNdspgEuXBflEjHGI8zkhs3
 i+hnYjO+qpmDNxhEBY5rCc37/GM0CaUP00RBUWo2XgJc
X-Google-Smtp-Source: ABdhPJwz24egP6XWL/QoM10HG8sHHzTWZuRVa8BeGIu868k/GqYim95/MwqgcyppGXYUWNOmLpdPQkP6lGfi8DdK2kU=
X-Received: by 2002:a17:90a:460a:: with SMTP id
 w10mr27024555pjg.132.1633909767040; 
 Sun, 10 Oct 2021 16:49:27 -0700 (PDT)
Received: from 753933720722 named unknown by gmailapi.google.com with
 HTTPREST; Sun, 10 Oct 2021 16:49:26 -0700
From: Stefan Kangas <stefan@HIDDEN>
MIME-Version: 1.0
Date: Sun, 10 Oct 2021 16:49:26 -0700
Message-ID: <CADwFkmneWfKQqwhdMgYfp-8FgUYxWF8E6xhWrGpSDUeC44xwqw@HIDDEN>
Subject: control message for bug #15219
To: control <at> debbugs.gnu.org
Content-Type: text/plain; charset="UTF-8"
X-Spam-Score: 0.5 (/)
X-Debbugs-Envelope-To: control
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -0.5 (/)

severity 15219 wishlist
quit

Last modified: Mon, 11 Oct 2021 00:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.