Re: [PATCH] gitk: Add workaround for system where Shift-F5 mapped to Shift-XF86_Switch_VT_5
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 1, 2012, 17:27 UTC
- Message-ID
- <7vwqzacdb7.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <1349105191-31681-2-git-send-email-andrew.kw.w@gmail.com>
Andrew Wong <andrew.kw.w@gmail.com> writes:
Show 20 quoted lines
> The same workaround was used for Shift-F4 in:
> cea07cf8dc9b3677e0c50433c0d72bce83adbdc7
>
> Signed-off-by: Andrew Wong <andrew.kw.w@gmail.com>
> ---
> gitk-git/gitk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/gitk-git/gitk b/gitk-git/gitk
> index d93bd99..698b84a 100755
> --- a/gitk-git/gitk
> +++ b/gitk-git/gitk
> @@ -2496,6 +2496,7 @@ proc makewindow {} {
> bindkey f nextfile
> bind . <F5> updatecommits
> bind . <Shift-F5> reloadcommits
> + catch { bind . <Shift-Key-XF86_Switch_VT_5> reloadcommits }
> bind . <F2> showrefs
> bind . <Shift-F4> {newview 0}
> catch { bind . <Shift-Key-XF86_Switch_VT_4> {newview 0} }Wouldn't it make more sense to have a small helper function to wrap binding both <Shift-Fn> and <Shift-Key-XF86_Switch_VT_n> to the same thing and have F4 and F5 binding use that to avoid repetition?