[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branch
From: |
Juri Linkov |
Subject: |
bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches |
Date: |
Thu, 22 Sep 2022 21:44:00 +0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) |
>> Another variant is to bind 'C-x v c' to a command that uses
>> 'read-key-sequence' to read a key sequence from the vc keymap,
>> then call a command with call-interactively while let-binding
>> vc-want-edit-command-p, like project--switch-project-command does.
>> Then e.g. 'C-x v c L' will have mnemonic "vc command for root log".
>
> That seems alright. Maybe we could use some symbol, e.g. '$' or '#',
> instead of a letter 'c', to distinguish its special status.
I see that 'c' might clash with a possible future command.
For example, git has a lot of commands whose names start
with the letter 'c': checkout, cherry-pick, clone, commit, ...
So the probability of the need to use 'c' is high.
OTOH, what key would keep the mnemonic of a prefix arg?
Maybe 'C-x v C-u'?
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, (continued)
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Juri Linkov, 2022/09/15
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/15
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Juri Linkov, 2022/09/16
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/18
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Juri Linkov, 2022/09/19
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/20
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Juri Linkov, 2022/09/21
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/21
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Juri Linkov, 2022/09/22
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/22
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches,
Juri Linkov <=
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/22
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Juri Linkov, 2022/09/23
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/23
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/24
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Juri Linkov, 2022/09/24
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/24
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Juri Linkov, 2022/09/25
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Sean Whitton, 2022/09/26
- bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches, Juri Linkov, 2022/09/27
- bug#57807: vc-edit-next-command (was bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches), Sean Whitton, 2022/09/27