Giter VIP home page Giter VIP logo

onedark.vim's Introduction

onedark.vim

A dark Vim/Neovim color scheme for the GUI and 16/256/true-color terminals, based on FlatColor, with colors inspired by the excellent One Dark syntax theme for the Atom text editor.

Color Reference

Color Reference

Breaking Changes

Pull request #271, merged July 11, 2021, contained several breaking changes, especially for 16-color users.

If you are an existing onedark.vim user that is suddenly having issues after this PR was merged, see the PR description for details.

Supported Plugins

onedark.vim includes support for the following Vim and Neovim plugins:

Installation

  1. Install the theme using your Vim plug-in manager of choice (or manually, by placing colors/onedark.vim in your ~/.vim/colors/ directory and autoload/onedark.vim in your ~/.vim/autoload/ directory.)

    The theme also supports being installed as a Vim 8 package. Simply clone this repository into ~/.vim/pack/*/opt/ (so that the local path to this README would end up being ~/.vim/pack/*/opt/onedark.vim/README.md) and add packadd! onedark.vim to your ~/.vimrc. (The * in the path can be any value; see :help packages for more information.)

  2. If you use Vim in a terminal, do the following to test whether your terminal emulator supports 24-bit/"true" color, then add relevant ~/.vimrc configuration if so:

    Note: GUI (non-terminal) Vim will always display 24-bit color regardless of the configuration done in this step.

    Run the following snippet in your shell:

    printf "\x1b[38;2;255;100;0mTRUECOLOR\x1b[0m\n"

    If your terminal emulator does NOT display the word TRUECOLOR in red, it does not support 24-bit color. If you don't want to switch to a different terminal emulator that supports 24-bit color, proceed to step 3. (After installation, the g:onedark_termcolors option may interest you.)

    If your terminal emulator displays the word TRUECOLOR in red, it supports 24-bit color, and you should add the following lines to your ~/.vimrc to enable 24-bit color terminal support inside Vim.

    (If you use tmux, be sure to view the tmux-related notes in the first few lines.)

    "Use 24-bit (true-color) mode in Vim/Neovim when outside tmux.
    "If you're using tmux version 2.2 or later, you can remove the outermost $TMUX check and use tmux's 24-bit color support
    "(see < http://sunaku.github.io/tmux-24bit-color.html#usage > for more information.)
    if (empty($TMUX))
      if (has("nvim"))
        "For Neovim 0.1.3 and 0.1.4 < https://github.com/neovim/neovim/pull/2198 >
        let $NVIM_TUI_ENABLE_TRUE_COLOR=1
      endif
      "For Neovim > 0.1.5 and Vim > patch 7.4.1799 < https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162 >
      "Based on Vim patch 7.4.1770 (`guicolors` option) < https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd >
      " < https://github.com/neovim/neovim/wiki/Following-HEAD#20160511 >
      if (has("termguicolors"))
        set termguicolors
      endif
    endif
  3. Add the following to your ~/.vimrc (below any lines you may have added in steps 1 and 2):

    syntax on
    colorscheme onedark
  4. Installing the sheerun/vim-polyglot plug-in is recommended for improved syntax highlighting for various languages, but is not required.

Options

Note: All options should be set before the colorscheme onedark line in your ~/.vimrc.

  • g:onedark_hide_endofbuffer: Set to 1 if you want to hide end-of-buffer filler lines (~) for a cleaner look; 0 otherwise (the default).

  • g:onedark_termcolors (see Troubleshooting (below) for more information about this option): Set to 256 for 256-color terminals (the default), or set to 16 to use your terminal emulator's native 16 colors.

  • g:onedark_terminal_italics: Set to 1 if your terminal emulator supports italics; 0 otherwise (the default).

lightline.vim Colorscheme

lightline-onedark.vim Preview

This repository includes a companion lightline.vim colorscheme for use with onedark.vim.

The lightline.vim colorscheme:

  • Depends on autoload/onedark.vim for its colors, and must therefore be used in conjunction with it.
  • Works with both color modes available in onedark.vim (16 or 256 colors), as specified in the configuration for onedark.vim.

Installation

(These instructions assume that lightline.vim and onedark.vim are already installed and configured to your liking.)

Place onedark.vim/autoload/lightline/colorscheme/onedark.vim in your ~/.vim/autoload/lightline/colorscheme/ directory either manually or by using your Vim plug-in manager of choice, then add the following lines to your ~/.vimrc (or merge them into your existing lightline.vim configuration):

let g:lightline = {
  \ 'colorscheme': 'onedark',
  \ }

vim-airline Theme

airline-onedark.vim Preview

This repository includes a companion vim-airline theme for use with onedark.vim.

The vim-airline theme:

  • Depends on autoload/onedark.vim for its colors, and must therefore be used in conjunction with it.
  • Works with both color modes available in onedark.vim (16 or 256 colors), as specified in the configuration for onedark.vim.
  • Is based on vim-airline's "tomorrow" theme.

Installation

(These instructions assume that vim-airline and onedark.vim are already installed and configured to your liking.)

Place onedark.vim/autoload/airline/themes/onedark.vim in your ~/.vim/autoload/airline/themes/ directory either manually or by using your Vim plug-in manager of choice, then add the following line to your ~/.vimrc:

let g:airline_theme='onedark'

Troubleshooting

Why do the colors in terminal Vim look totally crazy?

Broken Colors

If Vim looks similar to the screenshot above, you have enabled Vim's 24-bit color terminal support, but your terminal doesn't support 24 bit color. Remove the relevant ~/.vimrc configuration for enabling 24-bit color support to get things looking better.

Why do the colors in terminal Vim look slightly off/not like the preview image at the top of this README?

If your terminal doesn't support 24-bit color as described in the Installation section of this README, or 24-bit color support is not always available everywhere you use your Vim configuration, colors will not look like they do in the preview image.

However, you can use the g:onedark_termcolors option to control onedark.vim's fallback colors in situations where 24-bit color terminal support is not available.

