Re: has 7.4 changed behaviour chdir-ing to current file's dir by default?

On 29/12/13 18:51, jmlucjav wrote:
>
>
>
> On Sun, Dec 29, 2013 at 6:36 PM, Tony Mechelynck
> <antoine.mechelynck@gmail.com <mailto:antoine.mechelynck@gmail.com>> wrote:
>
> On 29/12/13 16:40, jmlucjav wrote:
>
> hey Tony
>
> with :verbose I still get the same:
> noautochdir
>
>
> meaning it was never changed from its default. Strange.
>
>
>
> About autocmd: I just pasted what I got from the log file, I
> dont know
> if the autocmd (and there is a autocommand before the au, not
> sure why
> you didnt see it) is linked with the chdir, let me copy exactly
> what I get:
> -----------------
> autocommand au! LoadBufferMenu
>
>
> chdir(C:\Users\jm\Dropbox\__conf\home\jm\vimfiles)
>
> C:\Users\jm\Dropbox\conf\home\__jm\vimfiles
> ------------------
>
> this is with gvim.exe -u NONE -U NONE -V9vimlog.txt
>
> Regarding the version, lol, I meant 7.4 32bit on win7 64bit. Exact
> version is 7.4 patch 131
>
> thanks
>
>
> Ah, that's better.
>
> About the autocommand: there is no LoadBufferMenu event (but any
> script could create a LoadBufferMenu group). Does Vim answer anything to
>
> :verbose au LoadBufferMenu
>
>
> just something along this:
> -----Auto-commands-----------
>
>
> ?
>
>
> -u NONE -U NONE means no vimrc, no gvimrc, no plugins. It even skips
> the system vimrc if there is one on your system. You must have done
> something else after that, or Vim would behave in a strictly
> standard way, with 'compatible' set (which is not what most of us
> expect, but we each have a vimrc), and no autocommands at all.
>
> Also, you might have a look at the output of the :scriptnames
> command. Do you see anything in there which you wouldn't have expected?
>
> I get this:
>
> 1: C:\Users\jm\Dropbox\portable\vim\menu.vim
> 2: C:\Users\jm\Dropbox\portable\vim\autoload\paste.vim
>
> no idea if this is ok or not. I have been using vim for a year or so but
> I am not a connoisseur regarding its inner workings or viml.
>
> BTW I am using vim from http://tuxproject.de/projects/vim/
>
> thanks!


If those two scripts are still loaded even when you do

vim.exe -u NONE -U NONE -V9 vimlog.txt

AND NOTHING ELSE, then there's something very weird at work. Maybe some
of the unlisted "manual compiling fixes" barely mentioned on that
tuxproject site.

For 32-bit Windows, Steve Hall's "Vim without Cream" has an established
reputation. Could you try it? It is found, as I already said, at
http://sourceforge.net/projects/cream/files/Vim/ . It is admittedly
still "only" at patchlevel 7.4.110, but if you don't see the bug in it,
then either it's in one of the 21 patches since then, or it's in
tuxproject's "manual fixes".

If there's a difference beween invoking "vim" and invoking "vim.exe"
then maybe there's a "vim.bat" somewhere. If so, then what does it contain?


Best regards,
Tony.
--
Time is money. Especially if you make clocks.

--
--
You received this message from the "vim_use" 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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.