Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Turning off syntax highlighting

dudzik.co

Post reply on HN
Print view View original

141–150 of 192 posts

Re: Turning off syntax highlighting

#142

Post by foobarian »

the_mitsuhiko wrote: post #13

I tried this multiple times over the last few years and it always didn't matter. It's not making a measurable difference but it looks less pleasant and I rather look at pretty things.

I also don't find the syntax coloring to make a big difference for me. What does though is the semantic feedback/navigation in the IDE.

When I joined a Java shop for the first time I was all gung-ho about sticking to my 80x24 terminal and emacs and to heck with the point-and-click crowd who couldn't do their work without a graphical UI. Then my new manager got me to try Eclipse for a week. I humored him and discovered that I was an order of magnitude more productive with Eclipse's semantic features like on-the-fly compile error underlining, code autocomplete, and navigation. It really was a humbling experience.

Re: Turning off syntax highlighting

#143

Post by dsymonds »

myg204 wrote: post #141
stevebmark wrote: post #10

Not this again "We should remove all color from traffic lights and make people remember which position is what"

About 8% of the world is color blind, so having standard positions on traffic light is indeed very important.

Actually instead they tint the traffic light colours to make them distinguishable to colour blind folk.

It's actually really uncommon to be completely unable to see colour; mostly it is just a problem to be able to distinguish colours.

Re: Turning off syntax highlighting

#144

Post by [deleted] »

yoz-y wrote: post #134
kazinator wrote: post #112

Earlier quoted context omitted.

You understand wrong. When that author typed ":syntax off" in Vim, he was actually disabling possibly the best syntax coloring engine there is.

On that I disagree. I am a long time Vim user and I always enable vim mode wherever I can. But compared to IDEs and editors that use compilers for hilighting, vim is pretty poor.

[deleted]

Re: Turning off syntax highlighting

#145

Post by Yaggo »

I do use syntax highlighting, but only with two additional subtle colors (one for literals, another for language keywords). Many editors come with themes resembling a decorated Christmas tree.

Re: Turning off syntax highlighting

#147

Post by enneff »

mseepgood wrote: post #26
aratno wrote: post #3

I totally agree with this, and use `:syntax off`, but comments really mess with visual clarity. For dimmed comments, I sometimes switch to nofrils. https://www.robertmelton.com/2016/04/10/syntax-highlighting-...

Comments are the most important part of code. They should not be dimmed. If anything, they should be the only thing that is highlighted.

My highlighting scheme is to very slightly dim comments, because they tend to be more dense than code. For example: http://imgur.com/a/bxfBO

Re: Turning off syntax highlighting

#148

Post by je42 »

iLoch wrote: post #37
DSMan195276 wrote: post #20

Earlier quoted context omitted.

I agree completely. On that note, I also consider `git add -A` to be horrible practice. Adding files manually makes you tons more aware of what changes you actually made, and also prevents you from accidentally adding extra files you don't want. I also recommend people to look at the Linux kernel git history for good examples of how to use git well. Even if you have no knowledge of kernel code (and most people don't)…

I just don't understand why people use the git CLI. Git is too powerful a tool, using the CLI limits one of two things: your capabilities, or your productivity. Often times I see my coworkers screwing around with git trying to review diffs and commit their changes. One of two things happens: they spend longer than they should doing it, or they do it haphazardly. Sometimes they get it wrong. Just use a GUI. I use Sour…

No gui that I have seen can deal with the GIT workflows in an efficient manner. Most GUIs are slow. Rethink GIT workflows and make them worse. I only use a GUI for this: - GitX for adding and reviewing files to a commit. (partial commit support is also very nice).

the rest is command line git.

With command line completion is pretty good and fast.

Re: Turning off syntax highlighting

#149

Post by bbarn »

On an average day, I use visual studio for 4 languages. There's C#, HTML, JS, and some old VB.net depending on how old the code I'm working with is. Many times the same fix/feature will touch all of them. That's just on the .net stuff. Having the same general colorization scheme in place is probably all that makes skimming through code possible for me.

I remember feeling like the game changed when I went from grey and yellow on black to grey and holy crap other colors for other things on blue from turbo pascal 3 to 7. You can't take it back from me now. I've had my syntax highlighted for 2/3's of my life now, I'm not giving it back.

Post reply on HN