On Mon, Mar 19, 2018 at 5:53 PM, Bram Moolenaar wrote:
> Steve Hall wrote:
> >
> > The Cygwin build process broke since 8.0.1553 to embed the build
> > location into the executable. gvim.exe fails with "The procedure
> > entry point __gxx_personality_[profile]
The Cygwin build process broke since 8.0.1553 to embed the build
location into the executable. gvim.exe fails with "The procedure entry
point __gxx_personality_[profile] could not be located in the dynamic
link library C:\[buildpath]\src\gvim.exe".
--
Steve Hall [ digitect dancin
On Wed, 2018-01-31T1216, Bram Moolenaar wrote:
> Steve Hall wrote:
> >
> > I'm seeing a BufRead autocmd error in with ft=html:
> >
> > E117: Unknown function: dist#ft#FThtml
> >
> > This is called in filetype.vim but I can't grep a definition
&
is is called in filetype.vim but I can't grep a definition anywhere.
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are rep
On Mon, Jan 15, 2018 at 1:56 PM, Bram Moolenaar
wrote:
> Steve Hall wrote:
> >
> > Any interest in moving the entire Vim installer to NSIS?
>
> There have been a few attempts at this, but they all dropped some
> funcationality. Best would be to do this step by step, maki
th Cream for Vim's installer in 2003. It installs
shortcuts, start menus, icons, registry, right click menu, write the
vimrc, uninstaller, etc.--all without needing Vim's little terminal
pop-up window and DOS command line prompting system.
--
Steve Hall [ digitect dancingpaper com
s function)
if (rbg_status == STATUS_GOT)
^
term.c:5854:7: error: 'bg_r' undeclared (first use in this function)
*r = bg_r;
^
term.c:5855:7: error: 'bg_g' undeclared (first use in this function)
*g = bg_g;
^
term.c:58
Wed, Sep 27, 2017 at 9:26 AM, Ken Takata :
>
> There's no reason to avoid supporting D&D on GUI tab pages line.
Wow, I had no idea this was available. I've been waiting for this since
tabs were introduced. ;)
--
Steve Hall [ digitect dancingpaper com ]
On Sun, Sep 17, 2017 at 9:14 PM, Ken Takata wrote:
>
> I haven't installed 6.10, so I don't know the name of it. If you
> have already installed it, could you report the name here?
6.6 3m_a0solc
6.8 3m_a1zjsw
6.10 3m_a36fs8
All three build for me.
--
Steve Hall [ digite
On Sat, Sep 16, 2017 at 9:28 PM, Ken Takata wrote:
> 2017/9/17 Sun 4:05:18 UTC+9 Steve Hall wrote:
> > What is the MZSCHEME_VER variable nomenclature?
>
> As I wrote in src/INSTALLpc.txt,
Ah, was looking in the make files, :help mzscheme, if_mzsch, and
everywhere else but there
What is the MZSCHEME_VER variable nomenclature?
The docs say MZSCHEME_VER=3m_a0solc corresponds to 6.6. What is it for
6.10? Every other build version uses typical MZSCHEME_VER=610, but I
have never been able to figure out why scheme is special.
--
Steve Hall [ digitect dancingpaper com
On Mon, Mar 13, 2017 at 5:26 AM, Christian Brabandt
wrote:
> On Sa, 11 Mär 2017, Ken Takata wrote:
> > 2017/3/12 Sun 10:32:02 UTC+9 Steve Hall wrote:
> > >
> > > I've gotten multiple reports that my recent g/Vim windows x64
> > > builds (via Cygwin) ha
.430.
Any clues?
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
--
--
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/ma
That was it, I'm finally able to build an installer with all the
features. Thanks again.
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below t
I'm trying to build a full-featured x64 Vim for Windows (via Cygwin)
and lack only mzscheme. It fails against Racket 6.8, any tips on a
better distribution or version?
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
--
--
You received this message
On Tue, Feb 14, 2017 at 10:29 PM, Ken Takata wrote:
> 2017/2/15 Wed 11:05:21 UTC+9 Steve Hall wrote:
> >
> > i686-pc-mingw32-gcc -c -Iproto -DWIN32 -DWINVER=0x0501
>
> This shows that the setting of CROSS_COMPILE is not overwritten. I
> think that setting a variable in
On Tue, Feb 14, 2017 at 6:56 PM, Ken Takata wrote:
> 2017/2/15 Wed 5:43:08 UTC+9 Steve Hall wrote:
> >
> > I'm setting the environment elsewhere now. So the only other thing in
> > Make_cyg is UNDER_CYGWIN = yes. Not sure what that does, is it
> > important?
>
&
On Tue, Feb 14, 2017 at 9:58 AM, Ken Takata wrote:
> 2017/2/14 Tue 22:58:45 UTC+9 Steve Hall wrote:
> >
> > I'm was simply using "make -f Make_cyg.mak", that was the default.
>
> Hmm, did you set 'ARCH=x86-64' manually?
> The command line you pas
our CROSS_COMPILE set and all is good.
I'm curious how many folks out there still need a w32? Not that anyone
needs my builds anymore (hmm, 6k downloads of previous installer), but
I wonder if it
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
--
--
Y
undeclared (first use in this function)
make: *** [Make_cyg_ming.mak:887: gobjx86-64/charset.o] Error 1
Any hints?
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
On Sat, Jan 16, 2016 at 2:54 PM, Steve Hall
wrote:
> On Sat, Jan 16, 2016 at 9:45 AM, Bram Moolenaar
wrote:
> >
> > Patch 7.4.1103 (after 7.4.1100)
> > Problem:Removed file still in distribution.
> > Solution: Remove Make_cyg.mak from the list of files.
> >
a is that we're
supposed to use Make_cyg_ming.mak, it is completely broken for me.
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
http://SteveHallArchitecture.com
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
as
advertised since patches .985 and .987. ;)
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
http://SteveHallArchitecture.com
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text
Hi Ken,
On Thu, Dec 31, 2015 at 10:15 PM, Ken Takata wrote:
> 2016/1/1 Fri 11:13:23 UTC+9 Steve Hall wrote:
> >
> > This was Ruby 1.9.x (http://rubyinstaller.org). I just upgraded to
> > 2.1.7 and tried again:
>
> I tested RubyInstaller 1.9.3 with Make_cyg.mak and
in:
if_ruby.c:113:18: fatal error: ruby.h: No such file or directory
compilation terminated.
Make_cyg_ming.mak:781: recipe for target 'gobji386/if_ruby.o' failed
make: *** [gobji386/if_ruby.o] Error 1
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cr
8: recipe for target 'gvim.exe' failed
A shame, I really wanted to test the :smile command :(
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
http://SteveHallArchitecture.com
--
--
You received this message from the "vim_dev" maillis
ewhere
else, too.
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
http://SteveHallArchitecture.com
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For mo
a secure
system with only a very few fingers in the process. Frankly, my
process would be automated if it was possible to post the files to SF.
The host is the toughest part.
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
http://SteveHallArchitecture.com
without Cream installer components on disk:
2.64 Mb gvim.exe
2.46 Mb vim.exe
16.42 Mb /runtime - /spell
3.63 Mb /runtime/spell/en + /runtime/spell/*.*
These plus the Nullsoft bits create our 8.22 Mb installer.
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cre
is
non-standard from the typical GUI Vim version installation, we like to
provide the extra service to our customers for the same low price. :)
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
http://SteveHallArchitecture.com
--
--
You received this message fr
ows. They are usually not something that can be copied around
because they are OS version/system specific.
Most Linux GUI .desktop file formats are documented on the web. At one
point KDE and GNOME were trying to use a common format but I don't
know how that turned out.
--
Steve Hall [ d
++
+mingw-64-i686-gcc-g++
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim http://cream.SourceForge.net
SteveHallArchitecture http://SteveHallArchitecture.com
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text yo
ure will grow in proportion to their contributions
and their input will become correspondingly weighted.
There have been many contributors come and go over the years, but Bram
is still here maintaining the project and their features!
--
Steve Hall [ digitect dancingpaper com ]
Cream for Vim htt
On Mon, Nov 3, 2014 at 10:30 AM, Ken Takata wrote:
> 2014/11/3 Mon 22:40:30 UTC+9 Steve Hall wrote:
> > Is Make_cyg.mak still supported? It's been broken for a while:
> >
> > xpm_w32.c:31:17: fatal error: xpm.h: No such file or directory
> > compilation terminat
Is Make_cyg.mak still supported? It's been broken for a while:
xpm_w32.c:31:17: fatal error: xpm.h: No such file or directory
compilation terminated.
Make_cyg.mak:657: recipe for target 'gobj/xpm_w32.o' failed
make: *** [gobj/xpm_w32.o] Error 1
--
Steve Hall [ digit...@d
re some differences here from Cesar's setup that would
shed light?
> +PERL=/cygdrive/c/perl
Please do not hardcode paths in make files without ifndef !
--
Steve Hall [ digitect dancingpaper com ]
--
--
You received this message from the "vim_dev" maillist.
Do not top-
but I was able to cross-compile both a gvim.exe and
vim.exe with +perl/dyn.
--
Steve Hall [ digitect dancingpaper com ]
:: Cream for Vim http://cream.sourceforge.net
On Sun, Dec 1, 2013 at 2:37 AM, Ken Takata wrote:
> Hi Steve,
>
> 2013/11/30 Sat 22:09:18 UTC+9 Steve Hall wrote:
>
In function ‘XS_VIBUF_Delete’:
66:if_perl.c:1803:15: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast]
67:if_perl.c: In function ‘XS_VIBUF_Append’:
68:if_perl.c:1882:15: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast]
69:Make_cyg.mak:6
I finally tracked down my ruby feature bug in Make_cyg.mak, line 275
has an offending ".lib" extension.
Problem:Ruby feature broken in Cygwin build.
Solution: Remove errant extension.
Files: src/Make_cyg.mak
--- src/Make_cyg.mak
***
*** 273,277
DEFINES += -DDYNAMIC
riority
so our builds are currently -perl -ruby -tcl -mzscheme.
--
Steve Hall [ digitect dancingpaper com ]
:: Cream for Vim http://cream.sourceforge.net
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying t
On Fri, Nov 1, 2013 at 10:27 PM, Bram Moolenaar wrote:
>
> ...perhaps someone can take the Vim logo and generate an .eps file
> with another tool, which does not have this problem?
Attached is the logo opened and exported via Scribus, the meta info
removed.
--
Steve Hall [
On Thu, Sep 19, 2013 at 11:41 AM, Bram Moolenaar wrote:
> Steve Hall wrote:
>
> > Bug in line 443 of Make_cyg.mak: "-mno-cygwin" is obsolete. Result
> > is build failure of the standalone DLL.
>
> Is there an argument to replace it or does the line need to b
On Wed, Sep 18, 2013 at 2:23 PM, Steve Hall wrote:
> On Wed, Sep 18, 2013 at 2:10 PM, Steve Hall wrote:
> >
> > Bug in line 443 of Make_cyg.mak: "-mno-cygwin" is obsolete. Result
> > is build failure of the standalone DLL.
>
> This also shows up in line 11 o
On Wed, Sep 18, 2013 at 2:10 PM, Steve Hall wrote:
>
> Bug in line 443 of Make_cyg.mak: "-mno-cygwin" is obsolete. Result
> is build failure of the standalone DLL.
This also shows up in line 11 of xxd/Make_cyg.mak and causes failure.
--
Steve Hall [ digitect dancingpaper
Bug in line 443 of Make_cyg.mak: "-mno-cygwin" is obsolete. Result is
build failure of the standalone DLL.
--
Steve Hall [ digitect dancingpaper com ]
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are r
han expanded
OS widgets of course, and who has time for that? :)
--
Steve Hall [ digitect dancingpaper com ]
OsterlundHall Architects [ http://osterlundhall.com ]
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you
Hi Ken,
On Mon, Feb 18, 2013 at 9:24 AM, Ken Takata wrote:
> 2013/02/18 Mon 22:41:13 UTC+9 Steve Hall wrote:
> >
> > (Having to specify STATIC_STDCPLUS=yes at the build line is always
> > required.)
>
> Actually It is not required, if you use stdc++ DLLs.
> You may
On 02/16/2013 06:16 PM, Bram Moolenaar wrote:
>
> Patch 7.3.821
> Problem:Build with OLE and Cygwin is broken. (Steve Hall)
> Solution: Select static or shared stdc library. (Ken Takta)
> Files: src/Make_cyg.mak
Works for me.
Just curious why this wouldn't be th
fo for
IUnknown]+0x0): undefined reference to `vtable for
__cxxabiv1::__class_type_info'
gobj/if_ole.o:if_ole.cpp:(.rdata$_ZTI9IDispatch[typeinfo for
IDispatch]+0x0): undefined reference to `vtable for
__cxxabiv1::__si_class_type_info'
collect2: ld returned 1 exit status
Make_cyg.mak:567: recipe f
On Fri, Feb 15, 2013 at 9:58 AM, Ken Takata wrote:
> 2013/02/15 Fri 22:54:17 UTC+9 Steve Hall wrote:
>
>> Perhaps it was an earlier patch (my previous build was .801), but my
>> build with Cygwin now is broken:
[...]
>> Make_cyg.mak:613: recipe for target `obj/blowfish.o&#
sh.o /bin/sh: i686-pc-mingw32-gcc:
command not found
Make_cyg.mak:613: recipe for target `obj/blowfish.o' failed
make: *** [obj/blowfish.o] Error 127
--
Steve Hall [ digitect dancingpaper com ]
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply b
On Wed, Feb 6, 2013 at 3:43 AM, Tony Mechelynck <
antoine.mechely...@gmail.com> wrote:
>
> For Windows, I recommend whatever is newest at
> http://sourceforge.net/projects/cream/files/Vim/
[...]
> now at 7.3.762 since 3 January
[...]
> but OTOH I expect that Steve Hall (the ma
Sergey,
On Thu, Nov 29, 2012 at 11:46 PM, Sergey Khorev
wrote:
> On Thu, Nov 29, 2012 at 8:28 PM, Steve Hall wrote:
> > Unable to compile vim via Cygwin with Racket Scheme 5.3.1, produces
various
> > errors:
>
> Current patchlevel of Vim does not support Racket 5.2.x or 5.
: parse error before
'*' token
[...]
--
Steve Hall [ digitect dancingpaper com ]
--
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
) after copying
Ruby193/include/ruby-1.9.1/i386-mingw32/ruby/config.h
to
Ruby193/include/ruby-1.9.1/ruby/config.h
Thanks! I'll finally be able to roll Ruby in to our build again after about
a year.
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "
t; issue.)
I've been seeing this for a year with a Cygwin GCC build, starting
with the Ruby 1.9 series. Something changed so that Vim's build no
longer finds the necessary Ruby libraries, for me starting with
ruby.h. I've spent hours (one today!), but never could track it down.
--
lease-notes.txt
> for downloading.
Whoops, fixed this folder name for the record.
--
Steve Hall [ digitect dancingpaper com ]
--
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 informati
On Thu, Aug 23, 2012 at 12:58 PM, Bram Moolenaar wrote:
>
> Patch 7.3.638
[...]
Not sure why, but the :version command of my build this time produced the line:
Included patches: 1-638, 638
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_de
On Wed, Jun 20, 2012 at 7:19 AM, Steve Hall wrote:
>
> I should have added... just updated to Fedora 17 which has a broken
> Vim also related to Ruby:
> "error while loading shared libraries: libruby.so.1.8: cannot open
> shared object file: No such file or directory&quo
On Wed, Jun 20, 2012 at 7:12 AM, Steve Hall wrote:
> On Wed, Jun 20, 2012 at 2:57 AM, Ike Devolder wrote:
>>
>> i have posted in this mailinglist before for a solution for the dynamic ruby
>> stuff but found no answer yet.
>>
>> http://code.google.com/p
On Wed, Jun 20, 2012 at 2:57 AM, Ike Devolder wrote:
>
> i have posted in this mailinglist before for a solution for the dynamic ruby
> stuff but found no answer yet.
>
> http://code.google.com/p/vim/issues/detail?id=49
Same experience for me:
https://groups.google.com/forum/?fromgroups#!topic/vi
resulting value of y is 2x the request.
--
Steve Hall [ digitect dancingpaper com ]
--
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
f
> root certificates installed on everyone's machines, and self-signed
> certs must be manually added on every machine that wants to trust
> that author is who he or she claims they are.
It only takes funds because the crooks that are trying to scare
everyone into a fully sponsore
cally accomplished with signed files. Perhaps we're just talking
about the official binaries? Or just checksums?
--
Steve Hall [ digitect dancingpaper com ]
--
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
From: mattn, Fri, September 16, 2011 9:50 am
>
> Plz try this patch: https://gist.github.com/1222166
Still fails for me. Seems to be a path problem, make is looking for
/i386-mswin32 but strawberry ruby installs /i386-mingw32.
--
Steve Hall [ digitect dancingpaper com ]
--
You re
y.o
if_ruby.c:88:18: ruby.h: No such file or directory
if_ruby.c:90:28: ruby/encoding.h: No such file or directory
if_ruby.c:136: error: parse error before "objtbl"
if_ruby.c:136: warning: data definition has no type or storage class
[...]
--
Steve Hall [ digitect dancingpaper com ]
--
s
> the OP describes.
Ok, I have fixed this in our build code, effective our the next
distributed build.
Unless other conversation decides to eliminate the default vimrc for
Windows entirely... :)
--
Steve Hall [ digitect dancingpaper com ]
--
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
t users tamper with. The first line explains how to
> > rename the file to "activate" it.
>
> Something similar to <http://vim.wikia.com/wiki/Example_vimrc>, but
> with more settings commented out?
Exactly.
--
Steve Hall [ digitect dancingpaper com ]
--
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
the OP describes.
I'll fix this before our next update.
Does the default Vim set diffexpr ? I guess that's probably a good
idea for Windows, most users don't have a diff.exe on path.
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_d
From: Tony Mechelynck, Fri, March 18, 2011 5:51 am
> On 18/03/11 03:11, Steve Hall wrote:
> >
> > Can we not start distributing .vimrc and _vimrc instead of relying
> > on the installer to create these?
> [...]
>
> If we distribute .vimrc and _vimrc, wouldn'
.vimrc and _vimrc
instead of relying on the installer to create these?
Below is the _vimrc generated by the Cream installer, taken from Vim's
installer years ago. If someone can point out how it differs from the
current Vim default, I'll fix it.
--
Steve Hall
On Sat, 2011-02-12 at 14:00 +0100, Bram Moolenaar wrote:
> Patch 7.3.119
[...]
FYI, the email subject on this was "7.3.1".
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below th
From: Tony Mechelynck, Thu, August 12, 2010 5:00 am
> On 12/08/10 00:32, Steve Hall wrote:
> > As a rule, are the Mercurial runtimes more current than FTP? Or
> > are we still in the situation where either patches or FTP files
> > could be? (In times past, I found that
As a rule, are the Mercurial runtimes more current than FTP? Or are we still in the situation where either patches or FTP files could be? (In times past, I found that FTP always superseded patches.)-- Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vi
and BTW, how come your mailer always breaks threading when
> replying?
I sometimes have to use a browser-based mailer that is less than
respectable.
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your rep
le or output. I do this with
Cream and it because the user only has to run one command, I can
collect an exhaustive amount of data that would otherwise take hours
to run. Our script labels, formats, and even inserts folds in the log
for easy navigation.
--
Steve Hall [ digitect dancingpaper com ]
-
//tango.freedesktop.org/
which in my mind gets it right for clarity AND avoiding the glossy
Apple OS X look which went out of style about five years ago. (Now
avoided by even Apple themselves.)
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_dev&q
the
next few days.
--
Steve Hall [ digitect dancingpaper com ]
--
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
From: Bram Moolenaar, Wed, February 24, 2010 5:27 pm
> Steve Hall wrote:
> > From: Bram Moolenaar, Wed, February 24, 2010 9:48 am
> > >
> > > Patch 7.2.374
> >
> > I'm still seeing build errors with Windows/Cygwin related to Ruby,
>
[...]
>
>
3d): undefined reference to
`_rb_string_value_ptr'
gobj/if_ruby.o:if_ruby.c:(.text+0xf38): undefined reference to
`_rb_string_value_ptr'
gobj/if_ruby.o:if_ruby.c:(.text+0x1157): undefined reference to
`_rb_string_value_ptr'
collect2: ld returned 1 exit status
make: *** [gvim.exe] Erro
:if_ruby.c:(.text+0x104f): more undefined references to
`_rb_string_value_ptr' follow
collect2: ld returned 1 exit status
make: *** [gvim.exe] Error 1
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
lately.
Would this require everybody to install Python and this revision
control system just to download patches?
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
On Wed, 2009-12-09 at 21:39 -0800, char101 wrote:
> On Dec 10, 10:22 am, Steve Hall wrote:
> > >
> > > [problems building latest Windows binary gVim with strawberry
> > > perl 5.10.1.0]
>
> I see, probably it's because Perl_croak_xs_usage isn't li
trawberry perl
> 5.10.1.0 (checked).
Hmm, that's the version I'm compiling against (downloaded last week).
Is it possible that the compiler could be finding another perl (ruby,
tcl, mkscheme, cygwin) instead of using that specified by $PERL
explicitly in the build shell?
Thanks for he
t for the life of me, I can not figure out the issue.
Details:
* Strawberry perl 5.10
* Windows XP-32
* Cygwin gcc
* Experimented with the perl bin and libs first on path, last on path,
not on path, etc.
This all worked just a few days ago on another machine, but I can't
recall if it was strawbe
good defaults, and good comments, and it helps
> the user to understand what the _vimrc is. For more opinions, I
> think raising the question on vim_use would be a good idea.
I'm happy to adjust our distro to do whatever ends up in the default
Vim distribution.
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
Vim"
> from the Explorer context menu on a couple of files. It worked
> fine!
Then I wonder what the origins of MyDiff() are? Why did it come about?
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
t is not in the
> PATH), gvim can still invoke diff with no MyDiff. I guess that
> whatever system call gvim is using to spawn diff is causing
> Windows to search the same directory as gvim.
I'm not sure why or how Vim uses diff the way it does, but I would
have thought this
but why does the default
install have to condition use of diff in the vimrc instead of the
binary?
--
Steve Hall [ digitect dancingpaper com ]
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
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 th
From: James Vega, Tue, November 17, 2009 10:29 am
> On Tue, Nov 17, 2009 at 10:06 AM, Steve Hall wrote:
> >
> > Hmm... but I see this if I patch only up to 7.2.286, and not if I
> > patch only up to 7.2.285. Not sure how 7.2.294 is involved.
>
> Not sure, but someho
From: James Vega, Tue, November 17, 2009 9:55 am
> On Tue, Nov 17, 2009 at 9:27 AM, Steve Hall wrote:
> > fileio.c: In function `vim_settempdir':
> > fileio.c:7012: error: `vim_tempdir' undeclared (first use in this
> > function)
> > fileio.c:7012: error: (E
rror: `vim_tempdir' undeclared (first use in this
function)
fileio.c:7012: error: (Each undeclared identifier is reported only
once
fileio.c:7012: error: for each function it appears in.)
make: *** [obj/fileio.o] Error 1
--
Steve Hall [ digitect dancingpaper com ]
--~--~-~-
t easy to visualize:
* other non-printing characters that look like dec 032
* double spaces
* spaces after chars at window edges with wrap on
* every char as a byte
Currently, Vim can show every "invisible" character except
intermediate spaces, why not add it and be complete? :)
--
tchars" arguments.
Nice! Bram, any chance this could become official?
--
Steve Hall [ digitect dancingpaper com ]
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
e will
> compile but will not be functional.
Except that I did. Or at least I thought I did, turns out it was a
logic error in the build script. Fixed now, no build problems.
Sorry for the noise.
--
Steve Hall [ digitect dancingpaper com ]
--~--~-~--~~~---~--
build failure, with the following error:
\if_mzsch.c:641:3: #error MzScheme 4.x must include mzscheme_base.c, for
MinGW32 you need to define MZSCHEME_GENERATE_BAS
E=yes
make: *** [gobj/if_mzsch.o] Error 1
This is on WinXP-64, built using the Cygwin Make_cyg.mak.
--
Steve Hall [ di
recall
several years ago when I moved away from BCC that not all the usual
perl, python, tcl, mzscheme, ruby, ole, etc. features were.
--
Steve Hall [ digitect dancingpaper com ]
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" m
g that the option is
> deprecated and soon to be removed?
Not sure why something so useful would be intentionally dropped.
My gVim installer for windows is downloaded 5,000 times a month.
--
Steve Hall [ digitect dancingpaper com ]
--~--~-~--~~~---~--~~
You receive
From: Bram Moolenaar, Thu, November 06, 2008 2:47 pm
>
> Patch 7.2.030 (after 7.2.027)
> Problem:Can't compile.
> Solution: Remove prematurely added ex_oldfiles.
> Files: src/ex_cmds.h
[...]
This fixes the compilation problem for me on Windows.
--
St
1 - 100 din 103 matches
Mail list logo
