Re: git-gui: automatically move focus to staged file before typing commit message?
- From
Birger Skogeng Pedersen <birger.sp@gmail.com>
- Date
- Oct 8, 2019, 19:46 UTC
- Message-ID
- <CAGr--=JM2uTyyymUxHw6vhE9H=bzAO_E_yzrmuOhuuk-td02CA@mail.gmail.com>
- In-Reply-To
- <20191008175938.iqibournnxam4r6d@yadavpratyush.com>
Hi Pratyush,
On Tue, Oct 8, 2019 at 7:59 PM Pratyush Yadav <me@yadavpratyush.com> wrote:
Show 7 quoted lines
> On 07/10/19 06:52PM, Birger Skogeng Pedersen wrote: > > So I kinda got this working, but only when focusing the commit message widget. > > Isn't this the point of your feature? You change the view when focusing > the commit message widget. I remember you were explicitly against doing > it as soon as all unstaged files were staged. Did you change your point > of view on that?
Yes, kindof. Sorry for not being more clear about the intent. I would prefer that the automatic selection of a staged file happens also when adding files while the Commit Message widget is in focused. For instance, if the user focuses the Commit Message widget and then hits CTRL/CMD+i a staged file should be selected (if it isn't already).
Show 13 quoted lines
> > I did not manage to get it working when invoking "do_add_all", (e.g.
> > when pressing CTRL/CMD+i). I added this:
> >
> > bind $ui_comm <$M1B-Key-i> {do_add_all;select_staged_file;break}
> > bind $ui_comm <$M1B-Key-I> {do_add_all;select_staged_file;break}
> >
> > But it seems that the "select_staged_file" procedure is invoked
> > _before_ "do_add_all" finishes. So that's not working. All changes
> > gets staged, but no staged change is selected.
>
> Hmm, that shouldn't happen. select_staged_file should be executed
> _after_ do_add_all, not before. I haven't looked into your patches yet
> though.I don't understand why it doesn't work. I'll play around some more with it.
Show 9 quoted lines
> > And I'm quite stuck. Do I send the unfinished patch, so maybe I can > > get some advice? Or is it better to just wait until I have the perfect > > patch ready? > > If you are stuck on something, and want to share the WIP feature to get > help/comments, you should mark your patches as "RFC" (Request For > Comments). This can be done by passing the option '-rfc' to > `git-format-patch`. This will make your subject prefix to "RFC PATCH" > instead of just "PATCH".
Sorry for not doing that, I'll take not and do that next time.
Thanks! Birger