Vim Colors
vimcolors.com
vimcolors.com
import lang.native.api.Something;
import third.party.api.Else;
...and syntax file goes to colorize Something, but Else is perceived as common text.I'm aware of limitations of vim, being text editor and not an IDE, but I'd rather syntax file to ignore the native API then to have me draw visual distinction between native and third-party classes when, effectively, I couldn't care less. The dissimilarity is just visual noise to me. :/
You can also quite easily customise syntax highlighting by placing your own additional syntax file in .vim/after/syntax for a language. I use this to add some more custom keywords. You could quite easily add highlight support for ".Else" in an after/syntax file.
And just to make sure, we agree that adding a feature like AST based highlighting wouldn't make an editor an IDE, right?
Are you using Reagent?
Especially when you switch from C-style languages to assembly, for example. Or to line-break sensitive formats like Python or YAML. Or markdown.
I love the Tomorrow-Night theme:
Vim: http://i.imgur.com/HBaCTAu.png
Zsh: https://github.com/sindresorhus/pure
On Github: https://github.com/chriskempson/tomorrow-theme/blob/master/v...
What is the use case for this that tmux/screen does not solve?
It appears I'm not the only one:
It's a similar feeling to when I haven't saved my editing in the last minute. :)
http://vimcolors.com/?utf8=✓&order=relevance&query=monochrom...
(d) -> "id-#{d[@id]}"
In my default color scheme, the #{} (string interpolation), @ (this pointer), and () (function parameter delimiter) are muted, since they're syntactically critical but not helpful to my understanding.The "id-" is more subtle than code but more visible than the muted syntax, because I only sometimes care about the string literal, and the array indexer [] is about the same.
The identifiers d and id are the regular typeface, since those are the code items.
The -> which creates a closure is brightest, because creating a closure is a relatively heavy operation and it's useful to be able to pick them out at a glance.
I understand that you CAN read it without highlighting, but the signal-to-noise ratio is much worse. In particular, the hash mark and atpersand stand out much too prominently.
The linked article is concerned about breaking up the "natural flow of the text", but I think that misses a critical observation. While prose text flows from left to right, line by line, that's not how code flows. Code's flow is in its structure.
> nmap <F11> :if exists("syntax_on") \| syntax off \| else \| syntax enable \| endif \|<newline><newline>
that makes F11 a toggle-highlighting button. Sometimes, highlighting helps spotting syntax errors.
Other than that, setting the "xterm*termName" X resource property to "xterm-256color" makes colors in vim much less distracting.
I've been wanting live-filter for a while but decided to launch with basic filtering.
Once I'm happy with core features I'll start looking at stuff like rating, favouriting, etc.
(I meant to post this comment earlier but it was throttling me.)
Solarized is too low-contrast for me, so I have hacked-on support for hybrid (solarized syntaxes + tommorow color codes), but it's not really uniform. And, imho, well-balanced contrast is the most important thing.
Non-exhaustive list of applications that I'd like to see supported - vim, emacs, tmux, weechat, vifm, newsbeuter, taskwarrior, mutt...
There is a related project called Base16-Builder: https://github.com/chriskempson/base16-builder
With Base16-Builder you can make a Yaml file of colours and it will build profiles for a zillion apps. It's pretty easy to hack to build other profiles as you just need to make an erb.
Base16 is organized in pretty much the same way as Solarized colours, so if you have gotten used to Solarized and just want to adjust the colours to something easier to see (I suffer from the same problem you do), then I think it is the way to go.
I hesitate to mention this because it isn't quite ready yet, but where I work we do a lot of remote pair programming over tmux. The problem is that everybody has their own idea of what colours look good. My buddy and I made a vim colorscheme that looks reasonable with many different palettes, called agnostic: https://github.com/ygt-mikekchar/agnostic
So if you ever need to pair program over tmux and one person wants a light background, but another person wants a dark backgroun, you can do it it. If you do that kind of thing a lot, then I recommend working with agnostic. Otherwise I think Base16 is probably the way to go.
Thank you!
https://github.com/noahfrederick/vim-noctu
It takes colours from your .Xdefaults/.Xresources, and all terminal apps just use your configured scheme.
See also: http://www.xcolors.net/
Then when I go inside/outside again I have to switch it all back. Quite a hassle. Has anyone found any trick to automate this? For starters I wouldn't know how to change the colorscheme of all my Vim sessions. Can you send a signal to your Vim sessions maybe? Then changing the terminal colorscheme is of course dependent on the terminal app you're using.
The solarized vim plugin even has a key binding to do this.
Or rather, vim doesn't need to change its color scheme in order to be displayed in a completely different set of colors, which is what he's talking about. If you change the color mapping of your terminal and vim doesn't immediately reflect that, then your terminal is not applying those changes to that window/tab.
I'll see if this will work out for me. Don't know what any pitfalls could be by setting the color scheme in the terminal. At least it's annoying if you use different terminals on different systems, you'll have to configure them separately, you can't put it in your dotfiles repos or something. Thanks anyway, will look into it!
If you have access to an OS X environment, you can try out "invert colors" at System Preferences > Accessibility > Display. iOS has it, too.
As a related tip, on iOS you can have a home button triple-press shortcut which you can assign inverted colors or grayscale, or both. Was stoked when discovered that.
> Solarized is a sixteen color palette (eight monotones, eight accent colors) designed for use with terminal and gui applications. It has several unique properties. I designed this colorscheme with both precise CIELAB lightness relationships and a refined set of hues based on fixed color wheel relationships. It has been tested extensively in real world use on color calibrated displays (as well as uncalibrated/intentionally miscalibrated displays) and in a variety of lighting conditions.
I'm assuming this means it's giving a criterion to "measure" how good it is in a not-entirely-subjective-way. That always bothers me about selecting a theme. I have no idea if it's good or bad in any standard measurable way.
I look at these themes and can't really tell what it's "unique properties" or anything interesting about it just by looking at it.
No matter how advanced colour matching engineering was needed for solarized, there will always be a colour scheme that just looks more beautiful... in the eyes of the beholder :)
To me changing colour schemes is like changing your car - after a few years you feel it just does not shine like it used to, so you change it.
That is why we cannot achieve perfection.
Personally I use a slightly tweaked version of http://vimcolors.com/1/jellybeans/dark … the id of 1 in the URL suggests the author might too.
Whoever solves that problem earns a raise
I'm working on a new capture engine which fixes this.
Aside: The pages are also a good browser stress test with the large number of iframes.
This is great.