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

Re: bug when using .c in :argedit and :argadd

Expand Messages
  • Benji Fisher
    ... I see the same strange behavior with vim 6.4, but not with vim 7.0. I tried both with -u NONE so there should not be any autocommands involved. --Benji
    Message 1 of 3 , Dec 22, 2005
      On Wed, Dec 21, 2005 at 10:55:20PM +0100, Bram Moolenaar wrote:
      >
      > Karsten Hopp wrote:
      >
      > > try ':argedit 1234.c".
      > > At the bottom of the screen appears: ".c" [New File] and :buffers prints
      > > 2 %a ".c" line 1
      > >
      > > And not unexpected when looking at the :buffers output there's a
      > > file '.c' instead of 1234.c after save&exit.
      > >
      > >
      > > A similar problem occurs with 'argadd 5678.c'
      > >
      > >
      > > >./src/vim --version
      > > VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Dec 20 2005 14:48:49)
      > > Included patches: 2-4
      >
      > Strange, it doesn't happen for me. Perhaps there is an autocommand that
      > gets in the way?

      I see the same strange behavior with vim 6.4, but not with vim 7.0.
      I tried both with "-u NONE" so there should not be any autocommands
      involved.

      --Benji Fisher
    Your message has been successfully submitted and would be delivered to recipients shortly.