Jonas Fonseca

I think the best would be to present "a stash" similar to the status view with three sections, so instead of a diff subview it would be a status subview,...

Is this the append mode you mentioned in the comment on Google+?https://plus.google.com/114916345471115163934/posts/1BiTKKjiaVJ) > [U]pon entering append mode, the diff is taken from the parent commit of the HEAD > (effectively...

Regarding the status view, this should be a matter of using `HEAD^` instead of `HEAD` when showing staged and unstaged changes. Regarding using `commit -a` instead of `commit. Do you...

Can you give an example of how this would be configured? Because as I said keybindings are not handled by the status view itself.

The easiest way to remove all default bindings is probably to compile Tig with `make NO_BUILTIN_TIGRC=y` and remove, not load (`export TIGRC_SYSTEM=/dev/null`) or override the system `tigrc`.

This makes sense and sounds like it will bring `view-blob` more in line with how the edit action works. However it is a bit hard to understand the behavior from...

You are not the first to ask for this feature. Can you provide some more detail as to what views you are mainly interested in responding to such an option?...

While looking at issue #26, I have been looking into adding support for --word-diff=porcelain as a way to provide side-by-side diff support. AFAIK, the parsing of the word diff can...

That's true. There's no way to undo or revert a single line.

This is the expected behaviour, which I agree is not optimal. To fix this we'd have to refactor the display management code to keep a proper history of the display...