all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: dalanicolai <dalanicolai@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Simple key guide package
Date: Tue, 24 May 2022 14:25:47 +0200	[thread overview]
Message-ID: <CACJP=3nk93hGB23z6wnDVnyUMJmz=QLHuzYn+X9U2Fag03CxEg@mail.gmail.com> (raw)
In-Reply-To: <871qwjmb4p.fsf@posteo.net>

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

Oops, thanks! Here is the correct link
https://github.com/dalanicolai/emacs-key-guide.

B.t.w. it does not add much to `pretty-hydra`, maybe I should just have
extended pretty hydra,
with a function that simply 'gathers' function names by giving it a list of
'key-strings'.
But I remembered that hydra was not a good option for `sketch-mode` so I
wanted to create
this anyway for that package.
And somehow it feels not right to create an extra keymap, just to have a
key-guide. But on the
other hand, that could also be just a better approach (that is hard to
'decide' ).

If anyone has some ideas about it, they are very welcome. Otherwise and in
any case this is just
very similar to pretty hydra, but without depending on the hydra package
and introducing extra
keymaps.

On Tue, 24 May 2022 at 13:19, Philip Kaludercic <philipk@posteo.net> wrote:

> dalanicolai <dalanicolai@gmail.com> writes:
>
> > I would like to inform you about some small project, named key-guide
> > <https://github.com/notifications>.
>
> You seem to have inserted the wrong link?
>

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

      reply	other threads:[~2022-05-24 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  6:56 Simple key guide package dalanicolai
2022-05-24 11:19 ` Philip Kaludercic
2022-05-24 12:25   ` dalanicolai [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACJP=3nk93hGB23z6wnDVnyUMJmz=QLHuzYn+X9U2Fag03CxEg@mail.gmail.com' \
    --to=dalanicolai@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.