Loading ...
Sorry, an error occurred while loading the content.

32327Re: vim's -l command-line option not quite vi-compatible

Expand Messages
  • Dorai Sitaram
    May 1, 2003
    • 0 Attachment
      Bram wrote:
      >
      > Dorai wrote:
      >
      > > Minor but hopefully easy fix.
      > >
      > > vim's -l command-line option seems to apply the 'lisp'
      > > option only to the first file that it opens. Per vi
      > > tradition, every file opened by vim -l, whether given
      > > on the command line, or opened with a :e, should get
      > > the 'lisp' option set.
      > >
      > > (In other words, this is somewhat like -R option, which
      > > also applies to every file opened.)
      >
      > Indeed. Strange that nobody noticed this until now.

      Well, here's a patch for doc/options.txt that should
      solve the low visibility of vim among Lisp users. 1/2:-)


      *** options.txt Wed Apr 23 10:29:14 2003
      --- options.txt.new Thu May 1 14:24:39 2003
      ***************
      *** 3564,3570 ****
      {not available when compiled without the |+lispindent|
      feature}
      Lisp mode: When <Enter> is typed in insert mode set the indent for
      ! the next line to Lisp standards (well, sort of). Also happens with
      "cc" or "S". 'autoindent' must also be on for this to work. The 'p'
      flag in 'cpoptions' changes the method of indenting: Vi compatible or
      better. Also see 'lispwords'.
      --- 3564,3570 ----
      {not available when compiled without the |+lispindent|
      feature}
      Lisp mode: When <Enter> is typed in insert mode set the indent for
      ! the next line to Lisp standards. Also happens with
      "cc" or "S". 'autoindent' must also be on for this to work. The 'p'
      flag in 'cpoptions' changes the method of indenting: Vi compatible or
      better. Also see 'lispwords'.
    • Show all 3 messages in this topic