From: Noam Postavsky <npostavs@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Robert Cochran" <robert-emacs@cochranmail.com>,
"Ikumi Keita" <ikumi@ikumi.que.jp>,
"Pierre Téchoueyres" <pierre.techoueyres@free.fr>,
"Vibhav Pant" <vibhavp@gmail.com>,
"Basil L. Contovounesios" <contovob@tcd.ie>,
"Jay Kamat" <jaygkamat@gmail.com>,
"Héctor Enríquez Ramón" <hector.e.r@gmail.com>,
"Andreas Schwab" <schwab@suse.de>,
31718@debbugs.gnu.org
Subject: bug#31718: 26.1; Strange behavior of `cond'
Date: Sat, 16 Jun 2018 11:23:33 -0400 [thread overview]
Message-ID: <87602ivjpm.fsf@gmail.com> (raw)
In-Reply-To: <08fcc11f-3ae6-cc99-d56a-450fd773495b@cs.ucla.edu> (Paul Eggert's message of "Sat, 16 Jun 2018 08:10:02 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> A small problem: gensym does not guarantee that the resulting symbol
> is unique so the generated symbol could in theory appear in the input
What?
gensym is a compiled Lisp function in ‘subr.el’.
(gensym &optional PREFIX)
Return a new uninterned symbol.
^^^
How could a new symbol have already appeared in the input?
(I have no objection to the alternative you used, just wondering why
gensym is not also correct)
next prev parent reply other threads:[~2018-06-16 15:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 6:26 bug#31718: 26.1; Strange behavior of `cond' Ikumi Keita
2018-06-05 8:07 ` Andreas Schwab
2018-06-06 5:41 ` Ikumi Keita
2018-06-06 7:41 ` Robert Cochran
2018-06-06 9:14 ` Ikumi Keita
2018-06-12 1:34 ` Robert Cochran
2018-06-12 22:22 ` Noam Postavsky
2018-06-13 5:51 ` Ikumi Keita
2018-06-13 6:26 ` Vibhav Pant
2018-06-16 15:10 ` Paul Eggert
2018-06-16 15:20 ` Eli Zaretskii
2018-06-16 15:28 ` Paul Eggert
2018-06-16 16:02 ` Eli Zaretskii
2018-06-16 16:45 ` Paul Eggert
2018-06-16 15:23 ` Noam Postavsky [this message]
2018-06-16 15:30 ` Paul Eggert
2018-06-16 23:00 ` Drew Adams
2018-06-17 4:44 ` Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87602ivjpm.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31718@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=eggert@cs.ucla.edu \
--cc=hector.e.r@gmail.com \
--cc=ikumi@ikumi.que.jp \
--cc=jaygkamat@gmail.com \
--cc=pierre.techoueyres@free.fr \
--cc=robert-emacs@cochranmail.com \
--cc=schwab@suse.de \
--cc=vibhavp@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.