g:onedark_termcolors can be set to one of two values, 256 for 256-color mode (the default), or 16 for 16-color mode (which uses your terminal emulator's native 16 colors.)

When Vim/Neovim are configured to use 24-bit color, the g:onedark_termcolors option is ignored. However, g:onedark_termcolors can still coexist with 24-bit color configuration. For instance, when tmux 2.1 or earlier and/or older Vim/Neovim versions that don't support 24-bit color are used, the g:onedark_termcolors option will take effect.

  • 256-color mode is enabled by default with no additional configuration, but colors are less accurate since they are approximated using a 256-color palette. The background color will appear darker than in the preview image, and most other colors will appear brighter than in the preview image. If you don't want to change your terminal's color palette as described in the 16-color mode section below, and your terminal doesn't support 24-bit color, 256-color mode is your only option.

    Although 256-color mode is enabled by default (when not using 24-bit color as described above), you can explicitly enable it by adding the following line to your ~/.vimrc:

    let g:onedark_termcolors=256
  • 16-color mode is the preferred option, since its colors are more accurate than those of 256-color mode. However, you'll need to set your terminal emulator's color palette to this color scheme's custom 16-color palette, since 16-color mode will cause the color scheme to use your terminal emulator's native 16 colors. If you don't use the custom 16-color palette in your terminal emulator when 16-color mode is enabled, onedark.vim's colors will not display correctly in Vim.

    The canonical version of the 16-color palette is an Xresources file located in this repository at term/One Dark.Xresources. Color schemes for various terminal emulators are also provided in term/. (The iTerm2 color scheme works with iTerm2 versions 2.9.x and later.) You should be able to easily convert the Xresources color scheme for use with your terminal emulator of choice either by hand, or automatically by using termcolors.

    Assuming your terminal emulator is configured to use the custom 16-color palette as described above, add the following line to your ~/.vimrc to enable 16-color mode:

    let g:onedark_termcolors=16

Why do all comments look like they're highlighted?

Broken Italics

If all comments look like the one in the screenshot above, you have enabled italics in onedark.vim by setting g:onedark_terminal_italics=1 in your ~/.vimrc, but your terminal isn't displaying italics correctly. You can either remove the option or try to fix your terminal. If you're using iTerm2 on macOS, you might need to use a special TERMINFO to get italics working.

Why do colors look washed out when using iTerm2?

Make sure that in Preferences, Profiles -> [Active Profile] -> Colors -> Minimum Contrast is turned all the way down. See #145 for more information.

Miscellaneous

Customizing onedark.vim's look without forking the repository

onedark.vim exposes onedark#extend_highlight and onedark#set_highlight functions that you can call from within your ~/.vimrc in order to customize the look of onedark.vim.

onedark#extend_highlight

onedark#extend_highlight allows you to customize individual aspects of onedark.vim's existing highlight groups, overriding only the keys you provide. (To completely redefine/override an existing highlight group, see onedark#set_highlight below.)

onedark#extend_highlight's first argument should be the name of a highlight group, and its second argument should be partial style data.

Place the following lines before the colorscheme onedark line in your ~/.vimrc, then change the example overrides to suit your needs:

if (has("autocmd"))
  augroup colorextend
    autocmd!
    " Make `Function`s bold in GUI mode
    autocmd ColorScheme * call onedark#extend_highlight("Function", { "gui": "bold" })
    " Override the `Statement` foreground color in 256-color mode
    autocmd ColorScheme * call onedark#extend_highlight("Statement", { "fg": { "cterm": 128 } })
    " Override the `Identifier` background color in GUI mode
    autocmd ColorScheme * call onedark#extend_highlight("Identifier", { "bg": { "gui": "#333333" } })
  augroup END
endif

onedark#set_highlight

onedark#set_highlight allows you to completely redefine/override highlight groups of your choosing.

onedark#set_highlight's first argument should be the name of a highlight group, and its second argument should be complete style data.

For example, to remove the background color only when running in terminals (outside GUI mode and for use in transparent terminals,) place the following lines before the colorscheme onedark line in your ~/.vimrc:

" onedark.vim override: Don't set a background color when running in a terminal;
" just use the terminal's background color
" `gui` is the hex color code used in GUI mode/nvim true-color mode
" `cterm` is the color code used in 256-color mode
" `cterm16` is the color code used in 16-color mode
if (has("autocmd") && !has("gui_running"))
  augroup colorset
    autocmd!
    let s:white = { "gui": "#ABB2BF", "cterm": "145", "cterm16" : "7" }
    autocmd ColorScheme * call onedark#set_highlight("Normal", { "fg": s:white }) " `bg` will not be styled since there is no `bg` setting
  augroup END
endif

Global color overrides

You can override colors across all highlights by adding color definitions to the g:onedark_color_overrides dictionary in your ~/.vimrc like so:

let g:onedark_color_overrides = {
\ "background": {"gui": "#2F343F", "cterm": "235", "cterm16": "0" },
\ "purple": { "gui": "#C678DF", "cterm": "170", "cterm16": "5" }
\}

This also needs to be done before colorscheme onedark.

More examples of highlight group names and style data can be found in onedark.vim's source code (colors/onedark.vim inside this repository).

tmux theme

If you'd like a tmux theme that complements onedark.vim, @odedlaz has you covered.

Contributing

If you'd like to contribute to onedark.vim, check out the contribution guidelines.

Relatives of onedark.vim

Several other themes and projects have reused code and/or colors from this project, or were otherwise inspired by it.

If onedark.vim isn't meeting your needs, try one of its relatives!

Preview images

Preview images were taken using:

onedark.vim's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

onedark.vim's Issues

Tab highlighting

Is there anyway to highlight whatever tab is open within vim?

What it looks like now:
screenshot 2016-02-22 11 51 52

Ideally I could see something like this (with your color scheme ofc):
screenshot 2016-02-22 11 53 51

Not seeing true colors on tmux/nvim

Hi,

This my environment:

  • macOS sierra 10.12.1

  • iterm2 3.0.13 - with xterm-256color and onedark-256 itermcolor

  • tmux 2.3 (with true color, checked with "tmux info | grep Tc"

  • nvim 0.1.7

Here is ~/.vimrc (the part which is related to the colors):

set t_Co=256
let g:rehash256 = 1
let g:onedark_termcolors=256

set background=dark
colorscheme onedark

and in tmux I see those colors:
screen shot 2017-01-18 at 11 43 28 pm

Outside of tmux it works.

Is this tmux issue? if so what's the specific issue?

nerdtree colors

Hey again! Long time no see :)

So I use nerdtree, which colors directories blue and executables red. But not with onedark.

screen shot 2016-07-19 at 7 28 02 pm

Ideas?

airtheme into repo

Put airline theme into this repository, Vundle will install it automatically.

Hard to tell the difference in vimdiff

Hi Team:
I realy like onedark and it could be the best vim theme I have ever tried. I get some problems recently.

I use vimdiff to compare the staged/unstaged files, and it really pains a lot to tell the difference.
you may take a look into the screenshot attached. Can we somehow highlighting the difference?

screen shot 2016-09-30 at 18 32 03

Brownish background in vim in iTerm2

So I installed onedark for iTerm2 and Vim as well. But it doesn't look right when I am using Vim in iTerm2 or even system terminal. Though it looks fine in MacVim.

As you can see, theme looks great in MacVim, great in iTerm but not so when Vim is opened inside iTerm

screenshot

Can't get the right colors gnome-terminal Ubuntu 16.04

I'm using the standard gnome-terminal on Ubuntu 16.04 and unless I'm wrong, this should support the truecolor-mode. I applied the install instructions to my vimrc, here it is:

" All system-wide defaults are set in $VIMRUNTIME/debian.vim and sourced by
" the call to :runtime you can find below.  If you wish to change any of those
" settings, you should do it in this file (/etc/vim/vimrc), since debian.vim
" will be overwritten everytime an upgrade of the vim packages is performed.
" It is recommended to make changes after sourcing debian.vim since it alters
" the value of the 'compatible' option.

" This line should not be removed as it ensures that various options are
" properly set to work with the Vim-related packages available in Debian.
runtime! debian.vim

" Uncomment the next line to make Vim more Vi-compatible
" NOTE: debian.vim sets 'nocompatible'.  Setting 'compatible' changes numerous
" options, so any other options should be set AFTER setting 'compatible'.
"set compatible

" Vim5 and later versions support syntax highlighting. Uncommenting the next
" line enables syntax highlighting by default.
if has("syntax")
  syntax on
endif

" If using a dark background within the editing area and syntax highlighting
" turn on this option as well
"set background=dark

" Uncomment the following to have Vim jump to the last position when
" reopening a file
"if has("autocmd")
"  au BufReadPost * if line("'\"") > 1 && line("'\"") <= line("$") | exe "normal! g'\"" | endif
"endif

" Uncomment the following to have Vim load indentation rules and plugins
" according to the detected filetype.
"if has("autocmd")
"  filetype plugin indent on
"endif

" The following are commented out as they cause vim to behave a lot
" differently from regular Vi. They are highly recommended though.
"set showcmd		" Show (partial) command in status line.
"set showmatch		" Show matching brackets.
"set ignorecase		" Do case insensitive matching
"set smartcase		" Do smart case matching
"set incsearch		" Incremental search
"set autowrite		" Automatically save before commands like :next and :make
"set hidden		" Hide buffers when they are abandoned
"set mouse=a		" Enable mouse usage (all modes)

" Source a global configuration file if available
if filereadable("/etc/vim/vimrc.local")
  source /etc/vim/vimrc.local
endif

" Set ESC-key to jk
inoremap jk <ESC>

"remap leader key to Space
let mapleader ="\<Space>"

filetype plugin indent on

"Use 24-bit (true-color) mode in Vim/Neovim when outside tmux.
"If you're using tmux version 2.2 or later, you can remove the outermost $TMUX check and use tmux's 24-bit color support
"(see < http://sunaku.github.io/tmux-24bit-color.html#usage > for more information.)
if (empty($TMUX))
  if (has("nvim"))
    "For Neovim 0.1.3 and 0.1.4 < https://github.com/neovim/neovim/pull/2198 >
    let $NVIM_TUI_ENABLE_TRUE_COLOR=1
  endif
  "For Neovim > 0.1.5 and Vim > patch 7.4.1799 < https://github.com/vim/vim/commit/61be73bb0f965a895bfb064ea3e55476ac175162 >
  "Based on Vim patch 7.4.1770 (`guicolors` option) < https://github.com/vim/vim/commit/8a633e3427b47286869aa4b96f2bfc1fe65b25cd >
  " < https://github.com/neovim/neovim/wiki/Following-HEAD#20160511 >
  if (has("termguicolors"))
    set termguicolors
  endif
endif

set encoding=utf-8
execute pathogen#infect()

syntax on
colorscheme onedark
set background=dark

I also copied onedark.vim into the colors folders as instructed. Still, the colors are all wrong compared to atom:

image

Cant highlight ColorColumn

Hi,

Beautiful theme.
I am using it with neovim inside tmux. I set my colorcolumn as well. But I cant see it highlight-ed to cursor_grey. hitest doesnt show any color for it as well.
I have tried using a different color hi ColorColumn ctermbg=black for example but it doesnt seem to work.

Any pointers?

Git commit comment highlighting

I noticed after 5640329 that my Git commit coloring appeared a bit off. In particular, comments and regular text are the same color. While I primarily use neovim + iterm2 (and the associated onedark themes), I notice the same issue with regular vim and a minimal vimrc. For example:

screen shot 2016-02-16 at 10 22 27 pm

However, tweaking the Git highlighting to use s:comment_grey where previously no color was specified, such as:

call s:h("gitcommitComment", {"fg": s:comment_grey })
call s:h("gitcommitUnmerged", { "fg": s:green })
call s:h("gitcommitOnBranch", { "fg": s:comment_grey })
call s:h("gitcommitBranch", { "fg": s:purple })
call s:h("gitcommitDiscardedType", { "fg": s:red })
call s:h("gitcommitSelectedType", { "fg": s:green })
call s:h("gitcommitHeader", { "fg": s:comment_grey })
call s:h("gitcommitUntrackedFile", { "fg": s:cyan })
call s:h("gitcommitDiscardedFile", { "fg": s:red })
call s:h("gitcommitSelectedFile", { "fg": s:green })
call s:h("gitcommitUnmergedFile", { "fg": s:yellow })
call s:h("gitcommitFile", { "fg": s:comment_grey })

results in something more like what I would expect:
screen shot 2016-02-16 at 10 28 24 pm

I'm not entirely sure what colors were intended for git commits, or how the above modification affects other configurations, or whether this is an issue with the color scheme or simply my personal configs.

Highlight Group 'IncSearch' interferes with SearchParty

Hi @joshdick ,

I use SearchParty and one of its features is to use IncSearch and highlight the occurrence under the cursor using the inverted colorscheme of the Syntax group the word belongs to.

This gets overridden when hl-IncSearch is explicitly defined, as is the case here. If you dont see this as a deal breaker, I would request removing (or temporarily commenting it out).

Alternatively, you could use a flag for the user to set/reset this hl group.

Cheers

MatchParen as bold ?

When using Rainbow parens, the matching paren is hard to see because of color reuse. How do I set it as Bold ?

Error when starting vim

I'm getting the following error when starting Macvim and using this color scheme.
screen shot 2015-11-25 at 9 36 10 am

I get the same error when trying use it in Neovim (just different line numbers)
screen shot 2015-11-25 at 9 35 48 am

I do not get these errors with other color schemes.

It seems to load fine after I hit enter, it's just annoying to get them every time I open vim.

incsearch doesn't highlight

When using onedark, the incremental search results aren't highlighted, making it impossible to use the incsearch feature.

Steps to reproduce:

  1. Edit a file with some text in it.
  2. :set incsearch
  3. / and start typing something in the file.

matching ( ){ } [ ] not working

Hi.

Thanks for your work. I started using it from neovim in terminal.

The only thing that I've trouble with is missing highlightning matching parens, square bracket etc.
If I change the colorscheme to another schema - its starts working again..

I have installed the following syntax plugins, it has no effect toggling rainbows_parentheses

Plug 'guns/vim-clojure-highlight', { 'for': 'clojure' }
Plug 'guns/vim-clojure-static', { 'for': 'clojure' }
Plug 'junegunn/rainbow_parentheses.vim'

Cheers

Flow syntax highlight

First of all I want to say that this theme is great and my favourite, really good work. ๐Ÿ‘
Are you going to support flow syntax? It would be really nice. This is how it looks now:

Colors don't appear right inside tmux

I previously thought this may be happening because my tmux didn't have TrueColor support enabled properly. I resolved my tmux TrueColor issue tmux/tmux#696, but my vim colors still do not match:

Relevant vimrc

if &term =~ '256color'
    " disable background color erase
    set t_ut=
endif

" enable 24 bit color support if supported
if (empty($TMUX) && has("termguicolors"))
    set termguicolors
endif

let g:onedark_termcolors=256
let g:onedark_terminal_italics=1

syntax on
set t_Co=256                  " Explicitly tell vim that the terminal supports 256 colors
set background=dark           " Enable dark background
colorscheme onedark           " Set the colorscheme

NeoVim Version

โ‡จ nvim --version
NVIM 0.1.7
Build type: RelWithDebInfo
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20161130-73384-ctpyvy/neovim-0.1.7/build/config -I/tmp/neovim-20161130-73384-ctpyvy/neovim-0.1.7/src -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/usr/include -I/tmp/neovim-20161130-73384-ctpyvy/neovim-0.1.7/build/src/nvim/auto -I/tmp/neovim-20161130-73384-ctpyvy/neovim-0.1.7/build/include
Compiled by [email protected]

Optional features included (+) or not (-): +acl   +iconv    -jemalloc +tui
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/0.1.7/share/nvim"

Screenshot

Left: iTerm > tmux > nvim
Right: iTerm > nvim

