th3whit3wolf / one-nvim Goto Github PK

8767c8e
This commit has changed the normal background color(syntax_bg).
Is this an intended change?

This color is no longer one-dark
https://github.com/atom/atom/tree/master/packages/one-dark-syntax
https://github.com/joshdick/onedark.vim

Right now when one_nvim_transparent_bg is true, the sign column and cursor line number look like this:

But they should have transparent backgrounds too.

This can be fixed with highlight SignColumn guibg=0 and highlight CursorLineNr guibg=0 but I think it should be part of the colorscheme.

The IncSearch highlight should probably have a background to distinguish matches better. This background could ideally be a completely different color (or even just a slightly different hue) than the Search highlight.

The issue can be seen when matching Numbers, Booleans, and more:

As you can see, the matched line is highlighted differently, but the matched text is not during incsearch (because the IncSearch highlight matches these other highlight groups). When <CR> is pressed, the match is highlighted more clearly by the Search highlight:

This gets even more confusing when there are other incsearch matches in the buffer, because everything except for the first match is highlighted clearly during the search.

If want to change the color of a particular highlight group, can't overwrite it in the usual way.
For example, it cannot be changed by the following method

highlight! ALEErrorSign guifg=#E06C75

Onebuddy could change this way.

If want to do the same with one-nvim, have to do the following

autocmd Colorscheme * highlight ALEErrorSign guifg=#E06C75

Can fix it?

I'm using the latest nvim (v0.5.0-dev+1112-ge55ded00c), alacritty with tmux (the result the same without tmux)

init.vim

...
syntax on
set termguicolors
set t_Co=256
set background=dark
colorscheme one-nvim
...

.zshrc

...
export TERM="xterm-256color"
...

Here's how the colorscheme looks in my terminal (which is termite):

Compare that to the screenshot given in the readme:

I'm using neovim-0.5.0+ubuntu2+git202106062340-f2906a466-d569569c9 with nvim-treesitter (latest)

Currently structs in rust look like this:

Here's how it looks after I changed TSField from Identifier to Normal:

In your screenshot fields look more like mine, would you consider changing it?

I'm using neovim 0.5.0-1 on ArchLinux with nvim-treesitter (latest).
When I was editting a C file, the background of the macro is werid and I cannot recognize what the value it is clearly.

And when I was coding just not finished, lsp-diagnosis will display like this:

I don't know how to deal with it, would you consider changing it?
Thank you.

I'm not sure if the code lens highlight groups are set, but by default they are a bit too jarring.

As a quick fix, I've linked it to the Comment highlight vim.cmd [[ highlight link LspCodeLens Comment ]] and I think the result looks much better.

After updating, I get this message:

I did as it is written in the instructions, but when starting gvim, it gives errors that there is no such topic
init.vim
`syntax enable "включает подсветку синтаксиса
set termguicolors
set mouse+=a
set autoindent "авто-отступ строки
set tabstop=2
set shiftwidth=2
set expandtab
set smartindent
set textwidth=80 "длина строки
"set number "показать номера строк

colorscheme one-nvim
vim.g.one_nvim_transparent_bg = true

let g:airline_powerline_fonts=1 "Включить поддержку Powerline шрифтов
let g:Powerline_symbols='unicode' "Поддержка unicode

" Plagins
call plug#begin()

Plug 'Th3Whit3Wolf/one-nvim'

Plug 'Pocco81/AutoSave.nvim'

Plug 'glepnir/galaxyline.nvim' , {'branch': 'main'}
Plug 'kyazdani42/nvim-web-devicons'
Plug 'romgrk/barbar.nvim'

Plug 'nvim-lua/plenary.nvim'
Plug 'nvim-telescope/telescope.nvim'
Plug 'akinsho/flutter-tools.nvim'

Plug 'preservim/nerdtree'

Plug 'ryanoasis/vim-devicons'

call plug#end()

lua << EOF
require("flutter-tools").setup{}
EOF

lua << EOF
require("telescope").load_extension("flutter")
EOF

lua << EOF
require('spaceline')
EOF`
one-nvim ./config/nvim/plugged/one-nvim
if you copy the one-vim.vim file to colors, then there are even more errors...

Hi!
https://github.com/Th3Whit3Wolf/one-nvim/blob/main/lua/one-nvim.lua#L12-L20

In terminal mode zsh-autosuggestions dissapear.
How it should be:

How it is:

It's a flaw of almost every vim theme, that's why I have the following in my config:

  let g:terminal_color_8=8

which makes suggestions look just like they look in my regular terminal.
Perhaps you would like to put the same (or a bit different) color setting into one-nvim.

Not an issue as much as a feature request. Neovim 0.5.0 will include a built-in LSP client. This client defines some highlights, viewable at :help lsp-highlight. These may include the following for references:

LspReferenceText
LspReferenceRead
LspReferenceWrite

And the following for diagnostics, which are all in the form of LspDiagnostics<Something> with Error, Warning, Information and Hint variants:

LspDiagnosticsDefaultError
LspDiagnosticsDefaultWarning
LspDiagnosticsDefaultInformation
LspDiagnosticsDefaultHint
LspDiagnosticsVirtualTextError
LspDiagnosticsVirtualTextWarning
LspDiagnosticsVirtualTextInformation
LspDiagnosticsVirtualTextHint
LspDiagnosticsUnderlineError
LspDiagnosticsUnderlineWarning
LspDiagnosticsUnderlineInformation
LspDiagnosticsUnderlineHint
LspDiagnosticsFloatingError
LspDiagnosticsFloatingWarning
LspDiagnosticsFloatingInformation
LspDiagnosticsFloatingHint
LspDiagnosticsSignError
LspDiagnosticsSignWarning
LspDiagnosticsSignInformation
LspDiagnosticsSignHint

Thanks for the beautiful theme!

Thank you for the nice theme! I really enjoy it and submitted it to nixpkgs.
I've spotted weird colors in terminal mode. I am using vim-floaterm with zsh shell and zsh-syntax-highlighting plugin.
Despite overall syntax highlighting this plugin highlights wrong binaries with red, good ones with green:

But in neovim with one-nvim colorscheme it suddenly highlights right paths with red, bad paths with grey:

Also, paths in git status are barely visible: