Adds a status bar item in VS Code (and VSCodium) to show current wrap status and allow changing without affecting settings
When editing files, I tend to swap between the word wrapping as needed as I read a file. It's always bugged me that I need to open the settings editor and find the specific setting to change in this case instead of having some easy way to toggle the wrapping, so I've added a status bar item to show and allow changing the word-wrap.
I've allowed the setting to be set through double clicks on the status bar item, but the column to wrap on, I'm assuming you'll change less often so leaving that to be changed through the settings editor should be OK.
This will display the current wrap setting on the status bar. For those wrap settings that are dependant on the setting defining the wrap column (i.e. 'bounded', which is shortest of window boundary and the wrap column, or the 'wordWrapColumn'), the wrap setting on the status bar will also show the current wrap column.
As the wrap setting itself, or the wrap column is changed in the settings, this will be automatically reflected to show the explicitly set value in your status bar.
Also allows you to double click the status bar item, which will cycle through the wrap settings (in the order of 'on', 'off', 'wordWrapColumn', and 'bounded'). I'd prefer this to be in-memory only, and not stored, but unfortunately that doesn't seem possible in VSCode, so the changed setting is in the Workspace context. It will be 'remembered' through restarts only within the current workspace.
This extension was tested on
This extension is based upon the sample statusbar from https://github.com/microsoft/vscode-extension-samples
The double click detection is based on tips & code from
0.0.0 Initial code - no funcitonality
0.1.0 Initially working status bar extension
0.1.1 Same as 0.1.0, however removed the browser extension files (not working and I don't use
v0.1.2 Added eslint action to the repository, updated README. No functional changes
v0.1.3 Updated URL for release 0.1.2 in README, no other changes