From: Drew Adams <drew.adams@oracle.com>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 43709@debbugs.gnu.org
Subject: bug#43709: minibuffer keybinding cheatsheet and launcher [CODE SUBMISSION]
Date: Tue, 29 Sep 2020 12:05:23 -0700 (PDT) [thread overview]
Message-ID: <85477a60-4296-4ae5-9ce9-a82b8787dec4@default> (raw)
In-Reply-To: <20200929182219.5r5nbvmipo33l24q@E15-2016.optimum.net>
> Oh. Had I known... Would I? / Wouldn't have I?
Yes, you should. And thanks for doing so.
Dunno whether filing a bug is the best way to
provide it, but that will work, no doubt.
Another possibility is to use emacs-devel@gnu.org.
Many more people read that mailing list,
including most who also pay attention to the
bug list.
> BACKGROUND: ...
> ATTACHED: ...
> FOLLOW-UP: ...
That all sounds good. Keep it up.
FYI: Another related library is `which-key.el',
which you may already be aware of.
https://github.com/justbur/emacs-which-key
next prev parent reply other threads:[~2020-09-29 19:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 16:59 bug#43709: minibuffer keybinding cheatsheet and launcher [CODE SUBMISSION] Boruch Baum
2020-09-29 17:41 ` Drew Adams
2020-09-29 18:22 ` Boruch Baum
2020-09-29 19:05 ` Drew Adams [this message]
2020-09-29 18:26 ` Boruch Baum
2020-10-01 13:51 ` Stefan Monnier
2020-10-01 15:31 ` Boruch Baum
2020-10-01 16:04 ` Stefan Monnier
2020-10-01 20:46 ` Boruch Baum
2020-10-01 18:25 ` Boruch Baum
2020-10-02 7:14 ` bug#43709: minibuffer keybinding cheatsheet and launcher [V2 CODE SUBMISSION] Boruch Baum
2020-10-02 18:24 ` Drew Adams
2020-10-15 18:53 ` bug#43709: minibuffer keybinding cheatsheet and launcher [V3 " Boruch Baum
2020-10-15 18:57 ` Drew Adams
2021-07-21 12:14 ` bug#43709: minibuffer keybinding cheatsheet and launcher [CODE SUBMISSION] Lars Ingebrigtsen
2021-07-21 13:48 ` Boruch Baum
2021-07-22 6:49 ` Phil Sainty
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=85477a60-4296-4ae5-9ce9-a82b8787dec4@default \
--to=drew.adams@oracle.com \
--cc=43709@debbugs.gnu.org \
--cc=boruch_baum@gmx.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).