unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christopher Howard <christopher@librehacker.com>
Cc: 74673@debbugs.gnu.org
Subject: bug#74673: 30.0.92; face warning on legal elisp syntax
Date: Tue, 03 Dec 2024 21:02:17 +0200	[thread overview]
Message-ID: <86h67k1tfq.fsf@gnu.org> (raw)
In-Reply-To: <874j3kfvq8.fsf@librehacker.com> (message from Christopher Howard on Tue, 03 Dec 2024 09:49:03 -0900)

> From: Christopher Howard <christopher@librehacker.com>
> Date: Tue, 03 Dec 2024 09:49:03 -0900
> 
> Hi, in Elisp buffers, I am occasionally seeing a face warning (red colored on my system) for what appears to be fully legal and functional syntax. Here is a recent example:
> 
> 1. emacs -Q
> 2. paste the following into the *scratch* buffer
> 
> ``` elisp
> (t-transduce
>  (t-scan
>   (lambda (s c)
>     (concatenate 'string s (string c))) "")
>  #'t-cons
>  "hello")
> ```
> 
> On my system, the text «"")», at the end of the «concatenate» line, is given font-lock-warning-face. Is this a bug, or some kind of warning about bad elisp style?

The latter, I think.  If you insert a newline before that "", does the
warning face go away?





  reply	other threads:[~2024-12-03 19:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 18:49 bug#74673: 30.0.92; face warning on legal elisp syntax Christopher Howard
2024-12-03 19:02 ` Eli Zaretskii [this message]
2024-12-03 19:19   ` Christopher Howard
2024-12-03 19:38     ` Eli Zaretskii
2024-12-03 20:48       ` Christopher Howard
2024-12-04 12:23         ` Eli Zaretskii
2024-12-04 17:12           ` Kévin Le Gouguec
2024-12-04 17:32             ` Eli Zaretskii
2024-12-05  9:28               ` Robert Pluim
2024-12-05  9:53                 ` Eli Zaretskii
2024-12-05 10:06                   ` Robert Pluim
2024-12-04 17:51           ` Jim Porter
2024-12-04 18:55             ` Eli Zaretskii
2024-12-06  4:46         ` Richard Stallman
2024-12-06  8:26           ` Eli Zaretskii
2024-12-04 15:42 ` Christopher Howard

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=86h67k1tfq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74673@debbugs.gnu.org \
    --cc=christopher@librehacker.com \
    /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).