51–60 of 110 posts
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
Earlier quoted context omitted.
Slightly related, I don't like (mostly in OOP langs) when I have something like: 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…
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.
> 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.
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/
Earlier quoted context omitted.
Don't set the colorscheme on Vim, set it on your terminal and Vim will honor it. I do that with iTerm2.
But you'll have to restart the terminal for that, right?
Earlier quoted context omitted.
Running a terminal inside an editor inside a terminal... What is the use case for this that tmux/screen does not solve?
Some more info here which might shed some light: https://news.ycombinator.com/item?id=9132352
When filtering by Light, some color schemes come through that are Dark. Is this a bug or do those color schemes have both light and dark versions? I looked at one of the dark "light" schemes and it didn't seem to have a light version on the github page.
You're correct, this is a bug - occasionally the app has trouble detecting which backgrounds a colorscheme supports. I'm working on a new capture engine which fixes this.
So the Solarized home page starts off with this paragraph: > 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…
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.