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

Re: reducing line crossings in gitk

From
Paul Mackerras <paulus@samba.org>
Date
Jun 15, 2005, 11:18 UTC
Message-ID
<17072.3723.242985.824999@cargo.ozlabs.ibm.com>
In-Reply-To
<7v8y1gvjfz.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano writes:
>  - What support from the core GIT side would you need if you
>    wanted to let users browse a remote repo?  A way to inspect
>    what is under ".git/refs/" hierarchy on the remote side?
>    Anything else?

I would need git-rev-list, git-cat-file, and git-diff-tree to be able to operate on the remote repository.

Show 5 quoted lines
>  - Pasting into the SHA1 field to "Go To" was a nuisance when
>    the field already had a string in it.  Clearing the SHA1
>    field when focus gets in would be one way to solve it, but
>    then you would lose the way to pasting out of that field, so
>    I do not know what to suggest offhand.

I could rebind the middle mouse button to replace the contents of the sha1 field with the selection instead of inserting it.

>  - How do I "Find" backwards?  Not being able to find a way to
>    do this was the most annoying thing for me.

The "?" key is bound to find backwards (i.e. select previous match) and the "/" key is bound to find forwards (select next match). I don't have a button for find backwards (and I'd rather not clutter it up by adding one, but maybe I could add a menu item for it).

>  - After typing something in "Find" and hitting <ENTER>, if the
>    focus stays in it and lets me hit <ENTER> again to go to the
>    next one would be nicer.  Somehow hitting <ENTER> again would
>    not do this for me right now.

Hmmm, if the focus stays in the find field then you can't use "?", up, down, etc. I could make <enter> do find-next if you like.

Show 6 quoted lines
>  - Indicaing "Find" wrapping around without annoying the user
>    too much (i.e. I do _not_ want you to add "Find reached the
>    beginning of time, wrapping around and continuing from the
>    top" pop-up window) would be nicer.  Currently I can tell by
>    looking at the scrollbar on the history pane jumping back, so
>    this is not a big issue, though.
I could make it beep - how about that?
Show 9 quoted lines
>  - Can I have a way to "Find" next commit that touches a given
>    pathname?
> 
>     $ git-rev-list | git-diff-tree -s -r --stdin '<that pathname>'
> 
>    which would give you a sequence of lines that look like:
>        "commit-SHA1 (from parent-commit-SHA1)"
> 
>    you would pick the commit-SHA1 from the output and jump to it.
Interesting idea... I could add a "Path" entry to the find type menu.
Show 5 quoted lines
>  - In addition to "Find" which looks at the commit message, can I
>    have one that uses pickaxe to find changes?
> 
>  - Can I have an option to use diffcore options to tweak the
>    diff that is shown in the lower-left pane?
Also interesting ideas, I'll see what I can do.

Regards, Paul.

Previous: Junio C HamanoNext: Jon Seymour
Message 3 of 7 in “reducing line crossings in gitk”
  1. Paul MackerrasJun 11, 2005
  2. Junio C HamanoJun 11, 2005
  3. Paul MackerrasJun 15, 2005
  4. Jon SeymourJun 15, 2005
  5. Paul MackerrasJun 16, 2005
  6. Jon SeymourJun 16, 2005
  7. Matthias UrlichsJun 12, 2005

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.