Klement wrote:
> I'm here to report what looks like a bug to me. Hopefully I'm not
> wasting your time.
>
> Here are the conditions.
>
> 1. Edit a blank file with no ft set (and hence no filetype plugins
> loaded).
>
> 2. Attempt to save the file with an extension which causes a filetype
> plugin to be loaded. (It seems to help if the filename chosen has
> slashes in it for directories.)
>
> 3. The plugin in question must be one that changes the active
> directory (through a command like `lcd %:p:r` or `set autochdir`).
>
> 4. Then rather than saving the file with the filename specified in
> step 2, it saves the file under a seemingly random name, often using
> what appears to be a line of code from the plugin as if it were the
> filename (though not the same line as mentioned in line 3).
>
> Anyway, I've recorded an animated .gif of the apparent bug in action,
> which you can view here:
>
> http://people.umass.edu/phil592w-klement/vimbug.gif
>
> You can see the file is being saved with a very strange filename, and
> not all the one specified.
>
> I'm using 7.3 on Arch Linux (x86_64).
I can't reproduce it. It does sound like a real bug, probably using
NameBuff or IObuff in an unexpected way.
Please find out the minimal setup to reproduce this, starting with "vim
-u NONE".
--
A law to reduce crime states: "It is mandatory for a motorist with criminal
intentions to stop at the city limits and telephone the chief of police as he
is entering the town.
[real standing law in Washington, United States of America]
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
