Not sure if this the right place to post this question. If not, my apologies.
I have two windows 10 machines. In both I have installed the last version of visual studio code and the last version of LaTeX-Workshop.
In one machine the Latex code shows up with the correct colors, whereas in the other machine it does not. See screenshots below of the first (working) example and of the second (non-working) example of the same code.
I have tried reinstalling LaTeX-Workshop but it didn't result.
Working example:
Non-working example:
There is an incompatibility of the package with some VScode themes.
More info here: https://github.com/James-Yu/LaTeX-Workshop/wiki/FAQ#syntax-highlighting-does-not-work-for-most-elements
Correct. It works with the Dark+ (default dark) theme but not with the Dark(Visual Studio).
Related
Prettier not working on VSCode
I have been using prettier for java on vs code from very long everything was working smoothly till yesterday and suddenly prettier stopped working for java.
I have tried every available resource on Youtube and Stack Overflow still didn't solve my issue, please help.
I tried from changing default formatter and format on save to settings.json still now working showing error - FormattingExtension 'Prettier - Code formatter' is configured as formatter but it cannot format 'Java'-files
Normally this happens when you have another extension overlapping the prettier settings. Disabling other extensions normally solves the problem. Reinstalling visual studio can be your best option, but you have to remove all remaining settings, or it will just be the same.
You can always install directly in terminal using: https://prettier.io/docs/en/install.html
Confirm on extensions that prettier is enabled. Update Visual Studio and Windows.
I am facing this exact problem with that exact words in vs code. I tried reinstalling vs code but that doesn't work and i also tried reinstalling powershell but that also does not work.
This does not happen when i use windows powershell,cmd,bash as terminal so it's a problem with powershell (version 7.2.5) i am using windows 7.
I had in the settings Terminal > Integrated: Windows Enable Conpty (setting ID terminal.integrated.windowsEnableConpty) disabled. After re-enabling it again (which is the default) the problem went away for me.
(I posted the same answer on the other question, but as this duplicate is findable on Google and not tagged here, I'm posting the same answer)
Prettier is behaving differently for me compared to my team mates.
We all have same version 9.5.0 of prettier installed on our VS Code.
We all have same configuration of prettier.
Still it is formatting my typescript file differently for one particular line than others and because of this the deployment is failing when I push anything from my machine and works for everybody else.
Does anybody face this?
Which part should I check to see the difference?
Update 1
One thing we found that is different is the VS Code version.
I have version 1.67.2 installed my colleague has 1.63.2 installed.
Could this be the reason?
Update 2
This is the exact line where I am getting prettier error on my machine for wrong formatting while this same formatting is considered correct by prettier for other machines
And this is how prettier formats the line on my machine (then devops complaint that it is a wrong formatting)
I think there is a bug with the prettier extension. Although I had my default formatter set to the prettier extension in the settings UI, I had to re do it manually.
Open any file, right click in the editor screen, click Format document with and choose Prettier - Code formatter.
The local prettier config and the one vscode uses should work now
I faced the same isssue.
in my case I run
npx prettier --version
on both computer and each one return different prettier version.
so although the prettier extension in vscode was 9.5.0 for both pcs. the npm module installed for the project in node_modules was different.
I installed the same prettier module for both computer and the restart vscode and problem solved
You might have installed multiple formatters and you aren't using the correct one. Try to specify it manually in command palette. Check out this answer (Solution A)
I have an issue with VS Code which I recently installed in my MacOS BigSur.
I tried out the Jupyter Notebook extension and in their documentation it says that they have full intellisense support for this extension as well.
Intellisense in Jupyter Notebook in VSCode works well for completing variables, functions,methods,etc....
The only issue I have is that I am not able to get the arguments/parameter information, though it is working fine with the python extension of VSCode
I tried out things like Shift+TAB...which works in JupyterNotebooks(not the VS Code version).
Is this a bug that I am facing...or is it just like that. Can you also please suggest as to how to make this work.
Edit May 12, 2021: With the Pylance language server (now the default), I now get parameters and type hints.
According to this issue on GitHub, the arg/param info is not supported on stable VS Code. It looks like you need to use the "Native Notebook" in VS Code Insiders (the beta) and use the "Pylance" language server Extension.
I haven't tried this solution myself (not sure I want to install Insiders), but just changing the language server to "Pylance" at least gives you signatures.
having assured myself that julia is enabled and that the linter is too (in vs code settings: Julia › Lint: Run), i get syntax highlighting on my xxx.jl script but no linting at all.
im on the latest vs code + latest julia 1.07 extension + latest macosx.
i did a clean installation of vs code, wiping all old related folders prior to installation (https://stackoverflow.com/a/53839847/11608725)
so julia is the only extension/package installed, no conflicts should be present.
what am i missing?
thanks!
edit/update:
i also found that i can NOT run an open script (via the leftmost button)
a pop-up says
and clicking on open launch.json gives
from which point on im pretty much stuck. googling around, a couple of very similar issues appeared (eg. https://stackoverflow.com/a/61284896/11608725, https://github.com/microsoft/vscode/issues/94725#issuecomment-612062020), but which should presumably have been fixed with vs code 1.44 and i am on 1.49.
perhaps the no-linting is related to this?
Have you tried Julia Formatter 0.3.0 for vs code? This has always worked for me.
similar message "Please first open a folder in order to .." pretty annoyingly appeared, my end, on a different platform [Win] [Visual Studio Code version: 1.56.2], too
meaning : it's likely the workflow/settings logic specific to VS Code, not an os/platform issue as such
all problems solved, my end, simply by
after launching VS Code
via "File" > "Open Folder..." : just do first -- before doing anything else in VS Code and/or with code-files -- open the current/working project folder [ie. the very folder with a ".code-workspace"-file in it for the given project (source file dir) ]