Steve Hall wrote:
>> The version of _vimrc installed by the Cream vim "without
>> Cream" installer appears to be an obsolete version and
>> contains a MyDiff() that doesn't work.
>
> Thanks for your helpful bugfix, I will change this for the
> next build.
Sorry, I should have reported this to Stev
On Tue, 2009-12-01 at 14:49 -0800, Gary Johnson wrote:
> The version of _vimrc installed by the Cream vim "without Cream"
> installer appears to be an obsolete version and contains a MyDiff()
> that doesn't work.
Thanks for your helpful bugfix, I will change this for the next build.
--
Steve Hal
Looking through the source code, I realize that this is a false alarm. The
test1 Makefile is actually a link to the file shown in buffer 4, which
bufexists is clever enough to figure out. Should the help entry for bufexists()
mention that symbolic links are resolved?
Thanks,
David
-Origina
On Tue, Dec 1, 2009 at 5:49 PM, Gary Johnson wrote:
> The version of _vimrc installed by the Cream vim "without Cream"
> installer appears to be an obsolete version and contains a MyDiff()
> that doesn't work.
Letting them know would probably work better as I'm not sure their
developers watch thi
The version of _vimrc installed by the Cream vim "without Cream"
installer appears to be an obsolete version and contains a MyDiff()
that doesn't work.
I recently installed vim-7.2.303 from the "without Cream" download
page, http://sourceforge.net/projects/cream/files/Vim, onto a device
running Wi
Hi folks,
I've been working on a script of mine and found this problem. If I call this
command:
:echo
bufexists("/home/mossberg/team/dalarson/mossberg/sim/tests/test1/Makefile")
it returns 1. It should have returned 0 because this buffer doesn't exist:
:ls!
1 #"/home/mossberg/team/dalar
chris...@256bit:~/local/share/vim/vim72/doc$ diff -Nu version7*
--- version7.txt2009-01-14 21:14:42.0 +0100
+++ version7.txt.new2009-12-01 20:32:22.0 +0100
@@ -1,4 +1,4 @@
-*version7.txt* For Vim version 7.2. Last change: 2008 Dec 17
+*version7.txt* For Vim version 7.
Fullquote, 'cause copying this message to vim_dev
Hi Andy!
On Di, 01 Dez 2009, Andy Wokula wrote:
> Christian Brabandt schrieb:
> > Hi Andy!
> >
> > On Di, 01 Dez 2009, Andy Wokula wrote:
> >
> >> Andy Wokula schrieb:
> >> setlocal formatexpr=FexLogBook()
> >>
> >> func! FexLogBook()
> >>
Since Windows' cmd.exe handles forward slash perfectly well, and
things like wildcards in file names do NOT work with backslashes, I
have 'shellslash' set in my _vimrc in Windows. I have recently ran
into the following problem:
Launch Vim in Windows XP with:
gvim -N -u NONE -i NONE
:echo shelles
