From: Thomas Walker Lynch via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Andreas Schwab <schwab@suse.de>,
Noam Postavsky <npostavs@gmail.com>,
22673@debbugs.gnu.org
Subject: bug#22673: execute-kbd-macro doesn't handle strings with characters in range (0x80..0xFF) correctly
Date: Sat, 29 Jan 2022 19:01:05 +0100 [thread overview]
Message-ID: <CAGxFmCO6fBzF-Dm8zKWjcd1W4awOCqKiq5+1RSj9pHb+7XndxA@mail.gmail.com> (raw)
In-Reply-To: <87mtje7a1t.fsf_-_@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
It has been so long that I only vaguely remember it in the first place.
That is one way to make a bug report moot. LOL
On Sat, Jan 29, 2022 at 5:59 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Andreas Schwab <schwab@suse.de> writes:
>
> >> (execute-kbd-macro [?¬]) works, but shouldn't the string version work
> >> too? I see that it fails because of this statement in keyboard.c:
> >
> > Strings as key sequence are legacy and can only contain ASCII and
> > Meta-ASCII characters.
>
> So I guess there's nothing to fix here, and I'm closing this bug report.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
[-- Attachment #2: Type: text/html, Size: 1266 bytes --]
prev parent reply other threads:[~2022-01-29 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 2:10 bug#22673: 24.5; global set key neg freaks out emacs Thomas Lynch
2016-02-15 8:44 ` Alexis
2016-02-15 10:20 ` Andreas Schwab
2016-02-15 12:42 ` Alexis
2016-02-15 13:03 ` Andreas Schwab
2016-02-15 13:24 ` Thomas Lynch
2018-06-06 0:02 ` Noam Postavsky
2018-06-06 7:39 ` Andreas Schwab
2022-01-29 16:59 ` bug#22673: execute-kbd-macro doesn't handle strings with characters in range (0x80..0xFF) correctly Lars Ingebrigtsen
2022-01-29 18:01 ` Thomas Walker Lynch via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=CAGxFmCO6fBzF-Dm8zKWjcd1W4awOCqKiq5+1RSj9pHb+7XndxA@mail.gmail.com \
--to=bug-gnu-emacs@gnu.org \
--cc=22673@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
--cc=schwab@suse.de \
--cc=thomas.lynch@reasoningtechnology.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.