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

3969Re: [OT] Bug or Feature?

Expand Messages
  • Chris Allen
    May 26, 2006
      On 5/26/06, Andre Berger <andre.berger@...> wrote:
      > Yes. I start vim without any command line-arguments, and get a "no
      > name" (previously a "no file") buffer, about which I read in the
      > upgrade information. So far, so good. I type my text, and save it to
      > a file with ":w". Previous versions of Vim wrote the file and loaded
      > it into the initial buffer, like ":saveas" does. 7.0.17 (my huge
      > self-compiled version) just writes to the file, but keeps the noname
      > buffer. I would like to have the old behavior back. I hope it's
      > clearer what I mean now. I asked this here because I wasn't sure if
      > that's a design change, Mac related, or a local problem.

      Interesting. I still get that behaviour, certainly, using 7.0.17,
      home-built huge. I can't think of a build option or runtime option to
      disable that, but I certainly don't know everything. Can you give us
      the output of ':set'?

      Chris Allen
    • Show all 17 messages in this topic