Before asking here I asked the same question to the team of the extension HTMLHint - VS Code Extension for Visual Studio Code, but I didn't get any response.
My question is very simple. I have correctly set up the extension and the configuration file. Everything works fine. The only problem that occurs is the following: warnings and errors are shown in the section "Problems" even when I closed the file which I'm working on. Is there a way to show them only when the file is actually open?
Thanks everyone for the help.
Related
I am very new to web development and I am starting my first project using frontendmentor.io. I began my project Monday and everything was working fine. All of a sudden on Tuesday, I began to get a error message when trying to open live server.
The error message reads:
Error: ENOTDIR: not a directory, stat '/Users/username/html/index.html/'
I have searched plenty of forums and cannot really find anything that fits my situation. I am using only HTML and CSS for this project. I uninstalled VSCode and I lost all of my previous work, so I only have the code that frontendmentor provided to get started, but I can post that below if needed. I am sure I did something wrong, I just cannot figure out what exactly.
I had that problem too.
I opened the CSS file with live server instead of index.html file and it works.
I have been trying to publish some documentation and can't get it to work. From what I can tell it looks to me as if readthedocs is ignoring the autosummary_generate = True directive in conf.py
I am using autosummary and it works well on my local machine, with all the individual .rst files being generated when calling make html.
When building on readthedocs everything appears to work, with no errors being thrown, but when trying to browse the documentation the links do not work. Digging a bit deeper I see this type of warnings:
/home/docs/checkouts/readthedocs.org/user_builds/libgs-ops/checkouts/latest/docs/source/index.rst:23: WARNING: failed to import libgs_ops.propagator
Since that is a file that should be generated by autosummary I am assuming the problem is, as I mentioned, that readthedocs has not generated the files.
You can experience the problem for yourselves here;
https://libgs-ops.readthedocs.io/en/latest/
See how none of the links work.
I found this thread, in which someone references a similar problem in one of the responses, but as the problem asked appears to be different I permit myself to create this new thread. As I said, autosummary works fine on my local install, just not on readthedocs.
Hi I'm running VSCode on my mac and Windows 10 machine. They've both started displaying the same symptoms after the latest update/rollback.
Every couple of keypresses I get the output box appear, with the "HTML Language Server" selected in the dropdown. The error displayed is:
[Error - 13:47:09] Request textDocument/documentLink failed.
Message: Request textDocument/documentLink failed with message: Path must be a string. Received undefined
Code: -32603
This gets repeated indefinetly and is making VSCode unusable. I'm editing some JSP / JSTL files so I'm wondering if it's some non-valid HTML setting it off, but this has never been an issue before.
All research I've found of this error seems to suggest a faulty extension, but I've currently not got any installed.
Help appreciated!
This is a known issue and, as per this Github issue, the workaround is to open Visual Studio Code on a folder instead of a file.
I too had this popping up this morning, google pointed me to vscode's extensions, so I went through the vscode extensions, updated them all and Debugger for Chrome (2.2.0) was the only one fitting the Error message.
Since I do not have the time right now to file an issue (and answer follow-ups) on https://github.com/Microsoft/vscode-chrome-debug/issues I have just disabled the extension for now.
One thing to note is, while vscode says it is version 2.2.2 in the extension panel, it is 2.2.0 on its marketplace page and github. Might be of some interest to dive in and find out where the extension panel picks up its - false - version number - and find out whether this has some impact on creating the error.
I'm trying to get to grips with the relatively new help system fronted by Microsoft Help Viewer 1.0.
I've found the SDK (at http://www.microsoft.com/en-us/download/details.aspx?id=14923) and have started working through it. I've used Help Library Manager to add the modified help file in step 9 of the "Walkthrough: Branding Package and Content" tutorial, but step 10 tells me to view help by typing a command into a command prompt that starts "ms-xhelp:///". The command prompt responds with a generic unrecognised command response. Pasting the whole thing into Chrome just does a Google search, so obviously that's not recognising it, and pasting it into Internet Explorer attempts to start doing something but then pops a message up "There was a problem sending the command to the program".
Remarkably, this appears to be the first post on here containing "ms-xhelp", and no tags seem directly relevant.
I do have VS2010 installed and it runs help correctly. If I modify the tail end of the URL the web browser opens in, I can get at the newly installed help file, but piggybacking on something that knows what it's doing is unsatisfactory and doesn't show me where things are going wrong. Does anyone know why the "ms-xhelp" approach isn't working?
We started to get
Refused to execute a JavaScript script. Source code of script found within request.
with version 17 of Chrome. Version 16 was working fine. What it seems to complain about is that we do a POST and the reply is the same what we already have if I understand it correctly. Or is there a way to verify exactly what it complains about?
Refused to execute a JavaScript script. Source code of script found within request
Is there a way to get around this or have anyone had simular problems with the new version 17 of Chrome? We dont do any cross posting on our site, so it kind of looks like a bug from Chrome, but anyhow it needs to be solved.
https://stackoverflow.com/a/1547887/99220 seems applicable. The feature is attempting to detect an XSS attack client-side, and refusing to execute code that looks like it's simply reflecting whatever was stuffed into a POST.
It's certainly possible that the XSS filters are buggy, and detecting your case as a false-positive. It's also possible that you have an actual XSS hole on your site that Chrome is warning you about. Can you post a link so others can take a look? If it is a bug, I'll help you file a ticket at http://new.crbug.com/ If it's not a bug, then we can evaluate how you can fix your site.