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
Description:
I would like to propose a feature that allows less to toggle between navigating by screen lines and text lines. Currently, navigation in less by default is done by screen lines (e.g., using the arrow keys or j), which can be confusing when dealing with wrapped lines. Instead of introducing new keybindings, I suggest using a toggle or flag to switch between these two modes.
Proposed Solution:
Implement a toggle (possibly a command-line flag or an in-session toggle key) that allows users to switch between screen line navigation and text line navigation.
When the toggle is set to screen line mode, less would behave as it currently does, navigating by screen lines.
When switched to text line mode, navigation commands like j would move by actual text lines, ignoring line wrapping on the screen.
Use Case:
This feature would be particularly useful when viewing files with long lines that wrap on the screen. It would provide users the flexibility to choose the most appropriate navigation method for their needs, especially those familiar with Vim’s navigation behavior.
The text was updated successfully, but these errors were encountered:
Description:
I would like to propose a feature that allows
less
to toggle between navigating by screen lines and text lines. Currently, navigation inless
by default is done by screen lines (e.g., using the arrow keys orj
), which can be confusing when dealing with wrapped lines. Instead of introducing new keybindings, I suggest using a toggle or flag to switch between these two modes.Proposed Solution:
less
would behave as it currently does, navigating by screen lines.j
would move by actual text lines, ignoring line wrapping on the screen.Use Case:
This feature would be particularly useful when viewing files with long lines that wrap on the screen. It would provide users the flexibility to choose the most appropriate navigation method for their needs, especially those familiar with Vim’s navigation behavior.
The text was updated successfully, but these errors were encountered: