| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
palettes (#4221)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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>
|
| | |
|
| |
|
|
|
|
|
|
| |
* helix_view::theme [WARN] Theme
* updated: warning, error, info, hint colours
https://github.com/catppuccin/catppuccin/blob/main/docs/style-guide.md#typography
Co-authored-by: Aiko Mastboom <git@aiko.sh>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Add mode specific styles
In similar vein to neovim's lualine and similar statusline packages this
allows helix users to style their mode based on which mode it is thus
making each mode more visually distinct at a glance
* Add an example based on rosepine
* Add editor.colors-mode config
* Document statusline mode styles
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the bottom value is used, so i've removed the top `ui.help` values from all themes
also, the values are not merged, so:
```toml
"ui.help" = { modifiers = ["reversed"] }
"ui.help" = { fg = "white", bg = "black" }
```
is equal to:
```toml
"ui.help" = { fg = "white", bg = "black" }
```
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Add markup support for all Base16 themes
* Fix rose_pine `markup.link.text` attribute misname
* Add basic default markup support for all themes
* Fix cursor change color on Base16 terminal and default
* Remove old markup monokai_pro support and fix Onedark `markup.link.text` attribute misname
* Remove old markup dracula support
|
| | |
|
| | |
|
| |
|
|
|
| |
* adds: rose_pine_dawn.toml colorscheme
* chore: define ui.statusline.inactive colors of rose_pine
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
