From: Anders Lindgren <andlind@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Dmitry Gutov <dgutov@yandex.ru>,
Stefan Monnier <monnier@iro.umontreal.ca>,
23465@debbugs.gnu.org
Subject: bug#23465: 25.0.93; `lambda' after hash-quote not highlighted as keyword
Date: Mon, 29 Jan 2018 13:52:05 +0100 [thread overview]
Message-ID: <CABr8ebZNjAakPK+FjyoPiTvov7FFwxnBfUXNbLu-iWdGyLO5tQ@mail.gmail.com> (raw)
In-Reply-To: <87zi4wj1gt.fsf@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
Ahh, right. I mixed it up with when `lambda':s weren't highlighted at all...
-- Anders
On Mon, Jan 29, 2018 at 1:25 PM, Noam Postavsky <
npostavs@users.sourceforge.net> wrote:
> Anders Lindgren <andlind@gmail.com> writes:
>
> > No, it was never pushed. However, this has resolved itself since
> > `lambda` now is a macro, so it's highlighted using the normal macro
> > mechanism.
>
> Not when it's hash quoted though, which I thought was the point of this
> bug.
>
[-- Attachment #2: Type: text/html, Size: 933 bytes --]
next prev parent reply other threads:[~2018-01-29 12:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 10:07 bug#23465: 25.0.93; `lambda' after hash-quote not highlighted as keyword Anders Lindgren
2016-05-06 18:32 ` Anders Lindgren
2016-05-10 15:00 ` Anders Lindgren
2016-05-10 16:25 ` Eli Zaretskii
2016-05-10 22:09 ` Dmitry Gutov
2016-05-11 9:19 ` Anders Lindgren
2016-05-11 9:34 ` Anders Lindgren
2016-05-11 9:46 ` Eli Zaretskii
2016-05-12 5:49 ` John Wiegley
2016-05-11 10:18 ` Dmitry Gutov
2016-05-11 12:32 ` Stefan Monnier
2016-05-11 12:39 ` Dmitry Gutov
2016-05-11 13:08 ` Anders Lindgren
2016-05-11 13:35 ` Stefan Monnier
2016-05-11 15:02 ` Anders Lindgren
2018-01-28 23:31 ` Noam Postavsky
2018-01-29 7:56 ` Anders Lindgren
2018-01-29 12:25 ` Noam Postavsky
2018-01-29 12:52 ` Anders Lindgren [this message]
2020-08-19 12:20 ` Lars Ingebrigtsen
2016-05-11 10:00 ` Leo Liu
2016-05-11 12:25 ` Stefan Monnier
2016-05-12 1:32 ` Leo Liu
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=CABr8ebZNjAakPK+FjyoPiTvov7FFwxnBfUXNbLu-iWdGyLO5tQ@mail.gmail.com \
--to=andlind@gmail.com \
--cc=23465@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.net \
/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).