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
Visual Studio Code v.1.85 + EditorConfig extension.
Settings - "files.autoSave": "afterDelay",
Current behavior (with autosave setting):
After a second starts autosaving and a new last empty line is added at the beginning of typing, the cursor is moved, in the next string because of this, text break glitches, for example:
.red
{/* here - moved cursor from the VS extension EditorConfig */}
/* here - empty new line created by the VS extension EditorConfig */
In EditorConfig plugin (WebStorm) another, more correct behavior:
After a second starts autosaving and a new last empty line is added, but , the cursor is NOT moved. Therefore, there are no glitches with line breaks.
.red {/* here - NOT moved cursor from the VS extension EditorConfig */}
/* here - empty new line created by the WS plugin EditorConfig */
Could you do the same behavior as WebStorm plugin (the cursor is NOT moved when auto-creating a new last empty line) in the plugin EditorConfig for VSCode?
Thank you in advance.
The text was updated successfully, but these errors were encountered:
Visual Studio Code v.1.85 + EditorConfig extension.
Settings - "files.autoSave": "afterDelay",
Current behavior (with autosave setting):
After a second starts autosaving and a new last empty line is added at the beginning of typing, the cursor is moved, in the next string because of this, text break glitches, for example:
In EditorConfig plugin (WebStorm) another, more correct behavior:
After a second starts autosaving and a new last empty line is added, but , the cursor is NOT moved. Therefore, there are no glitches with line breaks.
Could you do the same behavior as WebStorm plugin (the cursor is NOT moved when auto-creating a new last empty line) in the plugin EditorConfig for VSCode?
Thank you in advance.
The text was updated successfully, but these errors were encountered: