Hi,
I'm having this problem in ruby where all function names and keywords are all the same color. I think the function names ought to be brighter. I'm using latest kitty terminal with neovim.

Not sure whether it's a bug in nvim or something with the theme, but current line is not highlighted at all.

It's the colorscheme we set that defines us. (Batman)

Where does he say that? I need proof.

I am using NVIM LSP with LSPSAGA and here is how the errors and warning are displayed with gotham enabled.

Here is how they are displayed in Nord color scheme.

I absolutely love vim-gotham, and wanted to ask if there is any way to add little color tints to the error, warning and info icons?

The only blackspot for me with this theme:

Note that it is almost impossible to actually read the matched term on the first line (the term is Base and it's in the blackhole between extends and TimeSeriesSpec). This is a screenshot taken from within unite.vim's grep source, but the same applies to any other searches. It's enough that I am starting to think about departing from the one true batman path, and going with other themes. Thoughts?

I get following pic by running :verbose hi command. Error seems wrong for gotham theme.

...and WarningMsg:

I fixed the problem temporarily by overriding these 2 in my init.vim file:

Should I send a PR?

From: 4507f9d
Version: VIM - Vi IMproved 8.0.297 (on OS X from here), VIM - Vi IMproved 7.3 (on OS X default CUI)

Problem

Launch Vim with vim -u NORC -N --cmd "set ls=2" --cmd "set runtimepath+=~/.vim/bundle/vim-airline,~/.vim/bundle/vim-gotham" --cmd "colorscheme gotham256" (This only load airline and gotham) AirlineThene does not applied automatic on launch. Before 4507f9d, it applied.

Erase near L88-99 in autoload/airline/themes/gotham256.vim, it does not occur. But I don't know how to fix these lines.

This especially shows in the Airline theme when going in insert mode.
Compared with the color hue's used in other parts of the UI and compared to the colors for normal and visual mode (bright yellow, and green respectively) the yellow color just seems off, lowering the saturation of the color helps but doesn't solve it completely.

below two screenshots that illustrate this, side note: I use the Gotham ergo theme for Iterm.

the insert mode yellow:

The profile overview of the Gotham ergo theme, note that the yellow color is the same in all iterm colors chemes:

I'm curious as to what your opinion is on the mather and how this yellow color came about.

While the theme itself is marvelous, diffs are extremely confusing with gotham.

Using more intuitive backgrounds would help here, i.e. red -> deletion, green -> addition, else -> changed.

This is more of a request than a bug. I love this theme, but.. I love the consistency of base16. Can you guys port this over to base16-shell? This would require base16-shell, base16-vim, vim-airline-themes changes, if you do.

I'm using the gotham theme with Airline. When I open a new split for a terminal window using the :term command (added in vim 8.1), I get the following error:

This does not happen with any other color themes.

It happened.

I've tried matching the colors from your screenshot as closely as possible. It would be very useful if you could provide me extra screenshots and point out obvious mistakes. For instance I'm less sure about comments having almost the same color as the Ruby keywords. Once all of them are fixed, I'll proceed theming more packages and will add the mappings for the terminal version.

Hi guys, I've applied the gotham colorscheme but for some reason it looks with a grey background and orange keywords along with some other pale colors. That's not how it is supposed to be, when I changed it to the 256 version it looks great, so I don't know what makes the normal version looks like that.

I've download the last version from the site and manually putted in ~/.vim/colors folder.
I see this problem only when I use iTerm2 as the terminal. In the default terminal looks fine.

pd: Even when the 256 versions looks something better, there are a lot of difference to what you showed in the screenshot. That screenshot looks awesome, and is nowhere near it how it looks my terminal. Is it that normal? do I need to change something else?

More tests (normal version not 256):
On default terminal looks dark, but lot of colors are not correct.
On Iterm2 looks bad, greyed pale colors.
On MacVim looks awesome, how it should be on on my terminal.

are you planning to add support for neovim and other newer plugins?

I love this color scheme so much! I'm really curious, how did you pick the color palette/scheme? What should one do if they wanted to make their own color palette/scheme? How should one start?

macOS, Term.app.

This is the most awesome theme out there, but for some reason, the functions became this yucky color:

Why did it change, is it possible to go back to a little brighter color?

Changes introduced here: #26

I feel that the text on the buffer name (tab file name) is too dark.

(with transparency)

Screenshot from the README:

I feel the last screenshot shows better colors for filenames. Is this something that anyone else is experiencing?

I've been having a hard time switching through tabs since my brain takes a bit more to try and identify the filename, before it was very quick, now my eyes dance a bit around the tab to read the name.

thanks!

I use iTerm2 + Gotham.itermcolors + gotham.vim and trying to C-x C-l or C-x C-o or just neocomplete/YCM menu invocation:

Vim 7.4.865

ITerm2 version

my zshrc

vim version

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled May 21 2014 20:02:26)
MacOS X (unix) version
Included patches: 1-258
Compiled by Homebrew
Huge version with MacVim GUI.  Features included (+) or not (-):
+acl             +file_in_path    +mouse_sgr       +tag_binary
+arabic          +find_in_path    -mouse_sysmouse  +tag_old_static
+autocmd         +float           +mouse_urxvt     -tag_any_white
+balloon_eval    +folding         +mouse_xterm     +tcl
+browse          -footer          +multi_byte      +terminfo
++builtin_terms  +fork()          +multi_lang      +termresponse
+byte_offset     +fullscreen      -mzscheme        +textobjects
+cindent         -gettext         +netbeans_intg   +title
+clientserver    -hangul_input    +odbeditor       +toolbar
+clipboard       +iconv           +path_extra      +transparency
+cmdline_compl   +insert_expand   +perl            +user_commands
+cmdline_hist    +jumplist        +persistent_undo +vertsplit
+cmdline_info    +keymap          +postscript      +virtualedit
+comments        +langmap         +printer         +visual
+conceal         +libcall         +profile         +visualextra
+cryptv          +linebreak       +python          +viminfo
+cscope          +lispindent      -python3         +vreplace
+cursorbind      +listcmds        +quickfix        +wildignore
+cursorshape     +localmap        +reltime         +wildmenu
+dialog_con_gui  -lua             +rightleft       +windows
+diff            +menu            +ruby            +writebackup
+digraphs        +mksession       +scrollbind      -X11
+dnd             +modify_fname    +signs           -xfontset
-ebcdic          +mouse           +smartindent     +xim
+emacs_tags      +mouseshape      -sniff           -xsmp
+eval            +mouse_dec       +startuptime     -xterm_clipboard
+ex_extra        -mouse_gpm       +statusline      -xterm_save
+extra_search    -mouse_jsbterm   -sun_workshop    -xpm
+farsi           +mouse_netterm   +syntax
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/Applications/MacVim.app/Contents/Resources/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_MACVIM -Wall -Wno-unknown-pragmas -pipe  -DMACOS_X_UNIX  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1     -I/System/Library/Frameworks/Tcl.framework/Headers  -D_REENTRANT=1  -D_THREAD_SAFE=1  -D_DARWIN_C_SOURCE=1
Linking: clang   -L. -L/usr/local/lib -L. -L/usr/local/lib -L/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config -F/System/Library/Frameworks -L/usr/local/lib -o Vim -framework Cocoa -framework Carbon       -lm  -lncurses -liconv -framework Cocoa   -fstack-protector -L/usr/local/lib  -L/System/Library/Perl/5.16/darwin-thread-multi-2level/CORE -lperl -framework Python  -F/System/Library/Frameworks -framework Tcl -framework CoreFoundation -framework Ruby
--------------------------------------------------------------------------------

my vimrc

Problem

Install scheme from Vundle (before that was seul256 color scheme) and mu vim like as:

But when I open macvim scheme work correct

I upset 😭

P.S.: I find tread in reddit and I use seoul256-iTerm2 colors in terminal

I get the following error when adding colorscheme gotham256 to my .vimrc:

Error detected while processing /usr/share/vim/vim74/syntax/synload.vim:
line 19:
E185: Cannot find color scheme 'gotham-256'

I think the problem stems from this line in colors/gotham256.vim:

let g:colors_name = 'gotham-256'

This makes vim expect gotham-256.vim when it in fact wants gotham256.vim. Switching the line to:

let g:colors_name = 'gotham256'

works correctly.

When not using airline, the statusline's content of inactive window can not be seen.

Current images don't show up anymore.

But you can recover them here:

• https://web.archive.org/web/20210123055902/https://camo.githubusercontent.com/8fb9352c94a9e79a651590014ce2edb7a7f490b273cf16480e56e4f8b0d7e17d/687474703a2f2f692e696d6775722e636f6d2f46444c457a48432e706e67

• https://web.archive.org/web/20210123055902/https://camo.githubusercontent.com/c6798129e9cadb8f30e15d4214e9e40fd224f462edf229114fb596ad473529f2/687474703a2f2f692e696d6775722e636f6d2f4e66527548464e2e706e67

Hi!

I use a transparent term , so in my .vimrc I have the following set

hi Normal             ctermbg=NONE
hi Statement          ctermbg=NONE
hi Title              ctermbg=NONE
hi Todo               ctermbg=NONE
hi Underlined         ctermbg=NONE
hi ErrorMsg           ctermbg=NONE
hi LineNr             ctermbg=NONE

This pretty much works as intended apart from in the gotham theme when I have a split window I end up with some odd red artifacts around the filetype of the unselected split. I have no idea why these appear. Any ideas?

In this case it is the left pane that is unselected.

EDIT: Just noticed that if I source my .vimrc the red bits disappear, but as soon as I switch splits, they return.

As title. While I haven't tested it. I think the problem is that the support of nvim-treesitter/nvim-treesitter is needed.

update: OK it doesn't work:

gotham256 not autoloaded on startup, and when force replacing airline theme with AirlineTheme gotham256 the following errors appear:

Any help would be appreciated!
thanks

From :help group-name

Function       function name (also: methods for classes)

Many themes highlight function names differently than default color, making them more visible. Currently vim-gotham doesn't do it because Function definition is missing.

See example with Rust syntax highlighting (note that fn which is a keyword and main which is a function name are the same color here which doesn't look so well):

Example of how it can look better:

Sample definition for the color and group:

let s:colors.sea   = { 'gui': '#4d618e', 'cterm': 4  }

" Function.
call s:Col('Function', 'sea', s:background)

I submited my current configuration showcasing my current customized Tmux statusline together with the Gotham colorschemes on the unix porn subredit !!

I hope it helps more people find this awesome colorscheme.

The cursor color and the text as parameter (in Js function for example) being of the same color, we can't see what is behind:

Could something be done about that?

That's a weird behavior. I hope i can explain it clearly.

When the cursor goes over a bracket character the character becomes orange with dark background, and the matching character becomes dark with orange background. It make it looks like the cursor have jumped to the matching character. It's very disorienting.

Maybe some screenshots will help.

Something ain't right with the way colors are rendered when neovim is using termguicolors and is running inside a tmux session:

Tmux session + neovim + termguicolors:

Neovim + termguicolors:

I'm not really sure what is causing the unexpected behaviour.
term is correctly set to screen-256color
termguicolors is enabled in both instances

When I disable termguicolors whilst in tmux then the colors do render better but termguicolors should work in tmux sessions as I can successfully use other colorschemes that way.

Hello, I've considered porting your theme to Emacs as an alternative to Solarized Dark, but before I'll do that I'd like to ask whether there will be extra color shades to the already existing colors, such as a darker and lighter cyan. If these are available, colored backgrounds that are different from the main shades are possible and can be used for things like completion popups:

As a result, it's a bit confusing: non-printed symbols are mixed with comments since comments too use base4 colour. Even base3 may be a bit too bright, but is still much better.

diff --git a/colors/gotham.vim b/colors/gotham.vim
index 82ba3de..093b26a 100644
--- a/colors/gotham.vim
+++ b/colors/gotham.vim
@@ -135,7 +135,7 @@ call s:Col('Type', 'orange')
 call s:Col('PreProc', 'red')

 " Tildes on the bottom of the page.
-call s:Col('NonText', 'base4')
+call s:Col('NonText', 'base3')

 " Concealed stuff.
 call s:Col('Conceal', 'cyan', s:background)
@@ -151,7 +151,7 @@ call s:Col('StatusLineNC', 'base4', 'base2')
 call s:Col('MatchParen', 'base1', 'orange')

 " Special keys, e.g. some of the chars in 'listchars'. See ':h listchars'.
-call s:Col('SpecialKey', 'base4')
+call s:Col('SpecialKey', 'base3')

 " Folds.
 call s:Col('Folded', 'base6', 'blue')

(EDIT: NonText should be edited as well as SpecialKey.)

I'm new to vim (and I use neovim) so maybe I did some stupid mistake and can't find it.
Here is my init.vim

set nocompatible

let $PATH = $PATH . ':' . expand("~/.local/bin") . ':' . expand("~/.composer/vendor/bin")

call plug#begin('~/@stuff/vim/nvim_my/plugged')

Plug 'scrooloose/nerdtree'
Plug 'vim-airline/vim-airline'

" ======== THEMES =========
" Plug 'rakr/vim-one'
Plug 'whatyouhide/vim-gotham'

call plug#end()

colorscheme gotham

And here is how the theme looks like:

Why does it look white?