From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>, Glenn Morris <rgm@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>,
Lars Ingebrigtsen <larsi@gnus.org>,
17052@debbugs.gnu.org
Subject: bug#17052: substitute-command-keys strips text properties, bug#8911: huh?
Date: Mon, 16 Nov 2020 18:34:56 -0800 [thread overview]
Message-ID: <CADwFkmnOecR=ijpu4Ofsq4Aj1u1V7AZ42qJG1E9L7nb7QBkeKQ@mail.gmail.com> (raw)
In-Reply-To: <a6614aef-62d9-499f-9daf-93bdcf9ea88e@default>
Drew Adams <drew.adams@oracle.com> writes:
> I don't understand the relation between this bug, #17052,
> and bug #8911. Half of the messages in the 8911 thread
> are about 17052, and the subjects seem quite different.
>
> But it looks like 8911 is still open (wishlist). Is that
^^^^ you probably mean 8951
> correct? Why/how did these two bugs get overlapped or
> combined?
It was my perhaps ill-advised attempt to combine the discussions about
the Lisp conversion of `substitute-command-keys'.
(FWIW, I intend to look into Bug#8951 soon-ish.)
next prev parent reply other threads:[~2020-11-17 2:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 16:22 bug#17052: substitute-command-keys strips text properties Juanma Barranquero
2019-08-15 0:55 ` Lars Ingebrigtsen
2019-08-15 1:34 ` Glenn Morris
2019-08-15 1:58 ` Lars Ingebrigtsen
2019-08-15 16:46 ` Eli Zaretskii
2019-08-15 22:42 ` Lars Ingebrigtsen
2019-08-16 6:47 ` Eli Zaretskii
2019-08-16 7:04 ` Lars Ingebrigtsen
2019-08-18 17:08 ` Stefan Kangas
2019-08-18 17:19 ` Eli Zaretskii
2019-08-18 22:43 ` Lars Ingebrigtsen
2019-08-19 15:27 ` Eli Zaretskii
2019-08-18 17:19 ` Lars Ingebrigtsen
2020-11-17 1:24 ` Stefan Kangas
2020-11-17 1:37 ` bug#17052: substitute-command-keys strips text properties, bug#8911: huh? Drew Adams
2020-11-17 2:34 ` Stefan Kangas [this message]
2020-11-17 3:00 ` Drew Adams
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='CADwFkmnOecR=ijpu4Ofsq4Aj1u1V7AZ42qJG1E9L7nb7QBkeKQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=17052@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=lekktu@gmail.com \
--cc=rgm@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 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.