From: Eamonn Sullivan <eamonn.sullivan@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: 45563@debbugs.gnu.org
Subject: bug#45563: 28.0.50; key-chord-mode not working with native comp
Date: Thu, 31 Dec 2020 15:11:26 +0000 [thread overview]
Message-ID: <CABqzkqFGrQkPx+d-kdCMFVGXRvTr9g1ycWsj8vOJYtv+BNo5Tg@mail.gmail.com> (raw)
In-Reply-To: <xjfa6tujar1.fsf@sdf.org>
[-- Attachment #1: Type: text/plain, Size: 2466 bytes --]
Hi Andrea,
It's probably an issue with use-package, or use-package-chords.
Here's the smallest config that I could conjure that seems to reproduce the
issue:
https://github.com/eamonnsullivan/emacs.d/blob/master/minimal-init.el
I start that with: emacs -Q -nw -l ~/git/emacs.d/minimal-init.el
Native compile completes, but "JJ" does nothing.
Hope that helps,
Eamonn
On Thu, 31 Dec 2020 at 14:44, Andrea Corallo <akrl@sdf.org> wrote:
>
> [re-adding the bug in Cc]
>
> Eamonn Sullivan <eamonn.sullivan@gmail.com> writes:
>
> > Hi, sorry, said something incorrect:
> >
> > I am *not* able to reproduce the problem when running emacs -q. Key
> chords work -- I had forgotten to run key-chord-mode.
> >
> > But I don't think I'm triggering native-comp when I do that.
>
> Native compilation should be always available.
>
> I think would be helpful some reduced reproducer if you can poke a
> little at it trying to produce it.
>
> Thanks
>
> Andrea
>
> > Hope that helps,
> > Eamonn
> >
> > On Thu, 31 Dec 2020 at 14:16, Eamonn Sullivan <eamonn.sullivan@gmail.com>
> wrote:
> >
> > Hi Andrea,
> >
> > I only use key chords for one thing: QQ to bring up a hydra for
> straight.el. This was working in the last couple of
> > days. (I used to use it for other things, but kept accidentally
> triggering it...)
> >
> > This is my configuration, if it helps:
> https://github.com/eamonnsullivan/emacs.d
> >
> > I load use-package-chords in init-global-behaviour.el.
> >
> > However, I also seem to be able to reproduce the issue by starting
> emacs with -q and loading and eval'ing
> > key-chord.el (from
> https://github.com/emacsorphanage/key-chord/blob/master/key-chord.el), so
> might not be related to
> > native-comp. That was just my first thought. It seems to be wrong!
> >
> > Thanks for looking into this!
> >
> > -Eamonn
> >
> > On Thu, 31 Dec 2020 at 13:56, Andrea Corallo <akrl@sdf.org> wrote:
> >
> > 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
> >
>
> --
> akrl@sdf.org
>
[-- Attachment #2: Type: text/html, Size: 3912 bytes --]
next prev parent reply other threads:[~2020-12-31 15:11 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 ` 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
[not found] ` <CABqzkqEiECwMeza_hGReJ45C8SKwe6R7h-CewiVHieO3v50J+w@mail.gmail.com>
[not found] ` <CABqzkqEEz5NHq1Uk7zwQdeXV9PAoV4WO+Uwdex4wDWOv-iTZhw@mail.gmail.com>
2020-12-31 14:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-31 15:11 ` Eamonn Sullivan [this message]
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=CABqzkqFGrQkPx+d-kdCMFVGXRvTr9g1ycWsj8vOJYtv+BNo5Tg@mail.gmail.com \
--to=eamonn.sullivan@gmail.com \
--cc=45563@debbugs.gnu.org \
--cc=akrl@sdf.org \
/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).