Noticeable Problems:

  • Background color doesn't match. Background color of nvim running within tmux has a darker tone
  • Normally all colors look more contrasted (colors on left eg: pink, red, etc. are darker inside tmux

screen shot 2016-12-21 at 6 06 12 pm 3

Make autocomplete more obvious

I run into this problem a few times:

screen shot 2016-05-11 at 23 36 41

It's hard to tell at first glance where my code and the autocomplete end. Atom gets round this with a drop shadow. Maybe a slightly lighter shade could be used on the autocomplete background?

Italic HTML attribute names

Would you consider adding an option for italic HTML attribute names? I tried adding highlight htmlArg cterm=italic to my VIMRC but it didn't work.

It don't seems to work in iTerm2

I installed the scheme with iTerm2 and MacVim. In GVim it works well. However, it don't work in iTerm2 as it should.
Here's the relevant code in ~/.vimrc

" Basics
set nocompatible " get out of horrible vi-compatible mode [Vundle required]
filetype off " [Vundle required]
set encoding=utf-8

" Font
set guifont=PragmataPro\ for\ Powerline:h16

" Scheme
syntax on " syntax highlighting on
set t_Co=256
set background=dark
colorscheme onedark
let g:onedark_termcolors=256
let g:onedark_terminal_italics=1

Onedark colorscheme nolonger working

Hey man.

I wondered if you could help me with this. Suddenly, my onedark colorscheme is no longer getting loaded. I can load it manually with :colorscheme onedark, but only after I load something different, like monokai.

I have no idea why this started to happen all of a sudden.

Here is my ./vimrc => https://github.com/Skarlso/devops/blob/master/vimrc

I switched it to syntax on and after that colorscheme, but it didn't work either.

Here is an output of :scriptnames:

  1: /usr/share/vim/vimrc
  2: /usr/share/vim/vim74/debian.vim
  3: /usr/share/vim/vim74/syntax/syntax.vim
  4: /usr/share/vim/vim74/syntax/synload.vim
  5: /usr/share/vim/vim74/syntax/syncolor.vim
  6: /usr/share/vim/vim74/filetype.vim
  7: ~/.vimrc
  8: /usr/share/vim/vim74/ftoff.vim
  9: ~/.vim/bundle/Vundle.vim/autoload/vundle.vim
 10: ~/.vim/bundle/Vundle.vim/autoload/vundle/config.vim
 11: ~/.vim/bundle/vim-go/ftdetect/gofiletype.vim
 12: ~/.vim/bundle/vim-ps1/ftdetect/ps1.vim
 13: ~/.vim/bundle/vim-ps1/ftdetect/ps1xml.vim
 14: ~/.vim/bundle/Dockerfile.vim/ftdetect/Dockerfile.vim
 15: ~/.vim/bundle/plaintasks.vim/ftdetect/plaintasks.vim
 16: /usr/share/vim/vim74/ftplugin.vim
 17: /usr/share/vim/vim74/indent.vim
 18: ~/.vim/colors/monokai.vim
 19: /usr/share/vim/vim74/syntax/nosyntax.vim
 20: ~/.vim/bundle/nerdtree/plugin/NERD_tree.vim
 21: ~/.vim/bundle/nerdtree/autoload/nerdtree.vim
 22: ~/.vim/bundle/nerdtree/lib/nerdtree/path.vim
 23: ~/.vim/bundle/nerdtree/lib/nerdtree/menu_controller.vim
 24: ~/.vim/bundle/nerdtree/lib/nerdtree/menu_item.vim
 25: ~/.vim/bundle/nerdtree/lib/nerdtree/key_map.vim
 26: ~/.vim/bundle/nerdtree/lib/nerdtree/bookmark.vim
 27: ~/.vim/bundle/nerdtree/lib/nerdtree/tree_file_node.vim
 28: ~/.vim/bundle/nerdtree/lib/nerdtree/tree_dir_node.vim
 29: ~/.vim/bundle/nerdtree/lib/nerdtree/opener.vim
 30: ~/.vim/bundle/nerdtree/lib/nerdtree/creator.vim
 31: ~/.vim/bundle/nerdtree/lib/nerdtree/flag_set.vim
 32: ~/.vim/bundle/nerdtree/lib/nerdtree/nerdtree.vim
 33: ~/.vim/bundle/nerdtree/lib/nerdtree/ui.vim
 34: ~/.vim/bundle/nerdtree/lib/nerdtree/event.vim
 35: ~/.vim/bundle/nerdtree/lib/nerdtree/notifier.vim
 36: ~/.vim/bundle/nerdtree/autoload/nerdtree/ui_glue.vim
 37: ~/.vim/bundle/nerdtree/nerdtree_plugin/exec_menuitem.vim
 38: ~/.vim/bundle/nerdtree/nerdtree_plugin/fs_menu.vim
 39: ~/.vim/bundle/vim-nerdtree-tabs/nerdtree_plugin/vim-nerdtree-tabs.vim
 40: ~/.vim/bundle/vim-fugitive/plugin/fugitive.vim
 41: ~/.vim/bundle/vim-go/plugin/go.vim
 42: ~/.vim/bundle/YouCompleteMe/plugin/youcompleteme.vim
 43: ~/.vim/bundle/syntastic/plugin/syntastic/autoloclist.vim
 44: ~/.vim/bundle/syntastic/plugin/syntastic/balloons.vim
 45: ~/.vim/bundle/syntastic/plugin/syntastic/checker.vim
 46: ~/.vim/bundle/syntastic/plugin/syntastic/cursor.vim
 47: ~/.vim/bundle/syntastic/plugin/syntastic/highlighting.vim
 48: ~/.vim/bundle/syntastic/plugin/syntastic/loclist.vim
 49: ~/.vim/bundle/syntastic/plugin/syntastic/modemap.vim
 50: ~/.vim/bundle/syntastic/plugin/syntastic/notifiers.vim
 51: ~/.vim/bundle/syntastic/plugin/syntastic/registry.vim
 52: ~/.vim/bundle/syntastic/plugin/syntastic/signs.vim
 53: ~/.vim/bundle/syntastic/plugin/syntastic.vim
 54: ~/.vim/bundle/syntastic/autoload/syntastic/log.vim
 55: ~/.vim/bundle/syntastic/autoload/syntastic/util.vim
 56: ~/.vim/bundle/vim-airline/plugin/airline.vim
 57: ~/.vim/bundle/vim-airline/autoload/airline.vim
 58: ~/.vim/bundle/vim-airline/autoload/airline/init.vim
 59: ~/.vim/bundle/vim-airline/autoload/airline/parts.vim
 60: ~/.vim/bundle/svndiff/plugin/svndiff.vim
 61: /usr/share/vim/vim74/plugin/getscriptPlugin.vim
 62: /usr/share/vim/vim74/plugin/gzip.vim
 63: /usr/share/vim/vim74/plugin/matchparen.vim
 64: /usr/share/vim/vim74/plugin/netrwPlugin.vim
 65: /usr/share/vim/vim74/plugin/rrhelper.vim
 66: /usr/share/vim/vim74/plugin/spellfile.vim
 67: /usr/share/vim/vim74/plugin/tarPlugin.vim
 68: /usr/share/vim/vim74/plugin/tohtml.vim
 69: /usr/share/vim/vim74/plugin/vimballPlugin.vim
 70: /usr/share/vim/vim74/plugin/zipPlugin.vim
 71: ~/.vim/bundle/vim-airline/autoload/airline/extensions.vim
 72: ~/.vim/bundle/vim-airline/autoload/airline/extensions/quickfix.vim
 73: ~/.vim/bundle/vim-airline/autoload/airline/extensions/netrw.vim
 74: ~/.vim/bundle/vim-airline/autoload/airline/extensions/branch.vim
 75: ~/.vim/bundle/vim-airline/autoload/airline/extensions/syntastic.vim
 76: ~/.vim/bundle/vim-airline/autoload/airline/extensions/whitespace.vim
 77: ~/.vim/bundle/vim-airline/autoload/airline/extensions/wordcount.vim
 78: ~/.vim/bundle/vim-airline/autoload/airline/section.vim
 79: ~/.vim/bundle/vim-airline/autoload/airline/highlighter.vim
 80: ~/.vim/bundle/vim-airline/autoload/airline/themes/molokai.vim
 81: ~/.vim/bundle/vim-airline/autoload/airline/themes.vim
 82: ~/.vim/bundle/vim-airline/autoload/airline/util.vim
 83: ~/.vim/bundle/vim-airline/autoload/airline/builder.vim
 84: ~/.vim/bundle/vim-airline/autoload/airline/extensions/default.vim
 85: ~/.vim/bundle/nerdtree/syntax/nerdtree.vim
 86: ~/.vim/bundle/YouCompleteMe/autoload/youcompleteme.vim
 87: ~/.vim/bundle/vim-airline/autoload/airline/deprecation.vim

Thanks for any insight you could provide!!

Consider adding an issue template

There are a lot of issues opened around incorrect colours that can usually be answered in the README. Should we consider adding a template to direct users there in case they missed it?

We could also request the relevant vimrc settings

Disabling italics

How do I disable italic comment
I tried doing

let g:onedark_terminal_italics=0
colorscheme onedark

which is not working.
Using it with neovim.

Italics supports in iterm2 and vim

It seems like only let g:onedark_terminal_italics=1 before colorscheme onedark could not make it become Italics. I also added below gists in .vimrc and turn on Iterm2 italics supports using this gists.

let &t_ZH="\e[3m"
let &t_ZR="\e[23m"

My vim configuration lists here.

Missing colors in some languages

I've been using solarized-dark for a while, but I really like the colors in this theme. One problem I have though is that some languages have much less color (especially for symbols) using onedark instead of solarized. I'll just post some screenshots. The two main ones for me are the arrows (->) and symbols (<<<, ., etc) in PureScript and the symbols in JavaScript (const, =, &&, etc).

(FWIW, I find Atom's PureScript highlighting to be a bit odd (good for types, bad for code and imports) and way too colorful for JavaScript)

Solarized, PureScript:
screen shot 2016-01-06 at 11 12 01 am

Onedark, PureScript:
screen shot 2016-01-06 at 11 12 49 am

Solarized, JavaScript:
screen shot 2016-01-06 at 11 14 09 am

Onedark, JavaScript:
screen shot 2016-01-06 at 11 15 00 am

Atom, PureScript:
screen shot 2016-01-06 at 11 17 22 am

Atom, JavaScript:
screen shot 2016-01-06 at 11 18 24 am

And thanks for working on this theme, it's the best I've tried so far!

background color over ssh in HyperTerm

Local

  • VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jun 16 2016 14:20:57)
  • echo $TERM; // xterm-256color

screen shot 2016-07-19 at 5 22 23 pm

SSH

  • VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jul 24 2015 02:23:23)
  • echo $TERM; // xterm-256color

