all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, 17052@debbugs.gnu.org
Subject: bug#17052: substitute-command-keys strips text properties
Date: Wed, 14 Aug 2019 21:34:47 -0400	[thread overview]
Message-ID: <1xh86jb494.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <871rxns0vz.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Wed, 14 Aug 2019 17:55:28 -0700")

Lars Ingebrigtsen wrote:

> Looks like this has been fixed sometime in the intervening years?
>
> (substitute-command-keys (propertize "foo" 'face 'bold))
> => #("foo" 0 3 (face bold))

Nope, you need to use an example which does a substitution, eg

(substitute-command-keys (propertize "foo \\[find-file]" 'face 'bold))

The doc of substitute-command-keys used to mention this, but it was
somewhat prematurely removed in 049fac7.





  reply	other threads:[~2019-08-15  1: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 [this message]
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
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=1xh86jb494.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=17052@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=lekktu@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.