On Mon, Aug 30, 2021 at 07:46:32PM +0200, Theo Buehler wrote:
> On Mon, Aug 30, 2021 at 07:32:02PM +0200, Stefan Sperling wrote:
> > On Mon, Aug 30, 2021 at 07:01:15PM +0200, Theo Buehler wrote:
> > > > > That does not resemble vi(1) at all.
> > > 
> > > agreed.
> > > 
> > > > For me, Ctrl+U moves to the top when vi is in normal mode.
> > > 
> > > This scrolls up half the screen unless you've previously given a
> > > count to Ctrl+U or Ctrl+D (which is the inverse operation).
> > 
> > There is no requirement to match vi's behaviour 100%.
> > 
> > My keyboard lacks a Home key so to test Jasper's diff I needed to
> > find another key that is not used yet. I came up with U (for "up").
> > 
> > Jasper then figured out that Ctrl+U is already used for upwards motion
> > in some programs, such as vi. So it became Ctrl+U.
> > 
> > Later on jrick pointed out that 'g' is used in less(1) for moving
> > to the first line of the file. So we decided to provide it as well
> > for people already used to this motion.
> 
> This makes perfect sense to me (I use these a lot in less and the
> absence of 'g' is a recurring annoyance in our vi(1)).
> 
> > Would you prefer to drop Ctrl+u and keep only 'g'? Fine with me.
> 
> To be perfectly honest, I do not feel all that strongly about it.
> 
> I'm used to navigating with Ctrl-D and Ctrl-U both in less and in vi. I
> prefer them over Ctrl-F and Ctrl-B because they provide me with context.
> 
> I'm likely to be occasionally confused and it is a bit unfortunate since
> there's no way to jump back to where I was. I doubt I'll be alone.
> 
> I will get over it.
> 
> > My only concern about 'g' and 'G' is that it is easy to type one when
> > you wanted the other if your timing on the shift key is slightly off.
> 
> I can't tell. This never happened to me in many years of using them.

I have no strong feelings towards Ctrl+u (or g/G even) so if we
adjust them to what others prefer that's totally fine with me.

-- 
jasper