begin quoting James G. Sack (jim) as of Wed, Jan 02, 2008 at 01:44:17PM -0800:
> Tracy R Reed wrote:
[snip]
> > Yeah, this is odd. I can't believe it's such a religious issue but there
> > seems to be a lot of contention between tabs and spaces. I always use
> > spaces. Because I want the code to render the same on any display I use.
> > I have my vi and emacs both configured to use 4 spaces except in
> > Makefiles or some similar place which explicitly wants tabs. It seems
> > the only thing anyone really agrees on is that it is evil to mix tabs
> > and spaces.
Ayup.
> <possible flamebait?>
> I've come around to thinking that the only good use for TAB is as a
> separator that works better than comma (eg,.csv). I grudgingly accept
> makefiles use of tab as a reasonable exception (or stretch of the
> separator definition).
I've been giving NetBeans a go, and I'm trying to get the Tab key to
be mapped to the "bring up completion options" -- with little success.
I really loathe the pop-a-dialog-up-while-typing (a rule of UI design:
NEVER take focus away from where the user is typing. Ever. Change of
focus should *always* be a user-initiated action.), but I'm told that
code completion is the big advantage.
And I'm not using that key for anything else, and it maps nicely into
how the shell uses tabs...
> I religiously avoid embedding TAB is any text.
I have a commit-script on my CVS repository that rejects (source) files
that contain tabs. Exceptions are made for Makefiles and some data files.
> I have sinned by using the TAB key to control indent, but now that I
> have learned about ^{T,D} in vim, I may escape that habit.
Hurrgh... ^D is "close stream" to me. I don't like typing it. :-/
--
Control S is not Save, it is Stop, don't you get it?
And Control Q is Quontinue, don't you see, not quit.
Stewart Stremler
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
