-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
[html] Error message interrupt and frustrate #15018
Comments
Can you show us a screenshot of that error text? |
Sure, here you go. The annoying part is the output window covering the part of the file I was editing, and it seems like every keystroke, or every second this error is regenerated. There is workaround for this - you can slide the output window down. Closing the output window is not effective, as the next error opens it back up over your code. Also, actual error text is: |
@WardDurossette Can you share the whole file, or construct a minimal example. Look out for html elements with 'src' or 'href' attributes. |
Attached minimal example file. Please change extension to ".html". |
Same issue. The problem is caused by a source path that starts with "/". However, when opened a directory then open the html file, the problem solved. |
Is there any quick solution to this. It's very frustrating to work on VS code now. My whole day job is to directly work on server files from FileZilla with references to all kinds of paths. Can we please somehow turn OFF this feature whatever it's trying to check? |
Is there at least a workaround until the update is released? @aeschli |
@doncullen The workaround is to open VSCode on a folder instead of a file. |
Steps to Reproduce:
Open a Windows Explorer window to a remote share (I.e. \server.dom2.dom1\share
Double click a file to open in VSCode. (Default.asp)
Start editing file. As you type the output window will pop-up with the error text, covering the edit window, interrupting your work, causing you to become frustrated.
Close output window to get rid of useless error message that you can do nothing about.
5 Goto step 3.
The text was updated successfully, but these errors were encountered: