Long files consisting of one line can not be soft-wrapped

[real-esekyl]

When opening a file consisting only a very long line (auto-generated code f.e.), soft-wrapping is very important. If the content is bigger than the screen, you cannot scroll to the further content though.

[dmaluka]

This is fixed in my PR #1981.

[real-esekyl]

Thank you so much, it works basically very well. In a very long js-file, I encountered strange behaviour though. I could navigate the cursor by arrow keys and pageup/down (slowlier as the file gets bigger), but could not edit the file at all. Even with sudo, it did not change anything. Maybe there is a limit of characters per line?

[dmaluka]

I didn't encounter such a problem. I've just tried with a 1MB single-line file. I can edit it, editing is very slow but just as slow as cursor movement.

I don't think there is any limit on the line length, but certainly micro is very slow when it comes to very large lines.

[real-esekyl]

Just if you are interested: this only happens in the soft-wrapping branch and only when I open a write-protected file without sudo. It does not allow any edit. In the "original" micro it allows me to edit and asks for sudo inside the application.

[dmaluka]

Ah, I got it. The newest micro automatically enables readonly option if a file is write-protected (see #1224), so you cannot edit the file. You can manually set readonly off to be able to edit it.
You were probably using the latest official release 2.0.8 which doesn't include this feature yet, so you could edit right away. So it has nothing to do with my softwrap changes, only with the fact that my softwrap branch is synchronized with a newer master.

[real-esekyl]

Another big thanks to you, so I will reinstall micro from your branch and set readonly off ;)

[real-esekyl]

Becoming a bit off-topic I guess, but I cannot set readonly off/false in my setings.json. Saving and re-opening the file makes the line disappear.

[dmaluka]

Yep... I believe it isn't documented but readonly option (and also filetype option) is local-only, i.e. cannot be set permanently. In other words, set readonly off is the same as setlocal readonly off. So you have to turn it off manually each time after opening a write-protected file.

This behavior is not exactly intuitive, perhaps it should be improved somehow. You can file an issue for it if you like. In the meantime you can just start micro itself under sudo.