aboutsummaryrefslogtreecommitdiffhomepage
path: root/lib/colors
AgeCommit message (Collapse)AuthorFilesLines
9 daysadded high-contrast color schemeRobin Haberkorn2-0/+40
* strings are bold (if supported) and bright white * comments are in italics (if supported by the terminal) * otherwise this uses the same colors as terminal.tes * should be well suited for monochrome terminals as well
2024-12-24introduced true block and EOL commentsRobin Haberkorn2-19/+19
* The previous convention of !* ... *! are now true block comments, i.e. they are parsed faster, don't spam the goto table and allow embedding of exclamation marks - only "*!" terminates the comment. * It is therefore now forbidden to have goto labels beginning with "*". * Also support "!!" to introduce EOL comments (like C++'s //). This disallows empty labels, but they weren't useful anyway. This is the shortest way to begin a comment. * All comment labels have been converted to true comments, to ensure that syntax highlighting works correctly. EOL comments are used for single line commented-out code, since it's easiest to uncomment - you don't have to jump to the line end. This is a pure convention / coding style. Other people might do it differently. * It's of course still possible to abuse goto labels as comments as TECO did for ages. * In lexing / syntax highlighting, labels and comments are highlighted differently. * When syntax highlighting, a single "!" will first be highlighted as a label since it's not yet unambiguous. Once you type the second character (* or !), the first character is retroactively styled as a comment as well.
2024-10-16Solarized color scheme: fixed F5 function key macroRobin Haberkorn1-2/+2
The macro prefix was changed from ^F to ^K.
2021-10-13improved default selection colors and made them configurable via color.tesRobin Haberkorn2-2/+8
* NOTE: Selections are currently only used to highlight search results. * The default selection colors were not always visible well with default settings (--no-profile) and they were not uniform across platforms. On Curses, the selection would be reversed, while on Gtk it had a lighter foreground color. They are now always reversed (black on white background). The default styles do not assume any color support - they use only black and white. * Since these defaults cannot possibly work on every color scheme, color.selfore and color.selback has been added to color.tes. All existing color schemes have been updated to configure selections as reversed to the default colors. This especially fixes selection colors on Gtk. * On solarized.tes, the caret style was already distinct from inversed default colors. On terminal.tes, the color of the caret is now bright white, so it stands out from the selection colors. * In Curses, the caret color is currently __not__ applied to the command line where it is continued to be drawn reversed. The command line drawing code is considered deprecated and will eventually be replaced with a Scintilla minibuffer. * In Gtk, we now apply the caret style to the commandline view as well. * Fixed the comment color in solarized.light.
2015-07-15changed default popup background color and color schemesRobin Haberkorn2-3/+3
* use black on light white as the default popup colors (e.g. in --no-profile mode). this looks less annoying than black on light blue and is more often more readable (since light blue will be rendered quite dark often). It's no longer necessary to highlight the popup with (distinct) colors. Keeping the foreground black ensures that there's a brighter foreground color for bold entries in case the terminal does not support bold fonts. * the `terminal.tes` scheme keeps the default popup style. However since it uses white on black as the default colors, this will often still stand out from the message line (on 16 color terminals). * `solarized.tes` now uses a similar high-contrast popup style with either a bright or dark background. The foreground colors have been chosen so that bright variants exist for non-bold terminals - although these bright variants do not stand out very much.
2015-07-14added port of the Solarized color schemeRobin Haberkorn1-0/+138
* see http://ethanschoonover.com/solarized * I don't know if I want this port to be linked into the main solarized repository as it is certainly not perfect. * However both light and dark modes are supported and usable since to SciTECO's new theming support. * Set -U[solarized.light] before munging to enable light mode. * Registers function key F5 to toggle between light and dark modes. * Works on ncurses (with some restrictions) and almost all other PDCurses ports. GTK+ also works somewhat, but not all parts of the GTK+ UI are currently themable.
2015-07-14fixed default colors in color.tes and style Q-Register viewRobin Haberkorn1-15/+25
* the RGB values of the 8 standard colors defined by color.tes were wrong (i.e. did not correspond to the normal 8 color codes defined by Scinterm but only the bright versions). Except for `color.black` which referred to terminal color 0. * now we define the 16 colors defined by Scinterm, allowing color schemes to explicitly use bright color versions without using the bold attribute. On 8 color terminals, the bold attribute might still be the only way to get a bright color. * terminal.tes: Use bright default color instead of relying on bold to get bright color versions. This is especially important for comments which where relied on bold black to be rendered grey. This did not work by default on terminals supporting bold fonts (e.g. OS X Terminal) or GTK+. The scheme now works on more terminals out of the box and on GTK+ and is thus a good default color scheme. * Color schemes will now also define the default style, the line number style and caret foreground/background. `color.calltip` is now also defined for STYLE_CALLTIP and can later be used to style SciTECO's custom popup widget.
2014-11-19added first draft of new modular lexer systemRobin Haberkorn1-0/+22