I'm using a vscode customized theme that I changed to fit my needs, which I based on github dark for scopes. I'm finally in a spot I find it nice looking but I have a problem with fstring quotes, they simply don't get colored.
I've tried some scopes and just the punctuation.definition.string.begin/end worked. When I tried using the meta.fstring.python it changed the whole string color, quotes and text inside. The strange is that the raw (r"") strings work. Also there's this bug with the {var} inside the raw one.
Tried MagicPython to see if any of their Scopes work, but it didn't
Any suggestions as to which should I use to fix it?
Related
Does anyone know whether it's possible to customize the background of a text after it has been suggested by IntelliSense? I'm using the Everblush theme.
As you can see in the GIF, after selecting the suggested "activityBar.activeBackground" option in the settings.json, I get this annoying white background between the two quotes. This also happens with brackets and with other programming languages (Rust for example).
Do you have any idea on how to change this?
Keep in mind that this happens only after I press the ENTER key on option given by IntelliSense. It has nothing to do with normal text highlighting.
Following rioV8 suggestion, I found out that the option for this particular case is editor.snippetTabstopHighlightBackground.
All my whitespaces in VS code where code is written are being highlighted and I cant seem to understand where to change these settings.
In settings (open Command Palette CTRL+SHIFT+P and search for settings) menu search for Editor: Render Whitespace it is probably set to all instead of default selection. But i honestly have no idea why it is render with boxes and not dots or arrows, maybe it can be customized by using custom themes.
It was probably because of the theme the source was using from where I copied the source code. Replaced all these spaces with regular whitespace and now it's working fine.
I cannot get Sublime auto complete to work properly for custom syntaxes. For example, this is what happens when the syntax is set to Javascript:
When the syntax is set to my custom syntax, these types of suggestions never show up. Custom snippets show up just fine, but variables found in the file do not show up properly. When I click [CTRL+SPACE], this is what I get:
For some reason, single characters will show up, but not whole words. For the syntax, I copied the Completion Rules.tmPreferences, Symbol List.tmPreferences, etc. directly from here so that all should be fine (although messing around with them didn't seem to do anything).
I have tried adding the syntax to auto_complete_selector in settings, but it does not work. I use the package All Autocomplete, and deleting this did not change anything.
I am trying to make a custom theme for vs code and trying to change the colors for parentheses and braces/brackets, trying to use punctuation.definition but its not working, even when using the Inspect TM and scopes it shows I am using the correct scope and its showing the colors in my theme but the actual color its totally different, does anyone have any idea what's happening here ?
I use VSCode and I think its a great editor, but when I write a comment in html it drops to a new line under what I'm commenting which is really irritating.
If I comment a closing div I want it next to the closing div not under it.
I have uninstalled prettier but that made no difference.
Is what I want even possible in VSCode?
Any advise would be appreciated because I am so irritated that I am considering using a different editor (I'm on a Mac just in case it matters).
Thanks in advance.
This was a problem for me too, as were other new line / white space related HTML issues.
Assuming you are not using any formatters besides the native VSCode HTML language features (you said you uninstalled prettier, but you didn't mention whether you were using something else),
there is a setting HTML white space which you can set to preserve to leave your comments untouched.
Note that you may need to go into settings and check what is being used as the HTML default formatter