Open neumachen opened 7 years ago
Does this happen when editing files other than Ruby? It may be that the screenshot is using some other syntax for ruby.
@magicalbanana could you please provide vim version, tmux conf and terminal info?
Same deal in JavaScript (see const
vs then
), except it doesn't matter if I'm in tmux or not:
NeoVim version:
NVIM v0.2.0
Build type: Release
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_MSGPACK_HAS_FLOAT32 -DNDEBUG -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -I/tmp/neovim-20170707-80027-1bg0wcx/neovim-0.2.0/build/config -I/tmp/neovim-20170707-80027-1bg0wcx/neovim-0.2.0/src -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/opt/gettext/include -I/usr/include -I/tmp/neovim-20170707-80027-1bg0wcx/neovim-0.2.0/build/src/nvim/auto -I/tmp/neovim-20170707-80027-1bg0wcx/neovim-0.2.0/build/include
Compiled by brew@Sierra-2.local
Optional features included (+) or not (-): +acl +iconv +jemalloc +tui
Using zsh, but not setting any special properties that I'm aware of.
@jlowgren const
was meant to be orange
@magicalbanana I think it's because inside tmux you're falling back to the 256 colors version, which has a washed out red.
Not sure why this is doing this. I am sourcing the script for colors as per documentation.
And I noticed this only happens in tmux. I'm using a MacBook Pro late 2013.