screen shot 2016-07-19 at 5 22 25 pm

It seems like only the background color is slightly different over ssh then in my local vim..
any ideas what might be causing this?

Signify colours

Just wondering why these are all set to grey.

Using the GitGutter colours looks pretty good.

screen shot 2016-05-10 at 15 51 26

Issues with color

Thanks a lot for this plugin. I can now switch back to vim ๐Ÿ˜„

I've just set it up and have been having some odd inconsistencies.

  • Colors in lightline (Terminal Vim)

    Mine looks like the above but I don't think this is what it should look like

  • Colors in lightline (MacVim)

    I have the same settings in my .gvimrc but the default solarised theme doesn't seem to want to be changed from solarised.

  • Nerdtree colors
    Yet another color issue I cant figure out. I woul dhave expected it to match ba78df2

Colors vary between Macvim and vim + iterm

Seems like the vim theme works well using mvim, however, the colors seem off when using vim 7.4 within iterm and terminal app. Any thoughts? Screen capture depicts vim+iTerm on left and mvim on right.

screen shot 2016-04-12 at 6 27 55 am

Neovim colors off inside tmux

screen shot 2016-06-05 at 1 44 58 am

The tmux block in the README doesn't help things. Using minimal configs for both.

$ brew info tmux
tmux: stable 2.2 (bottled), HEAD
$ vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled May 27 2016 20:19:09)

