From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eamonn Sullivan <eamonn.sullivan@gmail.com>
Cc: 45563@debbugs.gnu.org
Subject: bug#45563: 28.0.50; key-chord-mode not working with native comp
Date: Thu, 31 Dec 2020 13:56:42 +0000 [thread overview]
Message-ID: <xjfim8ijcyt.fsf@sdf.org> (raw)
In-Reply-To: <CABqzkqHiQNUnyk1_MJj0-DmGyZiHCt8LqBMbmW=kwLtWgZey8A@mail.gmail.com> (Eamonn Sullivan's message of "Thu, 31 Dec 2020 10:12:39 +0000")
Eamonn Sullivan <eamonn.sullivan@gmail.com> writes:
> My key chord definitions (the few I have) have stopped working. Example
> in the scratch buffer:
>
> (key-chord-define-global "JJ" 'previous-buffer)
> previous-buffer
> JJ
Hi Eamonn,
could you tell since are you experiencing this regression? Also have
you tried compiling without --with-nativecomp to verify the problem is
introduced by native compilation?
Thanks
Andrea
next prev parent reply other threads:[~2020-12-31 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 10:12 bug#45563: 28.0.50; key-chord-mode not working with native comp Eamonn Sullivan
2020-12-31 12:14 ` bug#45563: follow up on 45563 Eamonn Sullivan
2020-12-31 13:56 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
[not found] ` <CABqzkqEiECwMeza_hGReJ45C8SKwe6R7h-CewiVHieO3v50J+w@mail.gmail.com>
[not found] ` <CABqzkqEEz5NHq1Uk7zwQdeXV9PAoV4WO+Uwdex4wDWOv-iTZhw@mail.gmail.com>
2020-12-31 14:44 ` bug#45563: 28.0.50; key-chord-mode not working with native comp Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-31 15:11 ` Eamonn Sullivan
2020-12-31 14:32 ` Eli Zaretskii
[not found] ` <CABqzkqHuqfDrKPSX1E_V5MyhJVR7a0tG9DvhvXstb7NaCeBbOQ@mail.gmail.com>
2020-12-31 15:18 ` Eli Zaretskii
2020-12-31 15:30 ` Eamonn Sullivan
2021-01-03 14:26 ` Eamonn Sullivan
2021-01-03 20:00 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=xjfim8ijcyt.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=45563@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eamonn.sullivan@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 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).