Sure, here are my custom options. Autoindent works normally for all
other syntaxes that I use: PHP, CSS, HTML, JavaScript, Python.

--- Options ---
  autoindent          guioptions=egmL     incsearch
scroll=10           tabstop=4
  background=dark     helplang=En         laststatus=2
shiftround          undolevels=5000
  cmdheight=2         hlsearch            number
shiftwidth=4        wildmenu
  expandtab           ignorecase          ruler
softtabstop=4       window=43
  backspace=indent,eol,start
  guifont=Courier_New:h9:cDEFAULT
  statusline=[%l,%c %P%M] %f %r%h%w
  wildmode=longest,list


On Oct 23, 5:21 am, Ben Schmidt <[EMAIL PROTECTED]> wrote:
> Perhaps show us your whole :set output?
>
> :redir > somefile
> :set
> :redir END
>
> then attach/append somefile to an email. Maybe we'll spot something...
> I'm running out of ideas, though; it's weird.
>
> Ben.
>
> 703designs wrote:
> > No luck with those. I tried this on GVim (Windows), MacVim, and vim
> > from the terminal (the latter two on my Mac) and got the same results.
> > nopaste was set, and indentkeys includes 'o' in addition to quite a
> > few others.
>
> > Thomas
>
> > On Oct 22, 10:04 am, Ben Schmidt <[EMAIL PROTECTED]>
> > wrote:
> >> 703designs wrote:
> >>> If I type in:
> >>> Redskins = {team,<CR>{name, "redskins"}}.
> >>> After the carriage return, Vi should indent as:
> >>> Redskins = {team,
> >>>     {name, "redskins"}}.
> >>> But instead, the second line isn't indented. And I know that Vi
> >>> understands Erlang indentation because, after typing this, if I indent
> >>> the line (==), it indents properly. What's the deal? Indentation
> >>> always is invoked with a carriage return with other filetypes.
> >> It works for me. Perhaps you have somehow inadvertedly set 'paste'?
> >> Check
>
> >>      :set paste?
>
> >> and/or issue
>
> >>      :set nopaste
>
> >> and see if that fixes it. If not, perhaps check
>
> >>      :set indentkeys?
>
> >> and/or
>
> >>      :set indentkeys+=o
>
> >> Those are the most likely things I can think of that would cause the
> >> problem. Once you've tracked down what the problem is, find its cause by
> >> adding :verbose to the queries, e.g.
>
> >>      :verbose set paste?
>
> >> and you'll be able to track down the rogue script that's messing it up
> >> (hopefully).
>
> >> Cheers,
>
> >> Ben.
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to