[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: |
Sean Whitton |
Subject: |
bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches |
Date: |
Sat, 24 Sep 2022 12:20:50 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Hello,
On Fri 23 Sep 2022 at 09:42AM +03, Juri Linkov wrote:
>>>> 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'?
>>
>> Might be confusing if you need to do C-u C-x v C-u C-x v b l ...
>>
>> '$' and '!' have shell command mnemonics.
>
> I didn't recognize '$' and '#' as shell-related symbols here
> because in Emacs they have another semantics: e.g.
> 'C-x #' is 'server-edit', 'M-$' is ispell-checking, etc.
>
> But 'M-!' has a clear connection with editing a shell command. So
> 'C-x v !' looks like the best candidate among all considered so far.
I'm running into the problem that you pointed out in another thread.
How do we apply vc-filter-command-function to the final VC command
that's to be run without also applying it to intermediate VC commands,
e.g. in vc-read-revision?
--
Sean Whitton
- 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/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, 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, 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 <=
- 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
- bug#57807: vc-edit-next-command (was bug#57807: 29.0.50; Make vc-print-branch-log able to log multiple branches), Juri Linkov, 2022/09/28
- 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/28