unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#67768: Feature request: expand IELM working buffer's read-symbol shorthands
@ 2023-12-11 15:59 Brandon Irizarry
  0 siblings, 0 replies; only message in thread
From: Brandon Irizarry @ 2023-12-11 15:59 UTC (permalink / raw)
  To: 67768

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

I'm currently running Emacs master branch (I just pulled and rebuilt a few
minutes ago).

I think it would be nice if IELM let you use the read-symbol shorthands you
first defined
in the buffer you now set as your IELM working buffer.

For example, say I edit /tmp/example.el, in the buffer "example.el". It
contains
the following:

(symbol-name 't-foo)

;; Local Variables:
;; read-symbol-shorthands: (("t-" . "tmp-"))
;; End:

If I evaluate the call to symbol-name, I get "tmp-foo", which is expected.
Now, let's say I open IELM, and
set my working buffer to "example.el". I can evaluate
read-symbol-shorthands:

ELISP> read-symbol-shorthands
(("t-" . "tmp-"))

This makes sense, since these are the shorthands for the working buffer.
But I can't actually use them! For example,
if I evaluate (symbol-name 't-foo) in the IELM session, I get "t-foo".
Unlike, say, in the minibuffer, the shorthand
isn't expanded in this context.

Ideally, the shorthand should be expanded, and I should be able to get
completion for things that use shorthands, just
as I would in the original buffer.

What do folks think here?

- Brandon

[-- Attachment #2: Type: text/html, Size: 1599 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-12-11 15:59 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-12-11 15:59 bug#67768: Feature request: expand IELM working buffer's read-symbol shorthands Brandon Irizarry

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).