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
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Seems to be a regression introduced by #169. It uses the getActiveTextEditor API, meaning to grab the file we are leaving, but instead grabs the editor we arrive at. It then sees that the buffer is not the same as the actual editor, and doesn't look for any cursors.
Probably related is that saving is async, so the event is likely firing after we switch tabs (or something to that effect).
The text was updated successfully, but these errors were encountered:
So I looked closer at the test cases in #169, and it's number 3 that is the issue. From it's description, I believe it's meant to be for when saving all files with the command prompt. This makes sense, but unfortunately conflicts with autosave as you change tabs.
I guess the question might be is this expected? I obviously don't like it killing whitespace while I'm writing a function & switch to another tab to look at something. But I don't know if these events can be distinguished, or even if other people actually want this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Prerequisites
Description
The
Ignore Whitespace on Current Line
setting is not respected.Steps to Reproduce
JavaScript
, paste in the following, and place your cursor where the pipe is (delete the pipe)Expected behavior: [What you expect to happen]
No change
Actual behavior: [What actually happens]
Whitespace eaten
Reproduces how often: [What percentage of the time does it reproduce?]
70%
I can't reliably reproduce every time, but it will happen when I try enough times.
Versions
whitespace 0.37.6
Additional Information
Seems to be a regression introduced by #169. It uses the
getActiveTextEditor
API, meaning to grab the file we are leaving, but instead grabs the editor we arrive at. It then sees that the buffer is not the same as the actual editor, and doesn't look for any cursors.Probably related is that saving is async, so the event is likely firing after we switch tabs (or something to that effect).
The text was updated successfully, but these errors were encountered: