Re: git-gui: unstaged changes windowpane resets after unstaging a line
- Date: Mon, 1 Apr 2019 08:40:19 +0200
- From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
- Subject: Re: git-gui: unstaged changes windowpane resets after unstaging a line
On Sun, Mar 31, 2019 at 9:48 PM Jan Ziak <0xe2.0x9a.0x9b@xxxxxxxxx> wrote:
> On Sun, 31 Mar 2019 at 21:15, Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx> wrote:
> > Hi Jan,
> > On Sun, Mar 31, 2019 at 8:45 PM Jan Ziak <0xe2.0x9a.0x9b@xxxxxxxxx> wrote:
> > >
> > > Hello
> > >
> > > After performing "Unstage Line From Commit" action, the "Unstaged
> > > Changes" windowpane is reset. The reset does not happen with "Unstage
> > > Hunk From Commit" action.
> > because its not necessary when staging a hunk. Though when staging a
> > line it is better to run the diff algorithm again.
> Yes. I was thinking comparing the old state of "Unstaged Changes" to
> the new state and preserving (or approximating) the selected filename
> and scroller position if possible.
> When unstaging a line (or a hunk) there is internally no possibility
> for the currently selected filename to disappear from the "Unstaged
> Changes" list.
> > Anyway, which problem do you observe in particular?
> The problem is that the selected filename and scroller position are
> reinitialized. It is uncomfortable when "Unstaged Changes" contains a
> lot of filenames.
I can't confirm this behavior. Neither when staging lines from the
"Unstaged Changes" file list, nor when unstaging lines from the
"Stages Changes (Will Commit)" file list.
Could you try to come up with a recipe from an empty repository?