We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
VSCode Version: 1.18.1 OS Version: Win10
Steps to Reproduce:
Expected: It does not close the pair by automatically writing "end". Actual: It does close the comment by writing "end".
Reproduces without extensions: Yes
I tried the following auto closing pairs:
"autoClosingPairs": [ // Those are not closing in comments { "open": "'", "close": "'", "notIn": ["string", "comment"] }, { "open": "b", "close": "d", "notIn": ["string", "comment"] }, { "open": "u", "close": "nn", "notIn": ["string", "comment"] }, // Those are closing in comments even with "notIn" { "open": "nn", "close": "u", "notIn": ["string", "comment"] }, { "open": "op", "close": "qo", "notIn": ["string", "comment"] }, { "open": "begin", "close": "end", "notIn": ["string", "comment"] } ],
I think the problem here is that VS code does not handle properly pairs where the opening part has multiple characters.
The text was updated successfully, but these errors were encountered:
f6ffced
rebornix
No branches or pull requests
VSCode Version: 1.18.1
OS Version: Win10
Steps to Reproduce:
Expected: It does not close the pair by automatically writing "end".
Actual: It does close the comment by writing "end".
Reproduces without extensions: Yes
I tried the following auto closing pairs:
I think the problem here is that VS code does not handle properly pairs where the opening part has multiple characters.
The text was updated successfully, but these errors were encountered: