You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many users are used to be able to use a count for keybindings. While this may be only nice-to-have (but still very handy) in most cases, it becomes very apparent with the g keybinding.
It basically has the same functionality in ov as in less, but in ov it is quite cumbersome.
To jump to line 10 in less, one can type:
10g
In ov one has to type:
g10<enter>
Not much, as it is only 1 keystroke more, but since the order of the count and the commands keybinding is exchanged it is hard to use for people accustomed to less.
It gets even worse when trying to jump to the beginning of the file.
In less one can type:
g
by just omitting the count.
I ov it is still necessary to type:
1g<enter>
Therefore I think it would be a nice addition to support a count for commands as this can come in handy for most commands and makes ov much easier to use for previous less-users.
The text was updated successfully, but these errors were encountered:
This Issue is the next level of #28.
Many users are used to be able to use a count for keybindings. While this may be only nice-to-have (but still very handy) in most cases, it becomes very apparent with the
g
keybinding.It basically has the same functionality in ov as in less, but in ov it is quite cumbersome.
To jump to line 10 in less, one can type:
In ov one has to type:
Not much, as it is only 1 keystroke more, but since the order of the count and the commands keybinding is exchanged it is hard to use for people accustomed to less.
It gets even worse when trying to jump to the beginning of the file.
In less one can type:
by just omitting the count.
I ov it is still necessary to type:
Therefore I think it would be a nice addition to support a count for commands as this can come in handy for most commands and makes ov much easier to use for previous less-users.
The text was updated successfully, but these errors were encountered: