From: "Jakub T. Jankiewicz" <jcubic@jcubic.pl>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, 67182@debbugs.gnu.org
Subject: bug#67182: 29.1; read-kbd-macro always return a vector
Date: Wed, 15 Nov 2023 14:20:55 +0100 [thread overview]
Message-ID: <20231115142055.3ab964d9@jcubic> (raw)
In-Reply-To: <jwvpm0bnr4y.fsf-monnier+emacs@gnu.org>
Then maybe the documentation for the function should be updated and in
changelog there is should a note about this breaking change.
On Wed, 15 Nov 2023 07:45:16 -0500
Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> >> This is the code I was always using in Emacs to send raw keys
> >> to modes like ansi-term:
> >>
> >> (defun raw (str)
> >> (interactive "sSend Raw Key: ")
> >> (term-send-raw-string (read-kbd-macro str)))
> >>
> >> But this doesn't work anymore it throw an error [3] when calling:
> >>
> >> (raw "C-c")
>
> The above code already threw the same error when you call
>
> (raw "C-<mouse-1>")
> or
> (raw "M-a")
> or
> (raw "é")
>
> :-(
>
> Maybe it should be something like
>
> (defun raw (str)
> (interactive "sSend Raw Key: ")
> (let ((keys (kbd str))
> (string (condition-case err
> (concat "" keys)
> (wrong-type-argument
> (let ((elem (nth 2 err)))
> (error "%s is not a character"
> (if (numberp elem)
> (prin1-char elem)
> elem)))))))
> (term-send-raw-string string)))
>
> ?
>
> >> According to documentation `C-h f read-kbd-macro`
> >> "The result will be a string if possible" but it seems that in new
> >> GNU Emacs it's always a vector.
> > Stefan, this is due to your change in edmacro-parse-keys as part of
> > commit 87789330, whose log message says nothing about
> > edmacro-parse-keys. Did you really intend to make that
> > backward-incompatible change? If so, why?
>
> Yes. I want to eliminate the use of strings that stand for a sequence
> of events because it does nothing more than leave latent bugs and create
> confusion (between the strings used as input to `read-kbd-macro` and the
> strings that used to be output by `read-kbd-macro`), while increasing
> the complexity of the rest of the code which has to handle both vectors
> and strings.
>
>
> Stefan
>
--
Jakub T. Jankiewicz, Senior Front-End Developer
https://jcubic.pl/me
https://koduj.org
next prev parent reply other threads:[~2023-11-15 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 1:05 bug#67182: 29.1; read-kbd-macro always return a vector Jakub T. Jankiewicz
2023-11-15 12:14 ` Eli Zaretskii
2023-11-15 12:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-15 13:20 ` Jakub T. Jankiewicz [this message]
2023-11-18 9:54 ` 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=20231115142055.3ab964d9@jcubic \
--to=jcubic@jcubic.pl \
--cc=67182@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).