[wplug] A question of etiquette

[Chester R. Hosey]

I hereby declare that both-posting is the new email paradigm -- I'm
adding the content at the beginning for the lazy and at the end for
those who like some form of logical structure.

I used to use vim with syntax highlighting but I more recently feel that
highlighting beyond dimming of comments can make code harder to read.

Maybe it's the product of astigmatism, but somehow having tons of colors
makes the code harder to read as a whole.

Chet Hosey

On Thu, 2005-06-02 at 13:02 -0400, Tom Rhodes wrote:
> On Thu, 02 Jun 2005 09:01:40 -0700
> "Michael P. O Connor" <mpop at mikeoconnor.net> wrote:
> 
> > 
> > 
> > > On Wed, 1 Jun 2005 22:16:58 -0700 (PDT)
> > > Rob Prowel <tempest766 at yahoo.com> wrote:
> > 
> > > Heh, on my GUI system, I have nedit installed.  It's a very
> > > lightweight WYSIWYG type editor.  Though I still use
> > > vi(1) 25% of the time.  All my non-GUI systems, it's
> > > vi(1) all the way.  I can't understand installing an application
> > > for the mere purpose of text editing when the base has
> > > several methods to edit text:
> > > 
> > > # cat <<EOF>> TXTFILE
> > > # vi TXTFILE
> > > # sed/awk/tr/whatever TXTFILE > NEWTXTFILE
> > > 
> > > Too easy.
> > 
> > depends on the text you are editing, I want my emacs for my cpp my h and
> > all my other files. vi remindes me to much of edline
> 
> If you need to have special formatting of special characters
> for programming, scripting, or what have you, check out vim
> and/or a ~/.virc file.
> 

I hereby declare that both-posting is the new email paradigm -- I'm
adding the content at the beginning for the lazy and at the end for
those who like some form of logical structure.

I used to use vim with syntax highlighting but I more recently feel that
highlighting beyond dimming of comments can make code harder to read.

Maybe it's the product of astigmatism, but somehow having tons of colors
makes the code harder to read as a whole.

Chet Hosey