Live data from Hacker News

Vim Colors

vimcolors.com

91–100 of 110 posts

Re: Vim Colors

#91
post #15

Earlier quoted context omitted.

It occurs to me that the fewer lexical types a language has, the less possible it is to highlight it in a pleasant way. Lisps and Forths (and most assembly languages) must look unpleasantly spare; and an encoding like Urbit's Nock would be literally monochrome.

Unpleasantly spare? http://take.ms/k83XH

Clojure is an exception to the number of lexical types found in most Lisps, note. Scheme doesn't highlight nearly as nicely.

Re: Vim Colors

#92
post #49

Earlier quoted context omitted.

Why is something limited in highlighting because it's a text editor and not an IDE? Highlighting is about text so it's quite a core feature of an editor.

Usually because the text editor is limited to regular expression and region matching, while the IDE parses the language into an AST so it knows what each bit actually means.

Except a text editor can also generate the AST.

Re: Vim Colors

#93
post #15

Earlier quoted context omitted.

It occurs to me that the fewer lexical types a language has, the less possible it is to highlight it in a pleasant way. Lisps and Forths (and most assembly languages) must look unpleasantly spare; and an encoding like Urbit's Nock would be literally monochrome.

Unpleasantly spare? http://take.ms/k83XH

OMG! How do I do that? Mind sharing your configuration?

Re: Vim Colors

#95

Earlier quoted context omitted.

Usually because the text editor is limited to regular expression and region matching, while the IDE parses the language into an AST so it knows what each bit actually means.

Except a text editor can also generate the AST.

What I meant was that the limitation in highlighting is usually due to the limitation in pattern matching. Of course, IDEs usually contain text editors, and they often do highlight using an AST. But that's expensive, both to develop and to run, and especially if you're not going to use the AST for any other IDE-like activity. Pattern-matching is cheap and usually good enough.

Re: Vim Colors

#96
Thumbnails would be great. A gallery view of thumbnails, possibly accompanied by a palette of the main colors in the scheme, would greatly assist the browse-ability of the site.

This is great.

Re: Vim Colors

#97

I'm probably in the minority, but I've always found that anything other than constant-coloured text on a constant-coloured background with a high contrast to be more distracting than helpful. It appears I'm not the only one: http://www.linusakesson.net/programming/syntaxhighlighting/

Having different colors for code, keywords, comments, and string literals greatly assist in scannability for me.

Re: Vim Colors

#98
Very cool. I'd love to see the ability to tag and filter 256-color schemes, for `TERM="xterm-256color"`. And some ranking metric (e.g. stars on the GitHub repo) would help surface the good ones that a lot of people use.

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.

Re: Vim Colors

#99

I'm probably in the minority, but I've always found that anything other than constant-coloured text on a constant-coloured background with a high contrast to be more distracting than helpful. It appears I'm not the only one: http://www.linusakesson.net/programming/syntaxhighlighting/

Seconded. This is one of the few lines in my .vimrc

> nmap :if exists("syntax_on") \| syntax off \| else \| syntax enable \| endif \|

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.

Re: Vim Colors

#100

I wish I could choose a language to preview the schemes with. My biggest gripe with many of these themes is that is looks great in some languages and terrible for everything else.

vim color schemes previewed in a variety of popular languages: https://code.google.com/p/vimcolorschemetest/ Just choose a language at the bottom of the page. Then wait... it takes a while to load the next page because its got a lot of html in many iframes
Post reply on HN