You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VSCode: bioSyntax extension causes theme to reset to VSCode default #60
Issue: When making a new tab and editing it, or switching tab, the VSCode theme is always reset to the default dark VSCode theme. After setting the theme preference, the theme is always overwritten upon editing in a different tab.
I used extensions bisect to identify that bioSyntax was the cause of the issue.
Extension version: 0.0.11
VS Code version: Code 1.58.2 (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:09:06.581Z)
OS version: Darwin x64 19.6.0
Restricted Mode: No
System Info
Item
Value
CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)
@liyao001 thanks for your quick reply, much appreciated.
This issue only started happening for me within the last few days, and as a user it was frustrating because it wasn't at all clear what was causing my theme to revert. I ended up spending a fair amount of time diagnosing it.
Is there a reason that Biosyntax can't leave the user's theme choice alone when the user isn't in a compatible file: and / or revert the user's theme when entering a non-compatible file?
If that is not possible I would respectfully suggest that theme changing could be an opt-in feature, documented in the install steps, rather than an opt-out. I appreciate that it's a core part of the Biosyntax functionality, but I would suggest that it shouldn't be at the expense of VSCode's normal expected behaviour. Just an opinion!
All the best,
Reacted by elwood68, Danilo Imparato, Dennis Dollée, Daniel Himmelstein, Hongxiang Chen, Sean Aubin, Aaron Virshup, Orestis Ousoultzoglou and Artem Babaian
The solution doesn't fix the issue when auto-detect color scheme is activated (will change the theme based on OS theme light or dark) so the user can't define a specific theme using the extensions settings bio syntax non bio theme since it changes automatically. The default theme refers back to dark+ even when OS is in light mode.
Extension version: 0.0.11
VS code: 1.83.1 (Universal)
Date: 2023-10-19
OS: Darwin arm64 20.6.0
Activity
liyao001 commentedon Aug 4, 2021
MillironX helped fix this issue. You can assign a theme for all other file types by the following steps:
Locate the settings for bioSyntax by clicking:
Change the value of
BioSyntax.nonBioThemeto the name of the theme that you want to use for all other file types (for example,Monokai)Restart VS Code to make the changes effective.
harryjubb commentedon Aug 4, 2021
@liyao001 thanks for your quick reply, much appreciated.
This issue only started happening for me within the last few days, and as a user it was frustrating because it wasn't at all clear what was causing my theme to revert. I ended up spending a fair amount of time diagnosing it.
Is there a reason that Biosyntax can't leave the user's theme choice alone when the user isn't in a compatible file: and / or revert the user's theme when entering a non-compatible file?
If that is not possible I would respectfully suggest that theme changing could be an opt-in feature, documented in the install steps, rather than an opt-out. I appreciate that it's a core part of the Biosyntax functionality, but I would suggest that it shouldn't be at the expense of VSCode's normal expected behaviour. Just an opinion!
All the best,
celinebalaa commentedon Oct 19, 2023
The solution doesn't fix the issue when auto-detect color scheme is activated (will change the theme based on OS theme light or dark) so the user can't define a specific theme using the extensions settings bio syntax non bio theme since it changes automatically. The default theme refers back to dark+ even when OS is in light mode.
Extension version: 0.0.11
VS code: 1.83.1 (Universal)
Date: 2023-10-19
OS: Darwin arm64 20.6.0
williamrowell commentedon Mar 1, 2024
I'm still seeing this issue as well, even after following the instructions above.
ababaian commentedon Mar 2, 2024
@harryjubb I think is right, I put up a "Caution" note on the install instructions for VSCode.