luxed/ayu-vim

Modern theme for modern VIMs

ayu-vim's Issues

Request: Support neovim diagnostic highlight groups

Reference: sainnhe/sonokai@9f7deae

Details: neovim/neovim#15585

Override default hex colors?

Hello,

I've been using the original ayu repo for quite sometime, I only just now found this fork and am making the switch.

I'm wanting to change a few of the hex colors, such as the editor_bg and editor_findMatch_inactive in the autoload/ayu.vim file. They're very similar and impossible for me to differentiate.

I can make these changes by over-riding them in-file, however I'm wondering if there's a way to do it without losing those changes when I update.

My knowledge on theming is almost non-existent, it took me a minute to even find this file.

Any tips?

Support new Neovim Floating Window Borders

Currently looks like this:

FloatBorder needs to be properly set.
Although this brings some issues: The current floating window color is the same as Pmenu, which is great when no borders are shown. With borders it would make more sense to set this color to the normal background instead.

One option would be to give the user an option like g:ayu_bordered_floats which would properly set the NormalFloat and FloatBorder colors.

With g:ayu_bordered_floats to false:

With g:ayu_bordered_floats to true:

I need to explore these a bit more and understand how everything works first. I know they were added recently, but I have no idea how they work, how they are enabled/disabled, etc.

Diff colors should be fixed

Here's how deleted lines diff color look:

I expect the color to be red.. Will that be fixed?

Highlighting of special characters in mappings buffer are difficult to read

When viewing the current mappings in Vim through something like :nmap, the resulting text is very hard to read for special characters:

coc.nvim suggestion menu current selection is not visible ```

when I write some text and coc presents the list of suggestions I cannot see which I select. See an example in the screen shot:

What do i have to modify to see the selection like it is the case with a different theme (e.g. seoul256)

These are the relevant lines in the .vimrc

set termguicolors                                                                                                                                                                    
set background=dark                                                                                                                                                                  
let g:ayucolor="mirage"                                                                                                                                                              
set t_Co=256                                                                                                                                                                         
colorscheme ayu                                                                                                                                                                                                                                                                                                        
"colorscheme seoul256                                                                                                                                                                 

Screenshots!

Post your screenshots here so everyone can see how the theme looks!

Here are mine:

Vimscript:

Lua (TreeSitter):

The colors of vim-floaterm are inconsistent

Using vim-floaterm to create a new terminal will look like this:

The ideal color should look like this:

How to adjust colors specifically for vim-floaterm？

update:
I added a rule and it works

" vim-floaterm: {{{
call ayu#hi('FloatermBorder', 'editor_fg', '')
" }}}

Can you take a look at the vimspector plugin? The colors of those buttons look a bit inconsistent

Lua reimplementation

Hi! Thank you for working on it! I re-implemented this theme in lua. Could be useful for Neovim-only users.

Fix markdown/treesitter missing highlights

Since the latest TreeSitter update, some highlights are missing (for example there are no highlights for the text part of a link).

For more information, see these changes

Improve tabline colors

Please apply PR ayu-theme#55 by @stsewd

Getting W18 warnings on vim startup

Vim version: 9.0

I am getting W18: Invalid character in group name errors on line 15, 311, 312, 313 and 316 of colors/ayu.vim

W18: Invalid character in group name

Starting with commit d6fc974, I'm getting the following error when starting Vim:

Error detected while processing /home/<user>/.vimrc[133]../home/<user>/.vim/plugged/ayu-vim/colors/ayu.vim:
line  395:
W18: Invalid character in group name
Press ENTER or type command to continue

%vim --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Apr 03 2023 07:45:49)
Included patches: 1-3995, 4563, 4646, 4774, 4895, 4899, 4901, 4919

I know the version is ancient, but that's what I'm stuck with at the moment, unfortunately. Maybe you can still make it work again?

tree sitter support

could you add treesitter support?

Not being able to customize theme

Hi, I'm trying to customize theme using the code snippet provided in readme.md, but it doesn't change highlight colors.
Probably I'm doing it bad because recently started with vim.

First I get hightlight group of the keyword I want to customize:

Then I add it to the function provided that is written in init.vim config file (adding all posible options to get a visible change for testing):

But it doesn't change anything. (Also tried changing extension to .jsx, .js and .ts)

What I'm doing bad? Sorry if is dumb question

Using ayu in vim 9.1.100

Activating the colorscheme does not work in my case. It results in a green background. Any ideas, whats going wrong? Thank you.

Incorrect Loading with Vim8 Native Pack Management

It seems that this repository is currently incompatible with vim8's native package management. In particular, it seems the colors directory is run before autoload, and therefore the necessary functions aren't defined yet.

Setting after vim has loaded through manually calling colorscheme seems to work fine, but doing so through ~/.vimrc produces the above issue.

Syntax highlighting differences between this fork and the original repository

I saw that some colors were updated to match the definitions in the ayu-colors repository. I'm not sure if this change is due to that, but I've noticed differences in syntax highlighting between this fork and the original:

(this fork on right, old on left)

Notice the difference in which variables recieve the blue color. Perhaps I'm just used to it, but I find the old highlighting to be easier to parse.

Was this intentional?

Sorry if this overlaps with the other syntax highlighting issues that are open.

Extra Syntax not working

When i use let g:ayu_extended_palette = 1 nothing changes please help me to fix this.

Screen Flash At Opening

Software

Hi, I'm using Ubuntu 23.10 with vim 9.0.1672. Installed ayu-vim by vim-plugin.

Problem

When I start vim with ayu-vim the terminal just flashes, looks like the theme is loading in a slow speed.

I have tried disable other plugins, but the only difference was the flash duration was shorter.

All three colors have this problem, although it is less noticeable with light color.

I am new to vim so I'm not sure which part I did wrong or how to solve it, could you take a look please?

Screencast.from.2023-12-29.16-25-46.webm

cursor disapper at the input position.

I found the cursor can be disapper, and i could not distinguish the cursor color.just as:

Is the colorscheme set or my vimrc config is not so correct?

Error color readability

I've found the ErrorMsg and Error colors hard to read with the light foreground (editor_fg):

ErrorMsg

Error

Switching to the background color (editor_bg) looks easier to read:

ErrorMsg

Error

Before opening a PR, I want to check some things:

1. Do you think that the error colors should change to something other than editor_fg?
2. If so, should they change to use the editor_bg or a different color? ie. for ErrorMsg and Error, use common_error with editor_bg instead of with editor_fg.
3. ErrorMsg uses common_error as the foreground, but Error uses common_error as the background. Should we change one of them to match the other? If so, which one?