Some time ago I've got a problem with Editor. I select multiple lines (with option-command-<up/down>) and trying to add multiple spaces to shift the whole block to the right. But editor adds tons of extra spaces. Please see screens attached.
Can anyone please help me to bring this to normal state?
Problem has been appeared recently (few days maybe).
VSCode version: 1.46.1
Found it. It was "editor.multiCursorMergeOverlapping". Setting it to true brings the behaviour to default.
Related
Every other snippet is working, but !+tab is not.
! snippet is not working
other snippet is working
I am using Visual Studio Code. I'm using 1.69.0. It was working before, but I wanted to add net html file, named that new.html, because I had index.html already. After that this script stopped working on every html file, but other scripts like "a", "div" etc. is working.
The v1.69.2 recovery release is out now. Emmet in html is working as it should for me now.
Looks like it will be in the Recovery Release, see https://github.com/issues?q=is%3Aissue+label%3Acandidate+repo%3Amicrosoft%2Fvscode+repo%3Amicrosoft%2Fvscode-internalbacklog+repo%3Amicrosoft%2Fvscode-remote-release+milestone%3A%22June+2022+Recovery+2%22+.
Don't know when the recovery release to Stable - presumably v1.69.2 - will be released. The .1 release is out and the fix is not in it.
It has been fixed though, see https://github.com/microsoft/vscode/issues/154375, and should be in the Insiders Build tomorrow (07/13/2022).
Testing the latest Insiders: ! is working. As is ul>li*3 type expansions (although that never stopped working for me - but it has been reported elsewhere). Should be in the v1.69.2 release out soon.
It is a known issue with the v1.69 release, see html emmet suggestion not automatically display or https://github.com/microsoft/vscode/issues/154517 for example. Lots of issues on github on ! and * not working.
So the emmet snippet will not appear automatically when you type !, but you can press Ctrl/Cmd+Space (which is the command Trigger Suggest) to make it appear and select normally.
Try Ctrl/Cmd+Space for anything emmet-related nnnnnot working in vscode v1.69.
You could also go back to v1.68 to solve the issue.
Try to write "doc" instead of "!". "doc" works for me.
On Windows 10, this worked for me:
Go to "Settings" and type "emmet.trigger" in the search
A checkbox for "Emmet: Trigger Expansion On Tab" will appear
Check the checkbox for allowing Emmet to trigger expansion on tab
After I did that, it worked just fine for !+TAB and any type of mulitpliers (i.e. li*4+TAB).
You need to check this option or put "emmet.triggerExpansionOnTab": true in settings.json to use the emmet abbreviation pressing TAB. I realized this ones what is not working:
!, lorem, >, and .
Examples of use: ul>li, li3, ul>li*3
None of them shows the preview of the emmet, and you can't use them pressing TAB without enabling the option that I sayed above, and even checking the option you won't be able to see the previews, you'll need to know them by yourself and press the TAB even though nothing showing that it's a emmet abbreviation.
You can use CTRL + SPACE too.
Edition Windows 11 Pro
Version 21H2
VSCODE Version 1.69.0
I had the same issue with the ! not working. I found another shortcut that does the same thing: type html:5, and press enter.
Looks like a bug, I have the same problem with 1.69.1, the VSC team is aware and fixing it. Should be fixed with the next release soon.
Meanwhile, you can use either HTML:5 or doc
meanwhile use "HTML:5"
enter image description here
or use "doc"
enter image description here
While #Mark's answer works, another work around would be to use the html:5 snippet which still works as expected in v1.69
Yes, I am facing this issue too since the latest update.
Somehow the solution I have got is :
You can check the box “Emmet: Use Inline Completions”
In settings by typing “emmet” in the setting’s search.
You can see the suggestion now and choose it by pressing the tab.
This is the solution I have got till now but hoping that we could have the previous version back.
Every other snippet is working, but !+tab is not.
! snippet is not working
other snippet is working
I am using Visual Studio Code. I'm using 1.69.0. It was working before, but I wanted to add net html file, named that new.html, because I had index.html already. After that this script stopped working on every html file, but other scripts like "a", "div" etc. is working.
The v1.69.2 recovery release is out now. Emmet in html is working as it should for me now.
Looks like it will be in the Recovery Release, see https://github.com/issues?q=is%3Aissue+label%3Acandidate+repo%3Amicrosoft%2Fvscode+repo%3Amicrosoft%2Fvscode-internalbacklog+repo%3Amicrosoft%2Fvscode-remote-release+milestone%3A%22June+2022+Recovery+2%22+.
Don't know when the recovery release to Stable - presumably v1.69.2 - will be released. The .1 release is out and the fix is not in it.
It has been fixed though, see https://github.com/microsoft/vscode/issues/154375, and should be in the Insiders Build tomorrow (07/13/2022).
Testing the latest Insiders: ! is working. As is ul>li*3 type expansions (although that never stopped working for me - but it has been reported elsewhere). Should be in the v1.69.2 release out soon.
It is a known issue with the v1.69 release, see html emmet suggestion not automatically display or https://github.com/microsoft/vscode/issues/154517 for example. Lots of issues on github on ! and * not working.
So the emmet snippet will not appear automatically when you type !, but you can press Ctrl/Cmd+Space (which is the command Trigger Suggest) to make it appear and select normally.
Try Ctrl/Cmd+Space for anything emmet-related nnnnnot working in vscode v1.69.
You could also go back to v1.68 to solve the issue.
Try to write "doc" instead of "!". "doc" works for me.
On Windows 10, this worked for me:
Go to "Settings" and type "emmet.trigger" in the search
A checkbox for "Emmet: Trigger Expansion On Tab" will appear
Check the checkbox for allowing Emmet to trigger expansion on tab
After I did that, it worked just fine for !+TAB and any type of mulitpliers (i.e. li*4+TAB).
You need to check this option or put "emmet.triggerExpansionOnTab": true in settings.json to use the emmet abbreviation pressing TAB. I realized this ones what is not working:
!, lorem, >, and .
Examples of use: ul>li, li3, ul>li*3
None of them shows the preview of the emmet, and you can't use them pressing TAB without enabling the option that I sayed above, and even checking the option you won't be able to see the previews, you'll need to know them by yourself and press the TAB even though nothing showing that it's a emmet abbreviation.
You can use CTRL + SPACE too.
Edition Windows 11 Pro
Version 21H2
VSCODE Version 1.69.0
I had the same issue with the ! not working. I found another shortcut that does the same thing: type html:5, and press enter.
Looks like a bug, I have the same problem with 1.69.1, the VSC team is aware and fixing it. Should be fixed with the next release soon.
Meanwhile, you can use either HTML:5 or doc
meanwhile use "HTML:5"
enter image description here
or use "doc"
enter image description here
While #Mark's answer works, another work around would be to use the html:5 snippet which still works as expected in v1.69
Yes, I am facing this issue too since the latest update.
Somehow the solution I have got is :
You can check the box “Emmet: Use Inline Completions”
In settings by typing “emmet” in the setting’s search.
You can see the suggestion now and choose it by pressing the tab.
This is the solution I have got till now but hoping that we could have the previous version back.
It is very annoying to see that background around code is lighter then the rest of the program. When the cursor moves the highlighting moves up and down to full window width. Can you please propose solution how to turn this highlighting off. Same problem is in output of task log, and in file explorer.
I have deleted all the settings and Application data and I have same problem. I have installed vscode on windows and I do not have this problem with same settings.
Unfortunately this is an issue in Chromium. You can work around this by starting VS Code with --disable-gpu from the command line.
Sean
It appears this can be fixed for some users by selecting a different color profile in macOS display settings. Note that you have to change this separately for all monitors that you use.
For me, "Apple RGB" will show these blocks, and switching to "LED Cinema Display" or "iMac" solves the issue.
See also: https://github.com/Microsoft/vscode/issues/12473#issuecomment-269024219
Currently eslint/tslint highlighting for issues/errors is super invisible (comparing, for example, to Atom). Its almost impossible to catch the issue - find the small green highlight zone (see screenshot)
VSCode:
Atom:
Question is not relevant since June 2018 (VSCode now has awesome highlights)
Simple. I use 2 extensions for that:
Error Lens (usernamehw.errorlens) for highlight the entire line and show on real time the error diagnostic
Error Gutters (igorsbitnev.error-gutters) for put error icons next of line number
Both look like this:
For those who would like a partial solution for this you can actually open up the console in vscode on the PROBLEMS tab to display all errors on across your application grouped by file.
I would prefer the inline visualised approach, but this does resolve this problem more or less.
To open the PROBLEMS tab, click CMD+Shift+M on Mac.
Not sure about windows.
I have been experiencing a strange issue in Flex Builder 3 where certain dialogs such as the Add New Project wizard and the SVN Commit dialog are completely empty save for the title area.
I'm running Flex Builder v3.0 (build 3.02.2.214193) on the Windows 7 RC. I have tried completely uninstalling and reinstalling Flex Builder to no avail. I don't think it's Windows 7 causing the issues because it was working a couple of months ago with no problems. Even more strange is that I have not installed any additional plugins or made any configuration changes to Flex Builder between the time before these problems began and now.
Has anyone else encountered this problem, and if so, know of any solutions?
Here are a couple of screenshots to illustrate the behaviour.
alt text http://www.colincochrane.com/image.axd?picture=2009%2f9%2fdialog2.PNG
alt text http://www.colincochrane.com/image.axd?picture=2009%2f9%2femptydialog.png
You are probably running Logitech SetPoint. Try killing all setpoint processes. (you don't even have to restart flex). It worked for me :-S
According to this Adobe forums post, there are multiple causes:
SetPoint (as indicated by Scheea)
Wacom Tablet drivers
In addition, comments suggest the following:
UltraMon
These seem to suggest that the cause is any program which monitors keystrokes or mouse movement.
Workaround: In the new wizard dialog above, note the question mark on the bottom left (the help button). When you click on the help button a help panel is added to the dialog on the right separated from the main dialog by a splitter. When you drag the splitter the rest of the dialog appears. You may need to scroll to a position where you can see all of its contents, but it should become usable. Resizing the dialog alone was not sufficient for me.
In addition, I couldn't fully use the mouse to select elements so I had to type into the filter field in order for the correct projects to show up.
I had the issue with Window7 x64 Ultimate with FB3 Pro and shutting down Set Point seems to have fixed the issue.
For me it was Set Point and Display Fusion (allows you to set up multiple background images as wallpaper on multiple monitors). Took a lot of hair pulling to figure this out.