git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] gitk: Fix nextfile() and more

From
Junio C Hamano <junkio@cox.net>
Date
Sep 26, 2006, 05:24 UTC
Message-ID
<7vpsdjryj2.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<873bag12k3.fsf@duaron.myhome.or.jp>
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
Show 14 quoted lines
> The current nextfile() jumps to last hunk, but I think this is not
> intention, probably, it's forgetting to add "break;". Right?  And this
> patch also adds prevfile(), it jumps to previous hunk.
>
> The following part is just my favorite the key-binds, it doesn't matter.
>
> +    bind . <Control-p> "$ctext yview scroll -1 units"
> +    bind . <Control-n> "$ctext yview scroll 1 units"
> +    bind . <Alt-v> "$ctext yview scroll -1 pages"
> +    bind . <Control-v> "$ctext yview scroll 1 pages"
> +    bindkey P prevfile
> +    bindkey N nextfile
>
> What do you think of this?
. As a patch e-mail, the initial Hi and trailing Thanks add
  additional work for the person who applies patch.
. ACK on missing "break" and addition of prevfile for symmetry.
. I do not have preference on the extra bindings.  I do not
  speak for Paul, but I suspect he would have liked them in a
  separate patch.
Previous: OGAWA HirofumiNext: OGAWA Hirofumi
Message 2 of 7 in “gitk: Fix nextfile() and more”
  1. gitk: Fix nextfile() and moreOGAWA Hirofumi, Sep 25, 2006
  2. Junio C HamanoSep 26, 2006
  3. OGAWA HirofumiSep 26, 2006
  4. gitk: Fix nextfile() and add prevfile()OGAWA Hirofumi, Sep 26, 2006
  5. gitk: add some key-bindOGAWA Hirofumi, Sep 26, 2006
  6. Paul MackerrasSep 27, 2006
  7. OGAWA HirofumiSep 27, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.