unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master b0049c942b8: bytecomp.el: Warn for `, ' not within backquote construct
Date: Sat, 16 Mar 2024 11:08:34 -0400	[thread overview]
Message-ID: <jwvzfuygqz9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1rlJ7D-0000em-KN@fencepost.gnu.org> (Richard Stallman's message of "Fri, 15 Mar 2024 21:45:39 -0400")

>   >     In my-foo:
>   >     foo.el:4:7: Warning: ‘,’ called -- perhaps used not within backquote
>     
>   >     In end of data:
>   >     foo.el: Warning: the function ‘,’ is not known to be defined.
>
> The mew warning (shown first above) is better), so I'd suggest disabling
> the old (second) warning for this function.

Reminds me that I have fun definitions for toplevel uses of `,` and `,@`
to propose:

    (defmacro \,@ (exp)
      "Splice EXP's value (a list of Lisp forms) into the code."
      (declare (debug t))
      `(progn ,@(eval exp t)))

    (defmacro \, (exp)
      "Splice EXP's value (a Lisp form) into the code."
      (declare (debug t))
      (eval exp t))

The first one is already available under the names `gnus--,@` and `ses--,@`.


        Stefan




      reply	other threads:[~2024-03-16 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <170700201601.3724.18410252880023545872@vcs2.savannah.gnu.org>
     [not found] ` <20240203231336.5A511C0EFF8@vcs2.savannah.gnu.org>
2024-02-04  4:06   ` master b0049c942b8: bytecomp.el: Warn for `, ' not within backquote construct Po Lu
2024-02-05  3:36     ` Richard Stallman
2024-02-05 12:46       ` Eli Zaretskii
2024-02-05 13:35     ` Stefan Monnier via Emacs development discussions.
2024-03-16  1:45       ` Richard Stallman
2024-03-16 15:08         ` Stefan Monnier [this message]

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=jwvzfuygqz9.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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).