I installed the extension "laravel-blade" for blade files syntax highlighting: https://marketplace.visualstudio.com/items?itemName=cjhowe7.laravel-blade
Then I uninstalled it, but it also removed the default highlighting that vscode had for blade files and now code inside blade.php files look white (Regular php files are still OK)
How can I restore the default highlighting for blade.php files?
It might also have messed with other settings for blade.php files so might as well restore everything to default not just highlighting
Related
I'm switching from vscode to neovim (currently using lunarvim). One problem bothered me most is that if my included file don't use relative path, but handle these dependencies in Makefile instead, then the lsp failed to navigate, and make linter report mistakes because some definitions and declarations are in other files and can't be located.
I face the same situation in vscode too, but by writting c_cpp_properties.json file, the intellisense will work normally.
If there is any way to write down some hints for neovim lsp? Or maybe if there is some plugin that can auto detect the Makefile or CMakeList file and solve the problem?
In the explorer of VS Code I want to have the gitignored files grey.
I managed to add "gitDecoration.ignoredResourceForeground":"#CCCCCC", however I now have various files and folders where there are other decorations and it looks like explorer.decorations.colors takes precedence over this. This mechanism now destroys the coloring of the ignored resources again as it looks like this rule is checked later.
How can I fix this and have the gitignored rule applied no matter what happens otherwise?
This is for:
VSCode: Version: 1.73.1
Release: 22314
Commit: 14f2d26367b7e8f03ff2352516ba27d6302dd7b1
Date: 2022-11-10T18:37:51.314Z (2 wks ago)
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 19.6.0
Sandboxed: No
MacOS: Catalina 10.15.7
Git: 2.38.1
The screenshot shows a situation where chamaeleon/ is part of .gitignore. All files nicely are greyed out with the exception of ChameleonTemplate.php which contains a PHP error, as well as srcwhich contains a file containing an error and Components which contains another file with an editor decoration due to a type problem in PHP.
Clarification: My question is not about files which are only gitignored (they show uo correctly) but about files which are gitognored and have a further editor decoration (such as a syntax error). If these two decorations apply both then the question is which one takes precedence. That is the problem here.
My question is rather not a bug (as in "does not work as expected") but a conceptual one. If we have two different reasons for setting foreground color, and both reasons apply, which color is chosen?
A workaround would be if we were able to set other attributes such as underline, strike-through, background-color or font type and not only foreground-color, because such attributes could be combined. Foreground-color and foreground-color cannot be combined but needs a precedence rule.
Probably you should provide more information, like VS Code and git version. I am running VS Code 1.73.1 and git 2.37.1 in macOS and it works automatically.
Possible solutions:
It could just be a bug in VS Code or git. Check if you are running the latest versions.
Restart VS Code.
Try to clone the project again.
Check that your project is not a symlinked folder.
For me this happened automatically... I think you just need the high-contrast dark color theme in vscoode. You could also choose another color theme but this changes. You could also look into making you own color theme for vscode like I did, and edit the colors to your liking.
As you can see, fort-bishop.exe is grayed out. I have ignored it in my .gitignore.
Probably, you missed workbench.colorCustomizations.
In your settings.json:
"workbench.colorCustomizations": {
"gitDecoration.ignoredResourceForeground": "#ff0000"
}
Seems like a known issue. Yet, please add VSCode version details. Below are the possible workarounds which might help:
Clear the git cache, re-add the files and re-commit. Re-save the .gitignore files once again.
Make a dummy edit to the .gitignore file and try saving the file.
For some reason whenever I begin to type the file path after an #import rule in my main.scss file,
VSCode disconnects from WSL2. I am using WSL2 version 20.02 on Windows 10. VSCode is Version 1.54.1 (user setup).
I am pretty new to all this. I am simply trying to import an icon font that I selected from the icomoon.io app and I am using the sass files that the app generated. I am trying to copy and paste the variables into my own sass files. (I will also put the font in my files as well). I have some styles in "main.scss" just to kind of test things and then I have a bunch of variables in the _variables.scss file. I'll type #import and everything is fine but as soon as I begin to type the path within the "" WSL disconnects and cannot even read the _variables.scss or main.scss file, let alone save/write to the files.
I have to close the whole folder and reopen it again from the terminal using code bjf5201.github.io (bjf5201.github.io being my project folder name)
Any ideas?
I had the same issue and found out that it was because of the Color Highlight extension I was using. After disabling it, everything works fine.
There is an alternative extension colorize, which seems to be compatible and does the same thing.
I use the extension Latex Workshop, however my preview does not auto update on save. I have to run pdflatex each time.
I tried uninstalling and installing the extension, deleting the extensions file, and even reinstalled vs code. Yet, the same thing persists.
Is there a specific setting, etc that needs to be changed?
Strangely for me it only seems to work when configuring
latex-workshop.latex.autoBuild.run: "onSave"
As from here the setting for this is:
latex-workshop.latex.autoBuild.run
With value "onFileChange".
Note that this is the default value for this setting, so it should detect the changes automatically, but give it a try.
Local and ssh installation:
For me the problem was that I had Latex Workshop installed on SSH but not locally. After installing locally, the LaTEX icon showed up and also auto-compile on save worked right away.
I am using IPython notebook and I want to edit programs in an external editor.
How do I get the %edit file_name.py to open an editor such as Notepad++.
Running %edit? will give you the help for the %edit magic function.
You need to set c.TerminalInteractiveShell.editor, which is in your ipython_config.py. I'm not quite sure where this is located in Windows; on OS X and Linux, it is in ~/.ipython. You'll want to set the variable to be the full path of the editor you want.
Alternatively, you can create an environment variable EDITOR in Windows itself, and set that equal to the full path of the editor you want. iPython should use that.
I'm using Windows 7 and 8 (and 10TP) and Python 3.4.2.
I started with ipython locate to tell me where ipython thought config files suggested elsewhere should be. When I saw it was different I read around and came up with the following:
On my system, the ipython locate gave me c:\users\osmith\.ipython, not the _ipython you'll see mentioned in the YouTube videos done with Windows XP,
Look in the directory ipython locate specifies for a profile directory; if you aren't actively doing anything with ipython profiles, it should be .ipython\profile_default, if you are using profiles, then I leave it to you to s/profile_default/${YOUR_PROFILE_NAME}/g
Check the profile_default directory for a ipython_config.py file, if it's not there, tell IPython to initialize itself: ipython profile create
Open the config file in a text editor,
If you are the kind of person who hasn't messed around with their console overly much and installs things in standard places, you can skip straight to this step by typing: ipython profile create followed by start notepad .ipython\profile_default\ipython_config.py.
Search for the string c.TerminalInteractiveShell.editor,
The comment above this indicates you can also use the EDITOR environment variable, but hard coding file paths never hurt anyone so lets do eet:
Copy the line and remove the leading hash and spaces from the copy.
Replace the text between the apostrophes ('notepad') with the path of our desired editor, e.g.
c.TerminalInteractiveShell.editor = 'c:/program files (x86)/noddyeditor/noddy.exe'
There is a catch here, though; some modern editors get a bit fancy and automatically and, when invoked like this, detach from the console. Notepad++ and Sublime Text, for example. Sublime accepts a "--wait" option, which works some of the time; this tells the command invocation to hang around until you close the file, for some definition of until and some other definition of close.
However, the following setting will work most of the time for sublime text:
c.TerminalInteractiveShell.editor = '"c:/program files/sublime text 3/subl.exe" --wait'
(assuming c:\program files\ is where your sublime text 3 directory is)
Try the 'Pycharm' editor
This works for me.