Use letters in the gutter instead of relative line numbers for jumping

[godalming123]

From what I understand, the most efficient way to jump vertically in helix is to use relative line numbers in the gutter with the j and k motions. However, there are a couple problems with this:

• This approach breaks when soft wrap is on, because the j and k motions work on visual lines, but the relative line numbers in the gutter work with semantic lines in a file (although I think that it might be possible to make j and k work with semantic lines in the helix config.)
• In terms of number of keystrokes pressed, and how far the user has to move their fingers to press the keys, this approach is also not optimal

My approach to fix both of these issues is as follows:

• Instead of relative line numbers, letters could be shown in the gutter

• When a user pressed these letters, it would jump the cursor to that line while keeping the same horizontal position

• The algorithm to determine these letters would go as follows:

  1. If the line being navigated to is above the cursor then the letters can start with ;, or if the line being navigated to is below the cursor, then the letters can start with z (view mode can be rebound to V)
  2. After the z or ;, then helix would count in base 9 as the lines move further away from the cursor, using the keys <space>, a, s, d, f, h, j, k, l for each base 9 digit.

  All of the letters in the algorithm would be configurable for people using alternate keyboard layouts, with helix automatically counting in a different base if a different number keys are listed (EG: if someone wants to use all of the letter keys to count, then base 26.) The same keys and algorithm that counts in a specific base could also be used for already existing goto word feature, allowing users to for example have goto word only suggest keys that are on the home row.