Light background

I know that this repo is called oneDARK... but could you provide an option for a light background?

vim-airline issue: Syntastic Errors not showing up when using onedark colorscheme

When I use the onedark airline theme, I don't see the expected [Syntax: line:xx in the status line for syntax errors. Below is a minimal vimrc (using Vim 8.0 with packages to install both onedark and syntastic at startup) that shows the issue. Comment out colorscheme onedark to default to the current theme and show the syntastic error part of the status line again.

" onedark
if (has("termguicolors"))
  set termguicolors
endif
colorscheme onedark

" syntastic
let g:syntastic_always_populate_loc_list = 1
let g:syntastic_check_on_open = 1
let g:syntastic_check_on_wq = 0

Screenshots are taken while looking at the same file with one syntastic error.

screen shot 2016-12-21 at 5 10 43 pm

screen shot 2016-12-21 at 5 09 55 pm

Thanks for this scheme, I'm a big fan! Just curious if I'm missing something obvious.

tmux with vim highlight color not working

hi

I work with vim.

so far, I use terminal.

but I use tmux.

one dark syntax high light is not working.

why?

.vimrc

let g:onedark_termcolors=16

screenshot with terminal

https://gyazo.com/24aae7222776162057dbf8c2377dc578

screenshot with tmux

https://gyazo.com/d14104eb81f67abfd3e125bcfce8dca3

Change VertSplit color

Hi,

I really like your theme! Great job! One tiny nitpick I have, however, is the way the separator for vertical splits is colored. I find the black a bit too strong. I played around a bit with the colors and found that using s:cursor_grey instead of s:vertsplit looks much less obtrusive. I've attached a screenshot. Is this something you would be willing to change?

screen shot 2016-07-31 at 15 49 02

PowerShell syntax highlighting is wacked

Hi!

First off, awesome theme, nicely done!

Second, once I enable this, sadly, my PowerShell syntax highlighting is completely gone. It just displays it as plain text. Other custom themes are also gone, like Dockerfile and Go. I suspect because on the first line, you are resetting syntax.

Can we do something about that? Can I somehow override for certain filetypes? What's the best way of solving this?

Cheers,
Gergely.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.