-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contracting snippets at the end of a file causes tabout and bugs the editor #70
Comments
Maybe it happens when cursor ends up outside the file, but This appers twice in the console:
First one is
does not go away, crashing at tabstops moving, with history still disabled and all button presses showing up in the editor, but being mistaken with valid target for the snippet. (How could you not double-check just before "expanding" that trigger is still there?) Second one is after |
So here is how it happens:
combinedChanges = '[94,[2,"→"]]'
combinedChanges.inserted = '[[""],["→"]]'
combinedChanges.sections = '[94,-1,2,1]'
-length: 96
-newLength: 95 shrinks the document. |
Just by changing |
Hi! Thanks for the report. I don't notice any issues with the snippet {trigger: "^>", replacement: "⟳", options: "A"} However, after removing the "auto" option so that the snippet has to be triggered with Tab, I find that pressing Tab to trigger the snippet does cause you to tab out of the editor, which is very strange. What do you mean by "contracting snippets"? I'll look into the issue and your proposed solution when I have time! |
I never use automatic snippets ) |
Fixed in 1.6.2, thanks for providing the solution! |
Snippets like {"^>"→"⟳"}, aka contracting snippets cause Tab to act on the browser interface (and tab outside the editor) instead of eating it, which makes the editor pane go crazy (into some weird insert-mode, tuning off saving the document once bugged).
Currently investigating further...
The text was updated successfully, but these errors were encountered: