shatur / neovim-ayu Goto Github PK

Nvim is deprecating VertSplit and moving to WinSeparator for borders in 0.10. By default, WinSeparator links to normal which does not look great for most colorschemes.

I just discovered your wonderful colourscheme and really like it!
I have one little question though: Would you possibly consider to implement background transparency?
All the colourschemes I'm using currently are supporting it and it's a real useful addition in the setup I'm using ...

Hi, I found with the new treesitter update there is no highlighting in html/jsx files. With put this 3 groups is possible to solve. For now, I moved treesitter to a commit before the change of the groups highlighting. I hope this solve the problem with the highlighting. Thanks

Groups

['@tag'] = { fg = colors.keyword },
['@tag.attribute'] = { fg = colors.tag },
['@tag.delimiter'] = { link = 'Delimiter' },

• Treesitter with commit before changes
  

• With the 3 groups
  

• Without groups
  

Hello!
When I use nvim8 I got a error at startup

Error detected while processing /home/alek/soft/configs/nvim/init.vim[120]../home/alek/.local/share/nvim/site/pack/packer/start/ayu-vim/colors/ayu.vim:                
line  275:                                                                                                                                                             
E474: Invalid argument 

in init.vim I have

"THEMES:
set termguicolors " enable true colors support
let ayucolor="mirage" " for mirage version of theme
colorscheme ayu

I use wbthomason/packer.nvim as a package manager.

In nvim7 the error is not reproducible

First, great implementation of a wonderful color scheme. I am using both the dark and light variants depending on the time of day.
I know it's something that is part of nvim and vim in general, but I don't like those tilde signs that hang out where there is no text/code both in NvimTree and main editor.

Is there any way to have them removed?

Thanks!

I believe the background for Normal was removed for some reason in the following commit ff797aa.

This causes problems in various scenarios, for example here with vim.ui.input:

or here with fidget.nvim:

Is there a particular reason to remove it?
It seems like it would make sense to have a default color rather than have to specify it for every potential scenarios.

the buffer-picking function in barbar highlights the key to press in each buffer. can this color be improved to fit with the colorscheme instead of the default red?

Now that neovim/neovim#21100 has been merged, highlighting is different in files that support semantic tokens, which sometimes does not look as good as before.

I think it would be worthwhile to explicitly define highlighting for those, see the highlight groups here : https://github.com/neovim/neovim/blob/f69d531d84c52ed71b6b9dd9b05a077ca8896ff6/src/nvim/highlight_group.c#L267-L279

You can also use this neovim/neovim#21393 to identify the treesitter and semantic tokens at play, like so :

Hi,
Thanks for this theme. This is excellent theme with good colours combinations so far I have found and much easier to override the colour options.
Please include the example of setting up nvim-lualine as well in the readme file. Initially I thought lualine was not supported, but I managed to set it up.

For those who are struggling with dark comments, dark line numbers, dark visual selection and dark current cursor line and almost non-visible selected file in nvim-tree, following may help.

-- color selections: https://www.canva.com/colors/color-wheel/
vim.o.background = 'dark'
require("ayu").setup({
	mirage = false,
	overrides = {
		Comment = { fg = "#9e926f" },
		LineNr = { fg = "#5081c0" },
		Visual = { bg = "#5a4e39" },
		CursorLine = { bg = "#2e2e2e" },
	},
})
require("ayu").colorscheme()

require("lualine").setup({
	options = {
		theme = "ayu",
	},
})

Hello,

Thank you for this lovely theme. I was wondering if you would consider adding a feature to dim inactive windows, similar to 'folke/tokyonight.nvim’, 'catppuccin/nvim’, and 'rebelot/kanagawa.nvim’?

I’m afraid that I’m very new to nvim and lua and therefore creating a pull request is a bit beyond my meagre capabilities right now.

Thanks again.

Markdown is not properly support by ayu when also using Treesitter.
For example:

• titles with "#" are not bold
• text within "..." is not bold
• code within "``" looks like a comment

Otherwise the colorscheme is amazing!

Hi,

When I use Nvim without Tmux, everything runs smoothly. However, when I'm inside Tmux, certain elements end up with a background color:

I can manually set the background color to transparent for some elements, but I suspect there might be an issue with my configuration file causing me to do it this way.

Any solution for it?
Thanks!

Sorry for asking a question that others might find very obvious.

Can you please point me to the variable that holds the color value for the highlighted text in visual mode, so I can set a brighter color?
I feel somehow that it blends in with the background, at least on my monitor, and I have to focus more to see what's highlighted.

