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 22:21
    verdie-g opened #893
  • Jan 28 10:19
    VonUniGE commented #340
  • Jan 28 02:20
    rcywongaa closed #869
  • Jan 26 20:30
    smkniazi edited #892
  • Jan 26 20:29
    smkniazi edited #892
  • Jan 26 20:28
    smkniazi opened #892
  • Jan 24 10:38
    timotheecour edited #890
  • Jan 24 09:20
    timotheecour opened #891
  • Jan 24 00:29
    timotheecour opened #890
  • Jan 23 22:09
    KeeReal commented #869
  • Jan 23 20:58
    avivey opened #889
  • Jan 21 23:26
    timotheecour commented #559
  • Jan 21 21:16
    koutcher commented #559
  • Jan 21 20:47
    koutcher commented #559
  • Jan 21 18:39
    smancill commented #559
  • Jan 21 07:11
    timotheecour commented #559
  • Jan 20 17:01
    smancill commented #559
  • Jan 20 10:25
    koutcher commented #559
  • Jan 20 02:54
    timotheecour commented #559
  • Jan 20 01:56
    timotheecour opened #888
Ghost
@ghost~57852856c2f0db084a22a690
Let me show an example....
image.png
I think it's unclear what is happening to the branches here.
Ghost
@ghost~57852856c2f0db084a22a690
image.png
This is how git displays the first loop.
Jonas Fonseca
@jonas
The revision graph can definitely be improved. But given that the code is already quite complex, I am not sure adding a lot of configurability is a good idea.
Anders Stedtlund
@falolaf
If I limit a search with a path name I get a list with commits that affects that path and that path is the only one shown. Is there a possibility to show the full commit somehow? I.e. what other files were changed in the same commit.
Dieter Plaetinck
@Dieterbe
hello everybody. i love tig. i've been using it for a few years now I think. but one thing I'm not sure how to do, is get an overview of all commits that introduce a change matching a pattern. e.g. something like git log -G or git log -S
oh d'oh it looks like i can just run tig -S or tig -G
Jonas Fonseca
@jonas
:+1: git-log arguments can be passed to tig to filter etc.
Dieter Plaetinck
@Dieterbe
yes, sweet :)
mwilbur
@mwilbur
hi - i've only just started using tig. i made a small change that i wonder if anyone would find useful. i wanted to be able to navigate to a blob and write the blob to a file name obtained through a prompt. i bound a key to @git cat-file -p %(blob) > %(prompt file name:) but the redirection didn't work. i peeked under the hood and ended up adding something in open_external_viewerto look for ">" in argv and, if it there, assume the next element is a filename and then run io_run_append.
also - this is my first gitter session so pardon me if my etiquette is off :)
mwilbur
@mwilbur
@jonas - I'd like to see if I could contribute to the project somehow - cleanup, bug fixing, whatever. Please let me know if I can help in some way.
Igor Almeida
@igoralmeida
@mwilbur i am not a contributor but i'm fairly sure unsolicited PRs are most welcome. i suggest you go through the issue list and see if something catches your eye (and probably let people know that you're working on them to avoid duplicated efforts)
mwilbur
@mwilbur
@igoralmeida :thumbsup:
Jonas Fonseca
@jonas
Yes, PRs are welcome. I've gotten a bit behind on the merging side though. Mostly to stabilize and release a new version once jonas/tig#663 is fixed
Matthew Cengia
@mattcen
Hi folks, I'm tearing my hair out trying to understand tig config format; I've spent over an hour on this but it seems like it should be so simple.
I would like to set main-view = id date:default author:width:3 commit-title:yes,graph,refs, with the local date, but set main-view-date-local = true doesn't make that happen unless I don't set main-view at all. How can I get what I want?
Matthew Cengia
@mattcen
Oh, for crying out loud. The ordering of those lines is important. main-view before main-vew-date-local works, but that's not what I was doing. Well that answers my question (unless there's a better way to do this)
Jonas Fonseca
@jonas
They could be combined into one line
set main-view = id date:default,local author:width:3 commit-title:yes,graph,refs
Matthew Cengia
@mattcen
Oh that's great. Thanks!
m8mble
@m8mble
image.png
Is this a known issue?
Jonas Fonseca
@jonas
Looks like a redraw issue
jonas/tig#742
m8mble
@m8mble
Interesting: h+qfixes everything on the tig repo.
On another, larger, private repo though, it just makes the screenshot problem permanent. Interestingly (without h+q), lines get "fixed" (output without weird doubling) when I scroll down (holding j). Isn't the real problem, that the redraw is different from the initial draw?
Jonas Fonseca
@jonas
BTW, is this when using master?
Jonas Fonseca
@jonas
@m8mble Would also be interested in knowing whether you run inside tmux
m8mble
@m8mble
yes on master, but without tmux/screen etc. Just a regular KDE konsole.
Vivien Didelot
@vivien
I do have this problem too! redrawing doesn't fix it!
Vivien Didelot
@vivien
Screenshot from 2017-09-22 14-19-28.png
I have this when simply running tig
Screenshot from 2017-09-22 14-19-51.png
then this when doing Ctrl+L
Jonas Fonseca
@jonas
Hi Vivien!
I'll take a look.
tke
@tke
is it possible to use tig without pagination? I'd love to have a replacement for git log --oneline --graph that renders the graph the same as tig does
Jonas Fonseca
@jonas
I played with supporting something like that at one point, but never managed to complete it.
Martin Darmüntzel
@hutchison
Hi, I have a small problem. The "unstaged changes" are not shown. I tried different versions of tig and in 2.0.3 they're shown and they're missing after 2.1. I have no .tigrc, so I'm working with default settings. Am I doing something wrong?
Igor Almeida
@igoralmeida
@hutchison even if you press s while in the main view ?
Martin Darmüntzel
@hutchison
Then I'm getting a different view and it's not the same as git diff.
What I mean is the "unstaged changes" at the top of the main view.
It's unfortunate because I liked that :smile:
Jonas Fonseca
@jonas
@hutchison Are you seeing this with the latest Tig master? What Git version are you using?
Jonas Fonseca
@jonas
There was a few changes to that part of the code between 2.0.3 and 2.1, but nothing springs out.
Martin Darmüntzel
@hutchison
Ok, I think it's not tig's fault – it has something to do with the name of the current branch.
It seems to me that if the name of the branch contains an umlaut (like ä, ü, ö) then the unstaged changes are not shown.
Martin Darmüntzel
@hutchison
Bildschirmfoto 2017-10-01 um 09.16.49.png
Bildschirmfoto 2017-10-01 um 09.16.58.png
Bildschirmfoto 2017-10-01 um 09.17.13.png
Bildschirmfoto 2017-10-01 um 09.17.36.png