[Feature Request]: Support for whichwrap

[hholst80]

What feature would you like to see?

I would like vis to implement the Vim 'whichwrap' setting.

The expected behavior between different users depends on their experience and previous editors. Instead of debating which is better, Vis can support both!

[mcepl]

1. If you want us to provide with some new feature, please, sit down and specify it as precisely as you are able to. If you say, “do it like them”, it means your time is too precious to sit down and do the specification, and we should do it instead of you. We would have to sit down, install some editor we don’t care about, study it and then divine what you meant by saying “do it like them”. That is not like the FLOSS world works. You should be paying others for doing work for you by doing as much as you can.
2. Issue tracker is for issues, with specified problem, and suggested solution, not for a free flow discussion. Please, send an email message to the email list https://lists.sr.ht/~martanne/devel, where we can discuss what is exactly what you wish for.

Thank you.

[hholst80]

Don't be an ass, I ask politely.

I thought that anyone working on vis would be familiar with vim standard configuration terms like whichwrap. I am sorry if I misjudged the situation.

Let me rectify it by pasting the man page for the setting?

Feature Request: whichwrap Behavior in a Vi-like Editor

Summary:
Introduce a whichwrap-like option in the editor, allowing users to configure the behavior of cursor movement at line boundaries. This feature provides fine-grained control over whether certain cursor motions (left, right, end, home, delete, backspace) should wrap to the next/previous line when at the beginning or end of the current line.

Key Features:

Configurable Wrapping: Users can define which motions (h, l, ←, →, BS, Space, ~) should allow line wrapping.

Customization Flexibility: Each type of motion can be individually enabled or disabled for wrapping, giving users full control over how the cursor behaves at line boundaries.

Improved Navigation: Enhances user experience by allowing intuitive wrapping behavior based on personal preferences or workflow needs.

This option would make line-based navigation more customizable, fitting various user preferences.

Reference
https://vimhelp.org/options.txt.html#%27whichwrap%27

[mcepl]

On Fri Oct 25, 2024 at 1:59 AM CEST, Henrik Holst wrote: I thought that anyone working on vis would be familiar with vim standard configuration terms like whichwrap. I am sorry if I misjudged the situation.

I have not used in anger vim (or in my case neovim) for more than year (I use it now only for two functions I miss in vis: nvim -d aka #1043 and support of orgmode TODO lists; Lua plugins for both are welcome!). I have truly forgotten meaning of all those hundreds options (certainly including this one).

Let me rectify it by pasting the man page for the setting?

Better than nothing … OK, so I opened neovim and looked it up. Yes, not only I have forgotten a lot, but I have never touched this option. Yes, it is different in vis, which was unpleasant in the beginning, but now I have completely forgotten about it.

[machinedgod]

@mcepl Offtopic, but there's a pretty nifty table plugin for vis (its on plugins page)
already