From: "John Wiegley" <johnw@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-orgmode@gnu.org, emacs-devel@gnu.org
Subject: Re: Key binding popup interface
Date: Tue, 12 Dec 2017 22:52:41 -0800 [thread overview]
Message-ID: <m2374ff7ba.fsf@newartisans.com> (raw)
In-Reply-To: <jwvr2rzr7de.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Tue, 12 Dec 2017 16:01:09 -0500")
>>>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
SM> I have no opinion on that part, but if a part of Hydra would be useful for
SM> other packages, then it'd be good to split it out: for me "Hydra" means
SM> "define a Hydra via defhydra or something like that", so if you tell me to
SM> use Hydra to "show the available valid key bindings", I wouldn't know
SM> where to start.
Plus, there are other, less intrusive way to achieve "show the available valid
key bindings", such as the which-key package.
I think one area where Hydras come into their own is that once you have the
Hydra active, it stays active, allowing you to chain together many single-
letter commands.
For example, you could have a hydra for "large-scale syntactic structures",
where repeated uses of n/p are mapped to what C-c C-n and C-c C-p usually do
in modes like cc-mode.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2017-12-13 6:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r2s3ctxh.fsf@ericabrahamsen.net>
[not found] ` <87d13m3jt2.fsf@gmx.us>
[not found] ` <87efo2wf0s.fsf@ericabrahamsen.net>
[not found] ` <87y3m8s7ym.fsf@gmx.us>
[not found] ` <87fu8gwfbr.fsf@nicolasgoaziou.fr>
[not found] ` <87k1xs2h0h.fsf@gmx.us>
2017-12-12 14:02 ` Key binding popup interface (Was: Re: Poll: new keybinding for org-insert-structure-template on org mode list) Kaushal Modi
2017-12-12 18:45 ` Key binding popup interface Eric S Fraga
2017-12-12 18:56 ` Kaushal Modi
2017-12-12 19:53 ` Alan E. Davis
2017-12-12 20:09 ` Key binding popup interface (Was: Re: Poll: new keybinding for org-insert-structure-template on org mode list) Charles A. Roelli
2017-12-12 20:20 ` Kaushal Modi
2017-12-12 21:18 ` Key binding popup interface Stefan Monnier
2017-12-12 21:28 ` Kaushal Modi
2017-12-13 11:49 ` Michael Heerdegen
2017-12-13 19:56 ` Key binding popup interface (Was: Re: Poll: new keybinding for org-insert-structure-template on org mode list) Charles A. Roelli
2017-12-12 20:20 ` Key binding popup interface Eric Abrahamsen
2017-12-12 20:33 ` Kaushal Modi
2017-12-12 20:44 ` Eric Abrahamsen
2017-12-12 20:56 ` Kaushal Modi
2017-12-12 21:01 ` Stefan Monnier
2017-12-12 21:19 ` Kaushal Modi
2017-12-12 21:48 ` Stefan Monnier
2017-12-13 15:38 ` Kaushal Modi
2017-12-13 16:18 ` Stefan Monnier
2017-12-12 23:51 ` Robert Weiner
2017-12-13 15:40 ` Kaushal Modi
2017-12-13 16:25 ` Robert Weiner
2017-12-13 6:52 ` John Wiegley [this message]
2017-12-13 15:43 ` Kaushal Modi
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=m2374ff7ba.fsf@newartisans.com \
--to=johnw@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-orgmode@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).