Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 28 2019 22:21
    verdie-g opened #893
  • Jan 28 2019 10:19
    VonUniGE commented #340
  • Jan 28 2019 02:20
    rcywongaa closed #869
  • Jan 26 2019 20:30
    smkniazi edited #892
  • Jan 26 2019 20:29
    smkniazi edited #892
  • Jan 26 2019 20:28
    smkniazi opened #892
  • Jan 24 2019 10:38
    timotheecour edited #890
  • Jan 24 2019 09:20
    timotheecour opened #891
  • Jan 24 2019 00:29
    timotheecour opened #890
  • Jan 23 2019 22:09
    KeeReal commented #869
  • Jan 23 2019 20:58
    avivey opened #889
  • Jan 21 2019 23:26
    timotheecour commented #559
  • Jan 21 2019 21:16
    koutcher commented #559
  • Jan 21 2019 20:47
    koutcher commented #559
  • Jan 21 2019 18:39
    smancill commented #559
  • Jan 21 2019 07:11
    timotheecour commented #559
  • Jan 20 2019 17:01
    smancill commented #559
  • Jan 20 2019 10:25
    koutcher commented #559
  • Jan 20 2019 02:54
    timotheecour commented #559
  • Jan 20 2019 01:56
    timotheecour opened #888
Ivan Sevcik
@isevcik
Hello, is it possible to locate a file in finder f and then show a log for selected file?
3 replies
Pavel Roskin
@proski
Any chance to see a new release soon? I really appreciate that my changes for vertical lines in Putty were accepted. I would be happy to make a custom package for my colleagues who are stuck with Putty and Windows, and I don't want to make it from a git snapshot.
Sebastian Gniazdowski
@psprint
Sharing a keybinding:
bind generic xrc !sh -c "$EDITOR $HOME/.tigrc"
How to reload the configuration?
Sebastian Gniazdowski
@psprint
Guessed it – it's :source …path…
Sebastian Gniazdowski
@psprint
I have a question: how to show a message after the source ~/.tigrc? In a binding?
Shuji Koike
@shuji-koike_gitlab
@here Hi, folks!
I have a question: In main view, is there a way to only show commits of head of the branches?
Shuji Koike
@shuji-koike_gitlab
Ok, I'm getting closer.
running tig --all with set main-options = -n 1000 --simplify-by-decoration is bascally what I wanted :)
I's there a way to make --simplify-by-decoration to toggle with a single key?
Brian Spilner
@Try2Code
mornin! I was wondering about the stash view: what commands does it offer?
Brian Spilner
@Try2Code
I thought, maybe there are keys to pop or apply them ...
Hsieh Chin Fan
@typebrook
@Try2Code FYI, this is my key bindings for stash view:
curl -s https://raw.githubusercontent.com/typebrook/settings/dev/tigrc | grep 'bind stash'
Hsieh Chin Fan
@typebrook
@shuji-koike_gitlab In this case, a new tig instance works. You can also press q to quit to your current tig instance.
bind main Y >sh -c "tig --all --simplify-by-decoration"
Yufan You
@ouuan
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.
Hsieh Chin Fan
@typebrook
@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
Yufan You
@ouuan

@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?

Yufan You
@ouuan

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.

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.

Leho Kraav
@lkraav

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

Frédéric G. MARAND
@fgm
Hello. One one server, the "lines" (/, \, |, *) are replaced by x,o,q,j characters. Any suggestion how I could fix this ?
Frédéric G. MARAND
@fgm
actually, it's even stranger, its one one repo on that server, not on the other repos
Johannes Altmanninger
@krobelus
I've been trying to port the CI to GitHub Actions, and I get this error: /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=true
I think GitHub Actions does not provide a TTY, maybe this should be done with something like expect or tmux?
svenn71
@svenn71
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.
Johannes Altmanninger
@krobelus
@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?
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
svenn71
@svenn71
commit 'b9c061743 svg hardcopy example' of branch 'pre-master' of 'remote.origin.url=git://git.code.sf.net/p/ngspice/ngspice' did cause problem on my tig which is '9fb0a2f (HEAD -> master, origin/master, origin/HEAD) Restore lazy navigation'
and there is mention of utf-* things in the forum for ngspice on sourceforge
Johannes Altmanninger
@krobelus
@svenn71 try updating again, you are missing the encoding fix (2305fe6f471be757c609d19a0fde1eadc6e3a57d) which was merged yesterday
svenn71
@svenn71
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.
Johannes Altmanninger
@krobelus
If you often get OOMs , I recommend something like "earlyoom" - it avoids having to wait
@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
svenn71
@svenn71
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
kaddkaka
@kaddkaka
Hi :wave: Is there anyway to search through the diff of multiple/all commits in tig? The regular search either searches the commits messages, or the content of the currently open diff view.
Another question: do you know any TUI for gitlab?
Johannes Altmanninger
@krobelus
@kaddkaka I guess you can run tig log -p @{u}.. It looks like :edit is not yet supported in the log view, but that can be fixed
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
@kaddkaka
Yeah I'm really interested in MR workflow from terminal because the gitlab webgui is utterly syrup :3 @krobelus sounds great!
Johannes Altmanninger
@krobelus
@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.
kaddkaka
@kaddkaka
@krobelus thanks that looks interesting, will def take a look!
kaddkaka
@kaddkaka
@krobelus Could you explain the @{u}.. syntax?
Johannes Altmanninger
@krobelus
@kaddkaka @{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.
kaddkaka
@kaddkaka
I didn't know about the abbrevation, thanks!
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
Johannes Altmanninger
@krobelus

Unless there is some way to toggle between regular tig view and tig log view

I think that could be something to implement in the future.
Switching between main and log view should maybe keep the commit, I'm not sure

kaddkaka
@kaddkaka
keep the commit = sync the position between the two views?
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