unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Weiner <rsw@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Oleh Krehel <oleh@oremacs.com>,
	emacs-org list <emacs-orgmode@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Key binding popup interface
Date: Wed, 13 Dec 2017 11:25:34 -0500	[thread overview]
Message-ID: <CA+OMD9g2A3Z0gh17h1pSqA3e6urF1pXgzB+K_tvhkSxjAZmUsw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY1uMppXshgiujU7AuzYG_jshM+N03swjEP1pG_s_Ozv7g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

On Wed, Dec 13, 2017 at 10:40 AM, Kaushal Modi <kaushal.modi@gmail.com>
wrote:

> On Tue, Dec 12, 2017 at 6:51 PM Robert Weiner <rsw@gnu.org> wrote:
>
>>
>> ​One limitation of hydra right now is that it doesn't interface with the
>> standard way of showing help for key bindings since its keys aren't
>> actually bound but handled via internal hydra event handling.  With a bit
>> of thought though, I think it could be integrated well.
>>
>
> I don't follow what the functional limitations are of what you said. How
> does your concern affect a package author or the end user?
>

​C-h k shows the documentation for a key binding in a help buffer rather
than just a laid out summary of all the keys in a particular hydra map.
C-h k is important to know the details of what individual keys do, so
hydra needs a way of integrating with standard key documentation lookup
capabilities if it gets integrated with core Emacs, which I would like to
see.

Personally, I also think the red, blue, etc. color notation should change to
something more descriptive of what they do and then the particular colors
associated could be customized to suit any particular visual theme.

Bob

[-- Attachment #2: Type: text/html, Size: 2985 bytes --]

  reply	other threads:[~2017-12-13 16:25 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 [this message]
2017-12-13  6:52               ` John Wiegley
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=CA+OMD9g2A3Z0gh17h1pSqA3e6urF1pXgzB+K_tvhkSxjAZmUsw@mail.gmail.com \
    --to=rsw@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=oleh@oremacs.com \
    --cc=rswgnu@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).