From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: 64584@debbugs.gnu.org
Subject: bug#64584: 29.0.91; skeleton: cannot pass `str' as argument to some functions
Date: Tue, 12 Sep 2023 09:08:09 -0400 [thread overview]
Message-ID: <jwvh6nz4ka8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87y1hbk2ab.fsf@gmail.com> (Visuwesh's message of "Tue, 12 Sep 2023 17:54:12 +0530")
> Yes, but here it basically does nothing unfortunately. I am not sure if
>
> 'str
>
> should have the side effect of setting that variable.
The above skeleton expression means "eval the variable `str` and throw
away the result". The only effect it can have is to signal an error if
the variable `str` is not bound.
> (defmacro vz/snippet-when (form &rest body)
> "Evaluate BODY if FORM returns non-nil or non-empty string."
> (declare (indent 1) (debug (form body)))
> `(let ((str ,form))
> (if (and str (equal str ""))
> ""
> ,@body)))
FWIW, this style of macro is usually called "anaphoric macro" and the
convention is to use the identifier `it` rather than `str` in them.
It would help avoid a confusion between skeleton's `str` and your
macro's variable.
[ And, yes, arguably, `define-skeleton` could be considered as an
anaphoric macro as well which should use `it` instead of `str`,
bringing back the confusion :-) ]
Stefan
next prev parent reply other threads:[~2023-09-12 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 17:05 bug#64584: 29.0.91; skeleton: cannot pass `str' as argument to some functions Visuwesh
2023-09-11 13:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 15:20 ` Visuwesh
2023-09-11 22:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 2:36 ` Visuwesh
2023-09-12 3:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 12:24 ` Visuwesh
2023-09-12 13:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-12 14:50 ` Visuwesh
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=jwvh6nz4ka8.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=64584@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=visuweshm@gmail.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).