I updated, and now it does not hang on the commit. thanks. I have observed this behaviour several times in the past on internal repositories, but there were large binaries in those repositories and I mentally blamed those binaries for hanging up tig. Normally we avoid large binaries in git repositories, but these were created by git-svn and we allow docx in subversion. I have no idea what git and tig tries to do with docx, but the hang was so serious I had to wait for a long time for the out-of-memory-killer to stop tig.
@svenn71 generally, Git and Tig shouldn't do much with binary files, you may want to add
*.docx binary to your .gitattributes, then it won't attempt to diff them as text
(alternatively you can define an external diff driver that knows how to compare docx files - can be as simple as converting docx to plaintext, and diffing the result)
it's strange that docx is not recognized as binary out-of-the-box though
Since we generally don't check in docx in git, I only get this in the cases where I 'transcode' old subversion projects to git to use the benefits of git. We allowed docx in subversion. With tortoisesvn, I can diff a docx against the previous version and something discovers that it is a docx and use the word diff function. with tortoisegit I get a diff view with junk in both panes. I have no idea who has the intelligence: svn, git or tortoise
we study the possibility to allow docx in git, but danger is that the initial git clone will blow up as the revisions of docx files increase. A shallow clone is not a solution for development. Things like git-annex is probably expecting too much from a novice user
Another question: do you know any TUI for gitlab?
For GitLab, git-bug might work. I'm using my own set of scripts that talk to the GitLab API. I hope to release that soon. It's quite convenient - I can browse commits in tig, and press a shortcut to write a review comment.
@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… :)
