h.m.brand at xs4all
Aug 15, 2012, 8:17 AM
Post #3 of 4
On Wed, 15 Aug 2012 15:55:05 +0100, Nicholas Clark <nick [at] ccl4>
Re: Cross-compiling, Errno_pm.PL and include paths..
[In reply to]
> > +# Local variables:
> > +# c-indentation-style: bsd
> > +# c-basic-offset: 4
> > +# indent-tabs-mode: t
> The new black is indent-tabs-mode: nil
> > +# End:
> > +#
> > +# ex: set ts=8 sts=4 sw=4 noet:
> > +#
> > +
> and hence (I think) et:
> I'm not sure where that needs to be documented, as it doesn't seem to be yet.
> Nicholas Clark
My ex clone does not know about et (nor expandtab):
bad option name et
It does however have
inputtab, itab (One-Of, buf)
The inputtab option controls the behavior of the Tab key. It can be set
to one of the following values:
* tab - insert an actual tab character. This is the traditional vi
behavior, and the default for user buffers.
* spaces - insert enough space characters to look like a tab
* filename - attempt filename completion on the preceding word.
Normally this only completes the names of text files, but you can
set the completebinary option to allow binary file names to be
* identifier - attempt tag name completion on the preceding word. If
the word is already complete, or if cursor isn't at the end of a
word, then it inserts a plain tab character. This can be handy when
you're editing source code.
* ex - a smarter version of filename completion, it knows enough
about ex command line syntax to avoid some tabbing mistakes that
the filename setting can make. It can also complete ex command
names, tag names, option names, and option values. This is the
default for the (Elvis ex history) buffer, which is used for
entering in ex commands.
smarttab, sta (Boolean, global)
The smarttab option only affects the behavior of the Tab key in input
mode, when the cursor is in the indentation portion of a line -- before
the first non-whitespace character. If this option is true, then Tab is
treated like ^T, so the line is shifted rightward by one shiftwidth. By
default this option is false, so the Tab key is treated normally (in
accordance with the inputtab option).
autotab, at (Boolean, buf)
The autotab option affects the behavior of the < and > operator commands,
and the ^D and ^T input mode keystrokes. If autotab is true then elvis
will include tab characters in the indentation whitespace; if it is false
then the indentation whitespace will consist entirely of space
characters. By default, it is true.
Note that if you start with a buffer which contains no tabs, and do a ":
set inputtab=spaces noautotab" then no amount of editing will result in
the buffer containing tabs... unless you get tricky with ^V or something.
How far do you want to go in making editor hints editor-dependent?
H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/
using perl5.00307 .. 5.14 porting perl5 on HP-UX, AIX, and openSUSE