[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Why non-escaped newlines are prohibited in single-quoted string literals?
- From: KHMan <keinhong@...>
- Date: Mon, 30 Jan 2017 11:53:57 +0800
On 1/30/2017 9:21 AM, Tim Hill wrote:
On Jan 29, 2017, at 9:35 AM, KHMan wrote:
On 1/29/2017 11:41 PM, Egor Skriptunoff wrote:
On Sun, Jan 29, 2017 at 5:57 PM, Roberto Ierusalimschy wrote:
[snip snip snip]
should 'int' and 'size_t', in C, have the same color?
You can make two different highlighting profiles
and switch between them depending on your needs.
Agree, and I can't think of anything really bad as far as modern syntax highlighting is concerned, and styling can always be adjusted to meet personal needs. I don't hear of folks complaining about highlighting in Visual Studio either. So why are some folks not using it? Anyone else who prefer monochrome text who wants to speak up? :-)
Personally I find syntax coloring suffers from the “more is better” syndrome.
Definitely agree on a balance. There are editor users who want
more, more, more, e.g. highlight Perl code in the s/// with
evaluate option but folks like me talk them out of it. Let's just
say that it's easy for folks to suggest features, good and bad.
There is no style set to satisfy *all* users out-of-the-box, so
users should dial it up or down as they please.
Perhaps color just keywords and comments, but then leave everything else alone. it’s distracting to have too many colors (are horrid to look at), the default colors are often hard to read,
I would say to editor users, if you have a better colour scheme,
offer it as an improvement to the project. I mean, in my
experience, beyond the most common colours (e.g. green for
comments, perhaps popularized by Visual Studio?) everything else
is just picked out for the colour difference. If someone has
better methods to select styles, offer it to editors! When I added
styles for new Lua language features for Scintilla/SciTE, I just
casually picked a new colour that was different from the rest...
and is useless to anyone who is color-blind (more people than you would think, and one reason why color is not a sole primary indicator for critical interfaces such as airplanes and medical equipment).
It isn't a problem at all with a good configurable editor. Never
heard of anyone colour blind needing help for editors on other
mailing lists, ever. Styles can be disabled -- set to normal text
style. Some editors have plenty of style options, many not
involving colours: font, size, foreground colour, background
colour, italics, bold, weight, fill to end of line, underlined,
case -- so, one can syntax highlight in varied monochrome styles
too. The only snag is that it is not an out-of-the-box option -- a
non-issue for FLOSS editors which rely on the community for such
Kein-Hong Man (esq.)