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

3978Re: [OT] Bug or Feature?

Expand Messages
  • Andre Berger
    May 27, 2006
    • 0 Attachment
      * Ned Konz (2006-05-28):
      > Andre Berger wrote:
      > >* Chris Allen (2006-05-26):
      > >>On 5/26/06, Andre Berger <andre.berger@...> wrote:
      > >>>* Chris Allen (2006-05-26):
      > >>>>On 5/25/06, Andre Berger <andre.berger@...> wrote:
      > >>>>>I don't know if it's a change in Vim 7.0, or a setting on my system--
      > >>>>>anyway, I would like :w on a freshly started vim to behave as it did
      > >>>>>before, the way :saveas does (see the file you just wrote in the
      > >>>>>current buffer). Do you know what I mean?
      > >>Let's just have a second look at this one. You mean when you do
      > >>something like ":w foo" you want to see, but do not see, a message
      > >>like ""foo" [New] 0L, 0C written", or I am thinking of the wrong
      > >>behaviour?
      > >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.
      >
      > It seems to be a local problem, or maybe your vimrc or other script files are strange somehow.
      > On my 7.0.017 version, ":w foo" and ":saveas foo" behave exactly the same, which is also what
      > you describe wanting to have happen.
      [...]
      > rm -f foo vimmsg.txt
      > vim -u NONE -U NONE -c 'redir > vimmsg.txt' -c 'w foo' -c messages -c q
      > cat vimmsg.txt
      [...]
      > and tell us what you get.

      $ cat vimmsg.txt

      "foo"
      "foo" [New File] 0 lines, 0 characters written
      Messages maintainer: Bram Moolenaar <Bram@...>

      You're right, it seems to be related to my vimrc. It's been working
      fine with all versions < 7. Sigh.

      -Andre
    • Show all 17 messages in this topic