tig ./path/file from inside tig? #126

Open
quite opened this Issue Mar 13, 2013 · 4 comments

Projects

None yet

2 participants

@quite
quite commented Mar 13, 2013

I can enter tig ./path/file to limit tig to that file, and thus easily browse only that file's commit history, diff by diff. How can I make this limit from within tig? Preferably from the tree view.

Essentially, what I would like to do is to browse a file's diffs, step by step back through history Doing likewise with the actual blob would also be nice.

@jonas
Owner
jonas commented Mar 13, 2013

Hello @quite, this is not currently possible but it's a good idea. I suggest this feature is added so that you can both filter by file via the tree view or by using the prompt, for example ':main path/to/file'.

I am not sure I understand what you mean by 'doing likewise with the actual blob'. Do you want to be able to skip to previous versions of a blob for a specific file?

@quite
quite commented Mar 13, 2013

Yes, you got it--with blob I meant flipping through full versions of the file.Flipping through it's diffs would be a priority though.

If would be a bonus if it, when moving to the previous diff, tries to maintain the view around the currently displayed lines--which might not be possible of course, since previous change could be anywhere in the file. But that way one could see how a part of the code has evolved. Perhaps this might be more useful when viewing the blob.

@jonas
Owner
jonas commented Mar 13, 2013

You can get that behavior using blame. There you can jump to the previous
commit (parent) which modified a set of lines.

On Wed, Mar 13, 2013 at 8:13 AM, Daniel notifications@github.com wrote:

Yes, you got it--with blob I meant flipping through full versions of the
file.Flipping through it's diffs would be a priority though.

If would be a bonus if it, when moving to the previous diff, tries to
maintain the view around the currently displayed lines--which might not be
possible of course, since previous change could be anywhere in the file.
But that way one could see how a part of the code has evolved. Perhaps this
might be more useful when viewing the blob.


Reply to this email directly or view it on GitHubhttps://github.com/jonas/tig/issues/126#issuecomment-14837746
.

Jonas Fonseca

@quite
quite commented Mar 13, 2013

Great. So what is left to accomplish all this, is one or two ways to show
diff for only a specific path/file, and goto parent (and child) for the
diff view.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment