3 replies
bind generic xrc !sh -c "$EDITOR $HOME/.tigrc"
How to reload the configuration?
Hi! I'm new to tig. I have searched in the manual but couldn't find: Can I start up in the diff view? i.e. instead of running
tig and then pressing d, can I do this in a single command? I've tried git diff | tig but that's different from the diff view as it doesn't support jumping to the diff of a file.
@ouuan Well, you are looking for
Though it is a little counter-intuitive, but already written in manual:
https://jonas.github.io/tig/doc/tig.1.html
tig showThough it is a little counter-intuitive, but already written in manual:
https://jonas.github.io/tig/doc/tig.1.html
@ouuan Well, you are looking for
tig show
Though it is a little counter-intuitive, but already written in manual:
https://jonas.github.io/tig/doc/tig.1.html
tig show shows the latest commit like git show. Can I use it to show the unstaged changes like git diff?
I've tried
git diff | tigbut that's different from the diff view as it doesn't support jumping to the diff of a file.
I just realized that the diff view of the unstaged changes doesn't support jumping to the diff of a specific file. However, it supports using the @ key to jump to the diff of the next file, while git diff | tig doesn't.
Hey all
Has anyone here seen tig's bash completion flat out stop working when upgrading to a later tig version, like 2.4 or 2.5?
I'm on Gentoo. All other bash completion works fine. Tig's used to work fine, also.
https://github.com/jonas/tig/issues?q=is%3Aissue+bash doesn't find anything obviously relevant
2.5.1 did ship jonas/tig#795 - but I can't tell why it wouldn't work
I've been trying to port the CI to GitHub Actions, and I get this error:
I think GitHub Actions does not provide a TTY, maybe this should be done with something like expect or tmux?
/home/runner/work/tig/tig/test/tools/libtest.sh: line 34: /dev/tty: No such device or address https://github.com/krobelus/tig/runs/1657107799?check_suite_focus=trueI think GitHub Actions does not provide a TTY, maybe this should be done with something like expect or tmux?
sometimes when browsing a repository, tig 'hangs' and makes my machine so busy I can't even drop to a shell and kill it. I guess this happens when the diff blob becomes huge and maybe contains binary data. I am investigating into what is causing this, but maybe other users have same experience. I build from git and try to keep tig as up to date as possible. This issue is not something new, it has been ongoing for a while.
@svenn71 there is a recently fixed bug when viewing diffs of files with non-UTF-8 encodings (jonas/tig#1087)
I assume it's not that?
I assume it's not that?
Try if you can reproduce it consistently - if it blocks the rest of your machine you could run it like
timeout -s9 10 tig or something
and there is mention of utf-* things in the forum for ngspice on sourceforge
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