Thanks!

Hi, could you please tell me how to make the background color of the editor window as black? Black as in deep/dark black. I would require a script setup as I'm very new to this colorschemes setup.

Hi there. Could you help me figure out why overriding highlights is not working in my setup?

This is how I load your package:

use {'Shatur/neovim-ayu', config = function() require('mrv.plugins.ayu') end} -- Ayu theme for Neovim

and inside my config file mrv.plugins.ayu I have:

vim.g.ayu_mirage = false

local colors = require('ayu.colors')

vim.g.ayu_overrides = {
  LineNr = {fg = colors.white}
}

vim.cmd [[ colorscheme ayu ]]

Thanks for your time!

See nvim-treesitter/nvim-treesitter@42ab95d

I took a quick look at https://github.com/Shatur/neovim-ayu/blob/master/lua/ayu/init.lua and there doesn't seem to be a good place to add the new hl calls. I can make the change if you let me know how to approach it. Perhaps a new function for the treesitter highlights? Also, my read of it is that it only affects these four groups -- is that right? https://github.com/Shatur/neovim-ayu/blob/master/lua/ayu/init.lua#L117

My numbers are gray and not orange.

PS. Sorry if this is a very minor issue. I just wonder if I should do something at the configuration level.

Screenshot:

Details

• Neovim. v0.7.2 (I am in Neovim from the terminal).
• OS. Linux Mint.
• Terminal: gnome-terminal.

Hi, thanks a lot for making this wonderful theme!

nvim-treesitter-context uses the highlight group TreesitterContext to change the colors of the context (e.g. the current function).
This highlight is used to distinguish the context from the rest of the buffer.

However, the fallback is NormalFloat which makes the context almost identical with the rest of the buffer (note the context lines numbered 10 and 3):

It would be nice if this situation can be improved, thanks a lot in advance!

This is not an issue but i wanted to contact you.

Would you like to take a look at: https://github.com/CantoroMC/neovim-ayu
I've taken what you have done so far and added some features:
i) divided set_groups in different function and loaded asynchronously with vim_loop some of them.
ii) aligned color of the various variant with the original ayu theme.
iii) added some plugins highlightings.
iv) added global variable to italicize comments and string, darken or shading floating window, and some "sidebars" (packer, nvim tree, terminal...), and disable borders between windows and "sidebars"

I've tried to make as many commits as change arguments.
Feel free to use it or if it all the changes (or almost) pleases you, please add me as a collaborator and merge the changes; so we will have only your repository.

I will add detailed documentation when I have some garbage time, probably next week.

Regards

When I change the cursor line of all 3 color styles (dark, mirage, and light) the cursor doesn't change for some text but does for others. Please see screenshots. This issue is for all 3 styles.

Cross-posting an issue here: ggandor/leap.nvim#27. As I posted in a comment there, I don't know if this is actually a bug with ayu.

I've worked around this for now:

local ayucolors = require("ayu.colors")
ayucolors.generate() -- Pass `true` to enable mirage

require("ayu").setup({
	overrides = {
		Cursor = { bg = ayucolors.line },
	},
})

https://github.com/Luxed/ayu-vim/blob/master/autoload/airline/themes/ayu.vim

Hello. Thanks for the awesome theme.

Started to get error after latest :PackerSync. I wonder if that could be somehow realted with the latest commit.

Error detected while processing /Users/kuzyo/.local/share/nvim/site/pack/packer/start/neovim-ayu/colors/ayu-light.lua:
W18: Invalid character in group name
W18: Invalid character in group name
W18: Invalid character in group name
W18: Invalid character in group name

When adding an override to the Ayu color scheme the result does not alter the displayed colors.

Code:
opt.termguicolors = true -- enable 24-bit RGB colors
cmd('set background=dark')
cmd('colorscheme ayu-dark')

require('ayu').setup({                                                                                                                            
    mirage = false,                                                                                                                              
    overrides = {                                                                                                                                    
        Comment = { fg = "Gray63" },                                                                                                                 
        line = { fg = "#ffcc66" }                                                                                                               
     },                                                                                                                                                
})

Expected behavior:
Line numbers are #ffcc66 - a golden yellow color, and comments are a gray.

Actual result:
Colors are unchanged from their default values

:highlight comment                                                                                                                                               
Comment        xxx cterm=italic gui=italic guifg=#626a73 

:highlight linenr                                                                                                                                                
LineNr         xxx guifg=#242a35 

I have tried using guifg and fg and neither produces the result I’m expecting.