#gitk — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gitk, aggregated by home.social.
-
Progress on gitlogui. Yes, exactly. A minimal UI for git log.
New:
- regex or simple search through the shown text
- commit graph (--graph option of git log) may be shownSuggestions of features to add are welcome.😀
Same for a professional layout suggestion for the seemingly randomly tossed text entries and check boxes of the UI.
-
Progress on gitlogui. Yes, exactly. A minimal UI to avoid reading the docs for all those who use it not that often, in particular with pickaxe options.
Now on codeberg: https://codeberg.org/harald/gitlogui
Suggestions of features to add are welcome.😀
-
New project.
If there is something I can't quite remember: the multitude of git log options. There should be a simple UI which makes this easier. Somewhat like gitk for git in general, but with as many useful options shown as understandable buttons as possible.
I also wanted to toy with tkinter a bit. The last few hours brought up this minimally functional thing, which seems to be a good start. Suggestions of features to add first are welcome.😀
-
Baffled by #gitk, configured to use the exact same font as my terminal (Inconsolata 12), failing to properly render a frame built from “BOX DRAWINGS DOUBLE” characters…
It really looks like what happens below (as if the font wasn't monospace):
```
╔══════════════════════════════════════════════════════════════════════════════╗
║ WARNING: SECURITY INFORMATION! ║
╚══════════════════════════════════════════════════════════════════════════════╝
``` -
Service reminder for situations where you
- have "lost" a git commit due to messing with reset or similar
- want to get a better understanding how git works (my simplified view: commits with named pointers on it, some of which move automatically when committing, branches, some don't, tags)Use
gitk --reflog
-
Service reminder for situations where you
- have "lost" a git commit due to messing with reset or similar
- want to get a better understanding how git works (my simplified view: commits with named pointers on it, some of which move automatically when committing, branches, some don't, tags)Use
gitk --reflog
-
Service reminder for situations where you
- have "lost" a git commit due to messing with reset or similar
- want to get a better understanding how git works (my simplified view: commits with named pointers on it, some of which move automatically when committing, branches, some don't, tags)Use
gitk --reflog
-
My new preferred way to run gitk:
#!/bin/bash
if [ "$#" -eq 0 ]; then
/bin/gitk --reflog &
else
exec /bin/gitk "$@"
fiWhich means: even if I really mess up my git working directory, with --reflog I'll see each and every available commit, branched or tagged or not and it is easy to resurrect "lost" commits.
Not that I frequently mess up, but I somehow got used to see it all.😀
-
Finally spent 5 minutes to check whether I was missing an obvious #gitk option to avoid tag's getting shortened as “tag...” when I'm looking at some-customer/some-version tags.
Hardcoded in “drawtags” but trivial to tweak:
set maxtagpct 25 → set maxtagpct 50
-
I’ve been using Git, whilst basically, for well over a decade now. Have tried several clients and occasionally commit stuff with VSCode. But after all these years I still think Git GUI, though ugly it may be, is still the best graphical client :-). And gitk for viewing the history of a repository.
#git #gitk