From: shortcutz <spookygostee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: strange behavior of mapconcat
Date: Mon, 15 Apr 2024 10:43:37 -0500 [thread overview]
Message-ID: <CAJ+V6LGV=LJ0fpevLDT6wuK6PPWwWBg-f=M8x_=sVKp6+NxymQ@mail.gmail.com> (raw)
Hi all,
In a piece of code I call mapconcat with these arguments:
(mapconcat 'org-no-properties "t" " ")
I'm getting the error (wrong-type-argument sequencep 115). This is the same
if I use the identity function or any other string instead of "t":
(mapconcat 'identity "t" " ")
(mapconcat 'identity "string1 string2" " ")
What am I doing wrong? I don't really understand where the 115 is coming
from. The code is unchanged after macroexpanding, and sequencep says
"string1 string2" and "t" are both valid sequences.
Thanks
R
next reply other threads:[~2024-04-15 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 15:43 shortcutz [this message]
2024-04-15 15:57 ` strange behavior of mapconcat shortcutz
2024-04-16 6:16 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-04-16 6:36 ` Joost Kremers
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='CAJ+V6LGV=LJ0fpevLDT6wuK6PPWwWBg-f=M8x_=sVKp6+NxymQ@mail.gmail.com' \
--to=spookygostee@gmail.com \
--cc=help-gnu-emacs@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.
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).