I've been working on my own color scheme, ripped out all the references to bold, and yet most identifiers still get bolded. Working on Gvim in windows. My guess is that there is a default setting that I haven't overridden.
Related
Something strange happened to me recently. I was testing the color schemes of Sublime Text 3 by selecting them from the menu Sublime Text > Preferences > Color Scheme. I did not find any that I liked more than my current one, but then I realized that the one I was using was not among the color schemes listed. Unfortunately I do not remember the name of the color scheme I was using.
By searching for popular color schemes online, I found one that is close: "Afterglow-twilight". However, the scheme I was using had much higher contrast, i.e. darker background and more vivid code highlight colors.
Is there a way in Sublime Text 3 to recover the color scheme I was using?
The color scheme that you're using is set as the color_scheme setting in your user preferences and the menu item Preferences > Color Scheme (which is under Sublime Text if you're on MacOS) allows you to more easily set that preference by showing you a list of all all most available color schemes along with letting you preview what they look like.
The short answer to your question is No, but the longer answer to your question is Yes.
The No is because unless you have your Preferences.sublime-settings file backed up somewhere (say if you use Dropbox to sync it) or under version control of some sort, then the value of the setting is gone now and the only way to get it back is to figure out what color scheme you were using so that you can reset it.
The Yes is because Sublime will only allow you to use color schemes that you have installed locally, and using the menu item outlined above allows you to pick between those you have installed (changing the setting as appropriate) but it doesn't remove any installed color schemes.
That means that unless you uninstalled a package in between when you were playing and noticed that your color scheme is no longer listed, that color scheme is still present even if the list isn't displaying it (and if you did uninstall a package, re-installing the package will bring it back). So all you need to do is figure out what it was.
There's a strikethrough in the first paragraph because Sublime hides some color schemes from you, so if you were using one of those it won't appear in the list and you need other means to find it.
The first thing to try is to add the following setting to your user settings (if it's not already there) to tell Sublime that legacy color schemes should also be listed:
"show_legacy_color_schemes": true,
Around the time the menu item for changing color schemes was added to the interface, some of the color schemes that used to ship with Sublime were relegated to Legacy status because they were wildly out of date and either not popular enough to warrant work to update them or impossible to fix without making visual changes.
Those color schemes are still present, but they're masked from the list of displayed color schemes unless you turn that setting on. So, in the case that you happened to be using one of those previously, this setting should let you find it again. Syntaxes that fall into this category will say Color Scheme - Legacy under them in the list.
If that doesn't turn up the color scheme that you were using, there is one last avenue of exploration. Sublime supports the idea of a hidden color scheme, which is generally something used by packages to give color schemes to things without more generally exposing them. Possibly there is a Theme out there for Sublime that distributes it's color schemes this way as well.
If you open the Sublime console with View > Show Console, you can enter the following lines one at a time into the input at the bottom of the window:
sublime.find_resources("*.hidden-tmTheme")
sublime.find_resources("*.hidden-color-scheme")
This will get Sublime to show you a list of all of the hidden color schemes (there are two different formats). Assuming either list is not empty, the items in the list represent hidden color schemes that the command mentioned above doesn't display.
If so, you can open your user preferences and manually set the color_scheme setting to each of the items in turn to see if one of them is the one you're looking for.
I use a particular color theme in the appearance preferences of LiClipse to change the appearance of the text in my editor for my PyDev projects.
I can easily change the color of any type of data that the editor interprets, except for strings. (Perhaps there's more but I have yet to discover them)
I am able in the Preference setting window to set any colors for strings, and I do see it being applied in the preview that the window shows, but when I click Apply, the strings in my code stays plain white. I've tried editing a couple of other data's color, and they all work great.
Following is two screenshots showing the settings window just before pressing "Apply", and my resulting code, in that order.
In the Preferences window, we can see in the preview that the "String" part is colored. Any color works. But then in my editor we can see that it did not apply, but all the other word object colors did.
My guess is that perhaps the strings in the PyDev editor are not interpreted as string, but instead something else.
I'm using LiClipse 4.5.2.201803171104
On Windows 7.
After a couple of trial and errors, I found out that by default, strings in the LiClipse PyDev editor are interpreted as constant.
Therefore, editing the color of constant changes the display colors of strings in the editor.
I just upgraded my Ubuntu laptop from 12.04 to 12.10.
In 12.04, running emacs -nw opened emacs in terminal mode using the terminal color scheme (background, foreground, ..., especially it keeped my transparent terminal background).
Now in 12.10, running the same command results in emacs opened in the terminal with an other color scheme (with a gray background). How can I tell emacs to keep my terminal color scheme ?
Thanks to https://stackoverflow.com/users/774691/john-k-doe's comment, I finally get the reason why my emacs -nw appeared like that.
I edited the font size (for the default face) in an emacs window (launched without the -nw option) and then saved this new setting using the menu entry Options -> Save Options. This action modified my ~/.xemacs/custom.el file loaded by default in my ~/.emacs file. The modification included background and foreground properties for the default face with the value used in "Window" mode.
To solve the issue, I just removed this custom entry from the custom.el file.
I'm not sure that there is a sensible answer to this. After all, a gnome terminal colour theme lists three "colours": (1) Text, (2) Background (3) Bold.
The way Emacs works is that every bit of text is given a "face". A colour theme is a mapping of faces to colours. There are more than three faces...
I am quite newbie.
After I have installed Studio3 plugin Eclipse, I got some problems of colors with Default Theme.
In these for the moment I have a not workaround situation while using the "Text compare" because I could not find how two change the color of elements which have the same color as background "black".
When black background is used, as the comparison mode uses black as default color for many elements they are hidden. I made some test with a variant grey background to find the elements, it obviously can't be used for normal use.
Where are the template definition for "comparison mode" seems the main question ?
The minimum to reach is that the black ForeGround colored elements (defined surely for white background) become white with a black background.
Elements of analysis :
The changes on other elements are taken in account in comparison mode (and obviously in edit mode which functions normally), but the elements that are not taken in account in comparison mode are black by default. So I look at a default color for not held elements, I could not find such an item. The default values that I found, and that I declared FG white, have no effect.
Thanks for help.
Trebly
Aptana Studio 3.0.7
No changes done to default parameters
context : Php
black elements in compare mode : vars; functions calls; names; syntax base;
hold elements : text; keywords (var, function, parent, class, extends, array, empty....); comments
After quite long search :
When Aptana studio3 plugin is installed, the default theme can not be well setup for others editors than Aptana such as standard comparison if you use the Aptana studio3 theme. Then you get incoherent display. The solution is simple.
To get everything right, if the application is able to hold new Aptana theme management, you must simply :
1- change the default Aptana studio3 theme for example for ECLIPSE (Base) theme
2- Change again to Aptana studio3 theme, this will reset all elements of themes (for various compatible editors)
Note : SmartyPDT (and others not tested probably) are not compatible with the theme management of Sudio3, in such case you need to stay with another theme as Studio2 (theme option in studio3). In fact the defined colors are compatible with studio2, particularly black standard text (which was default color). The incompatibility makes that you get a not a coherent fit of colors which lead to incoherency, which can't be avoided, worse black on black... for some text-elements.
Trebly
I'm using vim 7.3 in Lion OSX.
Whatever theme I have tried to apply retains the terminal's background color, which in my case I've set as Silver Aerogel theme.
Curiously, using the theme Zenburn works but breaks after awhile resulting in something that looks like the attached image. In my vimrc, I have this set set t_Co=256. My vimrc file: http://dpaste.com/699961/
Help guys?
I used to have this problem... Then I learned that color schemes designed for gvim or macvim are not necessarily compatible in a 256 terminal. If it wasn't designed for a 256 color terminal, try the csapprox plugin. (csappox description)