| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
| |
The adwaita-dark theme has no distinction between active and inactive
buffers on a bufferline. Add contrast to clarify differences.
|
| |
|
|
|
| |
Based on vscode ayu badge.
|
|
|
|
| |
This uses the same color as comments, which is a light gray in both dark and light.
I think it also looks nice with italics.
|
|
|
|
|
|
|
|
|
| |
* adjust inlay hints and color modes for fleet dark
* adjust virtual + ruler color
---------
Co-authored-by: krfl <kr.fl@outlook.com>
|
| |
|
|
|
| |
Co-authored-by: Jens Getreu <getreu@getreu@web.de>
|
|
|
|
|
| |
These gruvbox variants were introduced before theme inheritance and
only differ by a few colors. This change cleans up the duplicated
theming with theme inheritance.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The gruvbox themes (gruvbox, gruvbox dark hard and guvbox light)
don't provide a colour for the new virtual inlay hints. Looking at the
original repo, and other derivatives, there doesn't appear to be a clear
definition of what inlay hints should be. Although most sources indicate
that it can be the same as the color for comments.
Considering that, this commit sets the new field on each of the three
themes to be gray1, same as commented text.
Signed-off-by: Josh Bainbridge <josh.bainbridge@gmail.com>
|
| |
|
| |
|
|
|
| |
The configuration differs between parameters (upright) and types (slanted).
|
|
|
|
|
|
|
|
|
|
|
| |
Taken from the official theme:
```json
"editorInlayHint.background": "#4d4d4dcc",
"editorInlayHint.foreground": "#ffffff",
"editorInlayHint.parameterBackground": "#4d4d4dcc",
"editorInlayHint.parameterForeground": "#ffffff",
"editorInlayHint.typeBackground": "#4d4d4dcc",
"editorInlayHint.typeForeground": "#ffffff",
```
|
|
|
|
|
|
| |
- fix: add `markup.strikethrough` for theme.md
- add virtual.inlay-hint
- fix ui.virtual.wrap
- rename light-white to grey-300
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* update pop-theme for color-modes
* fixed ui.statusline.select not worrking
* adjustments for nicer statusline visuals
* added status line color
|
|
|
|
| |
Currently a bit hard to discern inactive and active buffers in a
brighter environment.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Using the picker with syntax highlighting the
fallback `ui.selection` makes a lot of text,
especially for the light variant, hard to read.
Instead, use a lighter background for highlights
|
| |
|
| |
|
|
|
|
| |
changes (#6085)
|
| |
|
|
|
|
|
| |
Passed it on as ok in the initial PR because the wrong runtime directory
was being sourced on my system. It makes the all variable members horribly
dark.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Add Darcula Solid theme.
* Update darcula solid theme.
* Derive darcula-solid theme from original darcula
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add ayu_evolve theme
* ayu_evolve: fix typo + raw markdown highlight
* Update runtime/themes/ayu_evolve.toml typo
Co-authored-by: Michael Davis <mcarsondavis@gmail.com>
---------
Co-authored-by: Michael Davis <mcarsondavis@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
Without styling the primary and secondary selections differently, it's
impossible to tell them apart when cycling through selections.
Make the primary selection slightly brighter and secondary selections
slightly paler.
|
| |
|
| |
|
|
|
|
|
|
| |
Current monokai (pro or otherwise) seems too red and green,
missingthe bright aqua / cyan color found in Sublime's Monokai.
This adds a variant of monokai, which I named monokai_aqua.
|
| |
|
| |
|
|
|
|
| |
monokai_pro_spectrum
|
|
|
|
|
|
|
| |
* discern between rulers and whitespace, add sumiInk2
* darker background for menu and help, bold selection
* bold modifier for insert and select
* dark color for window separator
* bring ruler, whitespace, indent-guide together
|
|
|
|
|
|
|
|
| |
This is a slight divergence from the VSCode theme, but it's more
accurate.
https://github.com/primer/github-vscode-theme/issues/111
https://github.com/primer/github-vscode-theme/issues/88
|
| |
|
|
|
|
|
|
|
|
|
| |
The diagnostic indicator background did not match the column or rows background
colour as this was context specific, and the background for the indicator was
being explicitly set.
This commit removes the explicit value for the indicators background allowing
it to adapt to the context. This is aligns it with other themes, and resolves
the issue.
|
| |
|
|
|
|
|
| |
* Change built-in themes to use curly underlines
* Change fleet_dark to use curly underlines
|
| |
|
| |
|
| |
|