| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
| |
Co-authored-by: ryan.palmer <ryan.palmer@servicenow.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* lint: snazzy
* lint: pop-dark
* lint: penumbra+
* lint: noctis_bordo
* lint: ingrid
* lint: flatwhite
* lint: doom_acario_dark
* lint: dark_plus
* lint: boo_berry
* fix: use 47345E per author instruction
* lint: bogster
* lint: everforest
* lint: acme
* lint: serika
* fix: use nasty_red per author suggestion
* lint: nord
* lint: dracula
* lint: gruvbox
* fix: cursorline gruvbox
* lint: autumn
* fix: no fg for cursorline
* lint: ayu
* lint: rose_pine
* lint: monokai
* lint: solarized
* lint: spacebones
* fix: penumbra bg!=sky
* Update runtime/themes/ayu_light.toml
Co-authored-by: Ivan Tham <pickfire@riseup.net>
* Update runtime/themes/ayu_light.toml
Co-authored-by: Ivan Tham <pickfire@riseup.net>
* fix: fg for ui.help thanks @pickfire
* fix: ingrid with input from @intarga
Co-authored-by: Ivan Tham <pickfire@riseup.net>
|
| |
|
|
|
| |
* fix: gruvbox color modes
* increase contrast, and use blue and not purple
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Default rulers color to red
Currently if the theme a user is using doesn't have `ui.virtual.rulers`
set and they set up a ruler it just fails silently making it really hard
to figure out what went wrong. Did they set incorrectly set the ruler?
Are they using an outdated version of Helix that doesn't support rulers?
This happened to me today, I even switched to the default theme with
the assumption that maybe my theme just doesn't have the rulers setup
properly and it still didn't work.
Not sure if this is a good idea or not, feel free to suggest better
alternatives!
* Use builtin Style methods instead of Bevy style defaults
Co-authored-by: Michael Davis <mcarsondavis@gmail.com>
* Only default the style if there's no ui or ui.virtual
* Update themes style from ui.virtual to ui.virtual.whitespace
* Revert ui.virtual change in onelight theme
* Prefer unwrap_or_else
Co-authored-by: Michael Davis <mcarsondavis@gmail.com>
|
| | |
|
| | |
|
| |
|
| |
Missed in the commit 943fca332e.
|
| |
|
| |
As recommended by @archseer in https://github.com/helix-editor/helix/pull/1509#issuecomment-1013583069
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* updated theme scopes
variable.property -> variable.field
property -> variable.field
* updated theme scopes
* update book and themes
updated book and themes to reflect scope changes
* wip
* update more queries
* update dark_plus.toml
|
| |
|
|
|
|
|
|
|
| |
* changed some gruvbox highlights
* more stuff including cursors
* use property instead
* use variable.property
|
|
|
* Enable using color palettes in theme files.
* Add an example theme defined using a gruvbox color palette.
* Fix clippy error.
* Small style improvement.
* Add documentation for the features to themes.md.
* Update runtime/themes/gruvbox.toml
Fix the value of purple0.
Co-authored-by: DrZingo <DrZingo@users.noreply.github.com>
Co-authored-by: DrZingo <DrZingo@users.noreply.github.com>
|
