Currently, when VS Code is restarted (e.g. for extension update, or version update), open documents would lose their word wrap settings after restart. It would be very helpful, if word wrap state for an open documents is preserved.
I am persisting and restoring an editor view state, so maybe it should be part of it.
alt+z was intended to be an "in-memory" word wrap toggle.
There are better ways to configure permanent wrapping, via the "editor.wordWrap" setting in user settings.
This is not part of the editor's view state because toggling a file via alt+z toggles its wrapping in all the editors where the file is open.
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
alt+z was intended to be an "in-memory" word wrap toggle.
There are better ways to configure permanent wrapping, via the
"editor.wordWrap"setting in user settings.This is not part of the editor's view state because toggling a file via alt+z toggles its wrapping in all the editors where the file is open.
With all due respect, I don't see how word wrap state is different from unsaved changes to the document. "Dirty" status is attached to the document, it is propagated to all views over the document, and it is preserved on restart. For all practical purposes, unsaved changes can be considered in-memory.
So, it's not clear why unsaved changes to the document can be preserved across restarts, and word wrap cannot.
Also, editor.wordWrap seems to apply to all the documents in a workspace or globally, which is not the ask here.
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
Most helpful comment
With all due respect, I don't see how word wrap state is different from unsaved changes to the document. "Dirty" status is attached to the document, it is propagated to all views over the document, and it is preserved on restart. For all practical purposes, unsaved changes can be considered in-memory.
So, it's not clear why unsaved changes to the document can be preserved across restarts, and word wrap cannot.
Also, editor.wordWrap seems to apply to all the documents in a workspace or globally, which is not the ask here.