From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Manuel Uberti <manuel.uberti@inventati.org>, 52158@debbugs.gnu.org
Subject: bug#52158: 29.0.50; Add key binding fo vc-git-stash
Date: Mon, 29 Nov 2021 15:12:19 +0100 [thread overview]
Message-ID: <87mtln59vg.fsf@gmail.com> (raw)
In-Reply-To: <87ilwb12t0.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 29 Nov 2021 14:58:35 +0100")
>>>>> On Mon, 29 Nov 2021 14:58:35 +0100, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Manuel Uberti <manuel.uberti@inventati.org> writes:
>>> Interesting, I didn't know about this. Although that's probably
>>> because when I do C-h m in vc-dir buffers I don't see key bindings
>>> related to stash-related commands, so I thought it was unbound.
>>
>> Actually, I've now discovered that P is bound to
>> vc-git-stash-pop-at-point when I move to a line that refers to a
>> stash, so I have no need for my previous wrapper any more.
>>
>> Thank you for pointing out the key binding. This can be closed, I guess.
Lars> I'm wondering whether we could make these commands more discoverable,
Lars> though. If you put point there and hit `C-h b', it'll list the
Lars> commands, but not elsewhere in the buffer (since these are text property
Lars> keymaps).
Lars> Anybody got any ideas here? Adding some text to the major mode doc
Lars> string about how there could be more commands available at certain
Lars> points in the "header" of the buffer?
Either that or add commands that go to the first stash and pops
etc. They'd have to unhide the stash list if it were hidden,
though (and I wouldnʼt bind the 'kill-stash' thingy).
Robert
--
next prev parent reply other threads:[~2021-11-29 14:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 8:36 bug#52158: 29.0.50; Add key binding fo vc-git-stash Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-28 13:51 ` Lars Ingebrigtsen
2021-11-28 13:55 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-28 14:12 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-29 13:58 ` Lars Ingebrigtsen
2021-11-29 14:03 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-29 14:12 ` Robert Pluim [this message]
2021-11-29 14:18 ` Lars Ingebrigtsen
2021-11-29 14:30 ` Robert Pluim
2021-11-29 14:40 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-29 15:32 ` Lars Ingebrigtsen
2021-11-29 22:16 ` Dmitry Gutov
2021-11-30 12:59 ` Lars Ingebrigtsen
2021-12-06 1:00 ` Dmitry Gutov
2021-12-06 5:42 ` Lars Ingebrigtsen
2021-12-06 6:29 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-06 6:31 ` Lars Ingebrigtsen
2021-12-06 6:32 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-06 8:58 ` Robert Pluim
2021-12-07 7:07 ` Lars Ingebrigtsen
2021-12-07 9:08 ` Robert Pluim
2021-12-07 12:56 ` Dmitry Gutov
2021-12-07 7:06 ` Lars Ingebrigtsen
2021-12-07 7:19 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-06 17:32 ` Juri Linkov
2021-12-07 5:06 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-29 17:12 ` Juri Linkov
2021-11-29 18:46 ` Lars Ingebrigtsen
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=87mtln59vg.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=52158@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=manuel.uberti@inventati.org \
/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).