From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Weiner Subject: Re: Key binding popup interface Date: Wed, 13 Dec 2017 11:25:34 -0500 Message-ID: References: <87r2s3ctxh.fsf@ericabrahamsen.net> <87d13m3jt2.fsf@gmx.us> <87efo2wf0s.fsf@ericabrahamsen.net> <87y3m8s7ym.fsf@gmx.us> <87fu8gwfbr.fsf@nicolasgoaziou.fr> <87k1xs2h0h.fsf@gmx.us> Reply-To: rswgnu@gmail.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114c95865f689505603b39d5" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51879) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eP9rH-0002oz-RR for emacs-orgmode@gnu.org; Wed, 13 Dec 2017 11:26:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eP9rC-0002VR-ML for emacs-orgmode@gnu.org; Wed, 13 Dec 2017 11:26:11 -0500 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Kaushal Modi Cc: Oleh Krehel , emacs-org list , Stefan Monnier , emacs-devel --001a114c95865f689505603b39d5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Dec 13, 2017 at 10:40 AM, Kaushal Modi wrote: > On Tue, Dec 12, 2017 at 6:51 PM Robert Weiner wrote: > >> >> =E2=80=8BOne 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 bi= t >> 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? > =E2=80=8BC-h k shows the documentation for a key binding in a help buffer r= ather 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 t= o something more descriptive of what they do and then the particular colors associated could be customized to suit any particular visual theme. Bob --001a114c95865f689505603b39d5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Dec 13, 2= 017 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:

=E2=80=8BOne limitation of hydra ri= ght now is that it doesn't interface with the standard way of showing h= elp for key bindings since its keys aren't actually bound but handled v= ia internal hydra event handling.=C2=A0 With a bit of thought though, I thi= nk 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?

=E2=80=8BC-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 in= tegrating with standard key documentation lookup
capabilities if it gets i= ntegrated with core Emacs, which I would like to see.

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

Bob

--001a114c95865f689505603b39d5--