Sublime text 4 on windows 11 and debian linux
Syntax highlighting currently applies in real time, while typing. I do not like to see full lines highlighted when I am writing or editing a line, but I do want to see those errors highlighted when saving or running.
Is there a way to change when syntax highlighting is applied?
Related
Any reason why :h lsp doesn't show any syntax highlight, where as h: mason does provide some syntax highlight of embedded LUA code? Within a same session, opened help files in 2 different tabs (you can see in the images below). Below are images for references,
I'm expecting all help files containing embedded code should get syntax highlight.
I'm not sure how I got this, maybe via some extension that was installed on my VS Code, but I need to disable this.
There is currently no setting to disable/hide these "squiggly lines". VS Code indicates them as errors or "Problems" with your code, and it's always recommended to address the problems rather than to hide them.
But there are workarounds.
Change the color
You can customize the color to make it transparent:
"workbench.colorCustomizations": {
"editorError.foreground": "#00000000",
}
You can also customize it so that it looks like the editor background.
"workbench.colorCustomizations": {
"editor.background": "#282a36",
"editorError.foreground": "#282a36",
}
If you are using a theme, you can get the theme's current value for editor.background by opening the command palette, then selecting "Developer: Generate Color Theme from Current Settings", which will open a JSON file containing all the theme colors. Look for editor.background.
You could also set it to something that isn't as striking as bright red.
Note that this way just hides the "squiggly lines". The errors will still show up in the Problems panel and when you hover your mouse over the line.
Disable Python linting
For Python, if you look at the Problems tab, the error is actually raised by the Python Linters that come with VS Code and the Python extension. In my case, I'm using pylint.
You could disable these linters by calling the Python: Enable Linting command command and setting it to off, or by putting this in your settings.json:
"python.linting.enabled": false,
Note that this way not just hides the red squiggly lines, but stops linting altogether, so you also won't see anything in the Problems panel.
This is harmful to the development process as it stops checking for "syntactical and stylistic problems in your Python source code, which oftentimes helps you identify and correct subtle programming errors or unconventional coding practices that can lead to errors.".
I don't recommend doing this.
If I create a simple Makefile in an Rstudio Text File:
graphic1.jpeg : mouse.csv graphic1.R
Rscript graphic1.R
It will not execute. I get the error message, "Makefile:2: *** missing separator. Stop." because the tab in line 2 is not really a tab.
If I edit the Text File in Text Wrangler, a real tab will be inserted and the file will execute.
I have updated my RStudio Preferences / Code to ensure that the box is unchecked for "insert spaces for tab".
Is this just a bug in RStudio text editor?
If you want to change this setting temporarily e.g. to tabulate a Makefile or a .tsv file, the fastest way is to only change the Project Options, do your stuff, and then revert it back.
The project options take precedence over Global Options, so changing the global ones only makes sense if you want to keep that option enabled for all future projects.
So I just learned from an R-Bloggers post by Jeffrey Hollister that there are two places in RStudio where I need to uncheck "Insert spaces for tab":
1) RStudio / Preferences / Code
2) Tools / Project Options / Code Editing
I am now up and running.
I have somehow added two SCSS syntax highlight options. One of keeps resetting to be the default (but it doesn't correctly highlight SCSS, it looks more like how the plain CSS highlighter does).
Every time I open a file I have to manually set it to be the correct one through the command pallet.
Here is a screen shot showing them both:
Check your installed packages. I guess it is from a third party package.
You also could deactivate them all and reactivate them one by one to find the package bringing the wrong highlighter.
Sublime Linter suddenly isn't displaying the nice ui highlighting it used to. It also isn't displaying lint messages in the bottom left of sublime. This may have happened after a recent windows update, but i wasn't paying close enough attention to be sure exactly when it occurred. I've followed the troubleshooting section on the documentation, and verified jshint is working in the command line. I've also switched to debug mode but I see no Linter errors in the console. I've also tried switching to manual lint mode, but the "Lint This View" option is grayed out. Not sure what to do at this point. Any suggestions?
You mention that you recently updated your copy of Windows, so it's possible that the Environment Variable for node(and other variables) have been removed or erased, I suggest you check that first.