unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Thierry Volpiatto" <thievol@posteo.net>,
	"João Távora" <joaotavora@gmail.com>
Cc: 59082@debbugs.gnu.org
Subject: bug#59082: 28.2; Undocumented `intern-soft` feature with shorthands symbols
Date: Sat, 12 Nov 2022 14:42:41 +0200	[thread overview]
Message-ID: <831qq8ny2m.fsf@gnu.org> (raw)
In-Reply-To: <875yfresq9.fsf@posteo.net> (message from Thierry Volpiatto on Sun, 06 Nov 2022 20:16:48 +0000)

> From: Thierry Volpiatto <thievol@posteo.net>
> Date: Sun, 06 Nov 2022 20:16:48 +0000
> 
> after having hard time getting the longhand name of a shorthand symbol
> at point (with regexp and the local value of read-symbol-shorthands) I
> discover it is easy to get this information with:
> 
>     (symbol-name (intern-soft (thing-at-point 'symbol)))
> 
> Is this the right way to get this information and if so is it
> possible to document it?

João, any comments?

Thanks.





  reply	other threads:[~2022-11-12 12:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 20:16 bug#59082: 28.2; Undocumented `intern-soft` feature with shorthands symbols Thierry Volpiatto
2022-11-12 12:42 ` Eli Zaretskii [this message]
2022-11-12 13:22   ` João Távora
2022-11-12 16:06     ` Thierry Volpiatto
2022-11-12 16:46       ` João Távora
2022-11-12 16:47         ` João Távora
2022-11-12 17:01         ` Eli Zaretskii
2022-11-12 17:18           ` João Távora
2022-11-12 17:49             ` Eli Zaretskii
2022-11-12 18:14               ` João Távora
2022-11-14  3:13                 ` Richard Stallman
2022-11-14  6:39                   ` João Távora
2022-11-14 13:11                     ` Eli Zaretskii
2022-11-14 13:38                       ` João Távora
2022-11-14 13:05                   ` Eli Zaretskii
2022-11-14 13:36                     ` João Távora
2022-11-14 13:56                       ` Eli Zaretskii

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=831qq8ny2m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59082@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=thievol@posteo.net \
    /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).