Kakoune: The `g` goto menu should be case sensitive

Created on 22 Dec 2020  路  2Comments  路  Source: mawww/kakoune

Hi,

All mappings added to the goto menu (g) are case insensitive.

I don't think it makes sense, since users could want to declare an alternative mapping to the default ones using shift (more practical than alt).

The shift modifier also has a significant meaning in the context of mappings (it generally means "extend"), despite that meaning being superseded by the G menu.

HTH.

bug

Most helpful comment

I assume they're case-insensitive so that you can select to the beginning of the line with GH. The idea of "hold shift to extend the selection" is easy enough, but for two-key movements like the goto menu, it's not immediately clear whether you need to hold shift for just the first, or for both keys. Plus, if you try to type Gh quickly you might wind up typing GH accidentally anyway.

All things considered, it's friendlier just to make the goto mode case-insensitive, so that what users type (due to confusion or to accident) Just Works.

All 2 comments

I assume they're case-insensitive so that you can select to the beginning of the line with GH. The idea of "hold shift to extend the selection" is easy enough, but for two-key movements like the goto menu, it's not immediately clear whether you need to hold shift for just the first, or for both keys. Plus, if you try to type Gh quickly you might wind up typing GH accidentally anyway.

All things considered, it's friendlier just to make the goto mode case-insensitive, so that what users type (due to confusion or to accident) Just Works.

I deliberately type gL and gH all the time and I keep getting surprised when it doesn't highlight my movement. I think gL and gH are very difficult to accidentally type.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

akkartik picture akkartik  路  3Comments

lenormf picture lenormf  路  4Comments

basbebe picture basbebe  路  4Comments

lenormf picture lenormf  路  4Comments

alexherbo2 picture alexherbo2  路  3Comments