thousandtyone / autoend Goto Github PK

Switching files causes semicolon button to no longer type. It still sends cursor to the end of the line, but I can no longer type a semicolon until I reload VS Code completely.

In vim normal mode, when you press the key';', a semi-colon will appear. Actually, it shouldn't appear a semicolon in vim normal mode.

I ran into this problem as I was conducting interviews.

1. Create a file names interviews.java
2. Write some code. Everything works fine.
3. Rename the file to interviews.cpp (because this candidate wants to write code in C++).
4. Semicolons don't show up anymore. It is not about autoend not working but I just can't type a semicolon at all.

Restarting VSCode makes it work again.

OS X El Captain Version 10.11.6
VSCode Version 1.24.0 (1.24.0)

Is there way to disable that when you ; it will not go to the next line? it will just jump to the end of the line.

thanks

I'm on Mac. Cmd-F, and then type "foo;" in the search box. It will search for "foo", but the semicolon will be inserted in the current document at the cursor.

Expected behaviour would be to search for "foo;" and not modify the document.

Can't type russian "ж" symbol that has ";" key on english layout.

Personally I would like for the command to never insert newlines, but everyone is different, I guess.. :)

Make it configurable perhaps?