@kaddkaka I've written some documentation for my offline GitLab review workflow and published my script here: https://gitlab.com/krobelus/gitlab-offline-review
I'm sure it has some rough edges, but writing review comments while browsing commits in Tig already feels so much better than GitLab.
I'm sure it has some rough edges, but writing review comments while browsing commits in Tig already feels so much better than GitLab.
@kaddkaka
A two-dotted commit range like
@{u} is an abbreviation for @{upstream}, which is usually something like origin/master, i.e. the remote tracking branch. man gitrevisions should explain that trick.A two-dotted commit range like
A..B means: all the commits that are in B, minus the commits that are in A. Here, HEAD is implied, so it's the same as @{u}..HEAD.
I often use something like that when I'm only interested in the commits on my topic branch.
@{u}..topic gives me those.
unfortunately the regarding
tig log -p I think I might as well use git log -p or just manually step through commits and search. Unless there is some way to toggle between regular tig view and tig log view
oh commit tree view (main?) and instead of a split with
diff-view, show git log -p in the right pane
that would be nice
tig path/to/file.cc -L500,+1 gives same result as without -L, .. oh do I need log as well?
but the diff view is empty if I do that :/
i just downloaded tig, very nice. what are peoples common use cases for tig? it's a nice git browser but apart from browsing, what are peoples main use cases? so i can make full use of it :D
I think im a basic user for 5 years. I have some bindings for doing auto squashing but it's not without quirks
Ok, I've found it. But there's one problem: after selecting a file it opens in a pager which from this point comes up directly whenever the file-filter view is invoked. I.e.: for consecutive bringings of this view a previous selection (previous file) is shown and no selection is being allowed. I see that it opens [pager] view. Is there a way to reset it? I would guess that IMO this is needed to resolve this. So, how to "reset" [pager] view?
I have one more question – could I start up TIG with some columns like ID/SHA shown via command line options? Like: tig reflog --pretty=raw | tig --pretty=raw --Show-sha. Is there something like --Show-sha option or a way to execute a :set command on startup?
I have an idea for a cool feature request – EditAll – to open an editor with all filles from a foremost commit passed as arguments :)
Think of it – tig as a central console place (it already has such connotations, I very often open editor(s) from tig) of the console – the place where editor sessions are being kept ↔ i.e.: the sets of files related to each other by a feature and edited together… :)
vim users should give this plugin a try! Prevents vim processes from nesting as child processes. https://github.com/iberianpig/tig-explorer.vim
I have a super-useful configuration – a bind to <Enter> that opens up this simple Zsh script on '%(text)' passed as 1st argument:
This message was deleted
#!/usr/bin/env zsh
emulate zsh -o extended_glob
if [[ $1 == (#b)([^:]##):([0-9]##):* ]]; then
[[ -z $EDITOR ]] && EDITOR=mcedit
$EDITOR +$match[2] **/$match[1];t
fi
It allows to open the compiler error-line by pointing cursor and pressing enter. It will automatically jump to the line with the error.
So, :!make and browse freely :)
though why would you execute Make in Tig, and not your editor?
Guys, I've submitted an interesting PR (#1139); autoscroll and colorizing of compiler errors in pager view, to implement this simple IDE-like round-trip error fixing use case: https://asciinema.org/a/430460. You can
have this functionality also without the PR, just without autoscroll and colorizing of errors, as described in the PR.