-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] Ability to 'export' colors to the VS color settings #313
Comments
Exporting colors is not possible at this time. I had reproduced the "Codist is NOT performing any syntax coloring initially" problem and fixed it in version 7.8. Please give it a try. |
I read your post in the Development Community. If exporting only styles used in code editor is your goal, the implementation is much easier and viable. Maybe it will be possible in the future. |
Thanks for considering the idea! I really cannot ask for more than that -- any actual implementation is a hope & dream, depending purely on your interest and kindness in sharing all your hard work! Thanks again! BTW, v7.8 appears to be working great with VS2022, so good job on the fix for the initial style settings (and more)! |
This is just a dream, so feel free to immediately discard if this is not possible...
With the startup issue that v7.7x is having with syntax coloring in VS2022, it might be useful to be able to have Codist write all of our color settings to the matching settings directly within VS2022 "Fonts & Colors" settings. I understand that many colors don't have equivalents and others may come from other extensions, but at least the most basic (keywords, numbers, strings, variables, etc.) would keep code from looking quite so alien first thing in the morning.
This assumes that Codist is NOT performing any syntax coloring initially and only starting after I import my saved colors (or otherwise interact with the Codist styling settings). If Codist is responsible for the strange initial colors, then I cannot think of a reason why the colors I'm porting cannot be saved to the location where Codist is obtaining the strange initial colors. If those are hard-coded, I don't understand why Codist doesn't always load the color/style settings when it starts up. But then, I don't know anything about the troubles if interacting with Microsoft's horrible mess of extensions and VS Fonts & Colors -- but I can imagine, based on the horrible mess of the Source Code Control Plugin interface (which I've suffered through to allow VS2022 to use our old 32bit SCCP.)
Of course, this may be fixed in v7.8 (which I have not yet tried).
The text was updated successfully, but these errors were encountered: