Re: Updates on the Vim project

If your PHP runs on E_ALL and everything’s fine, you’re probably good indeed. Unlike Git, hg won’t need too many tutorials on the internet because it’s intuitive to use. :-p YMMV… > On Montag, Aug. 28, 2023 at 7:05 PM, Christian Brabandt (mailto:cbli...@256bit.org)> wrote: > > On Mo, 28 Aug

Re:How about dropping the MzScheme interface?

Bram Moolenaar schrob am 26.01.2020 um 18:57: >OK, that is good to know. Is this with scripts you only write for >yourself, or something you publish? I rarely publish my scripts for anything - the only script which made it to Vim's scripts repository is Logpad.vim which was in VimL.  It's

Re:How about dropping the MzScheme interface?

Bram Moolenaar schrob am 24.01.2020 um 21:21: >So, who would complain if we drop the MzScheme interface? >Please reply to the vim-use and/or vim-dev maillist. I would. It is the only interface I use myself. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type

Re: So, how about Vim 9?

I really like the approach to unify the scripting interfaces, bringing Vim closer to Acme where any language can extend the editor by echoing plain text. Thank you for the roadmap, I will definitely be a tester! -- -- You received this message from the "vim_dev" maillist. Do not top-post!

Re: [vim/vim] Windows binaries are old - when can we get updatedversions? (#5045)

Pf... https://tuxproject.de/projects/vim Always ready for you. At 07:09 AM 11.10.2019 -0700, Christian Brabandt Vim Github Repository wrote: >this way: https://github.com/vim/vim-win32-installer >— >You are receiving this because you are subscribed to this thread. >Reply to this email

Building on MSVC won't work ...

Somewhere in between, termscreen.c was broken: > termscreen.obj : error LNK2005: vterm_screen_get_attrs_extent ist bereits in > screen.obj definiert. > termscreen.obj : error LNK2005: vterm_screen_set_damage_merge ist bereits in > screen.obj definiert. > termscreen.obj : error LNK2005:

I can't compile Vim x86 with ActiveTcl x64

> if_tcl.obj : error LNK2001: Nicht aufgelöstes externes Symbol > "_Tcl_InitStubs". > if_tcl.obj : error LNK2001: Nicht aufgelöstes externes Symbol "_tclStubsPtr". Tcl seems to be the only Vim scripting language that explicitly requires both platforms if I want to have both an x86 and a x64 Vim.

Re: What do Vim plugin authors want from Vim?

It looks like the SO people don't really appreciate this kind of question. -- -- 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 --- You received this

Re: Visual Studio 2017 fails to compile one of six Vims...

Tony Mechelynck schrob am Freitag, 29. Juni 2018 um 05:41 Zeit: > So the question arises: do you have the correct software installed > (including headers) to compile and link with 32-bit OLE? I was thinking so. Hmm... Investigating. -- -- You received this message from the "vim_dev"

Visual Studio 2017 fails to compile one of six Vims...

As some of you might know, I provide my own Windows Vim builds. My latest hardware upgrade brought a new infrastructure though. I usually compile six Vims in a row: - x86 GVim without OLE - x86 GVim with OLE - x86 CLI Vim - the same for amd64 Now I get these errors _exclusively_ with x86 GVim

Re: Patch 8.0.1461

GVim can't be compiled after 1459 anymore, at least not on Windows: > gui.c(5531): error C2198: "vim_chdirfile": Nicht genügend Argumente > für Aufruf. I suspect that another file is missing... -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below

Re: Ruby DLLs have a wrong name when compiled with MSVC

Ken Takata schrob am Sonntag, 27. August 2017 um 17:19 Zeit: > When you compile Vim, the first part of the Ruby dll name is decided > by the compiler version Obviously, the decision is not quite correct, because no MinGW is involved in my "stack". > Didn't you set RUBY_MSVCRT_NAME explicitly?

Ruby DLLs have a wrong name when compiled with MSVC

I'm not sure if this is my or Vim's problem, so I won't try to "patch" it just yet: As some of you know, I use to compile my own Vim builds on Visual Studio (MSVC from here on). This also means that I have to compile Ruby myself, since Vim, when compiled with MSVC, does not play well with the

[patch] Compilation fix for Win32 with TERMINAL

Attached: the patch for the missing semicolon. Tested with 8.0.0844. -- -- 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 --- You received this message

Re: Patch 8.0.0773

That fixes it for me. Thanks! -- -- 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 --- You received this message because you are subscribed to the Google

Re: Patch 8.0.0756

Hmm... works partially. x86 builds fine, x64 fails with a number of undefined _vertm_ symbols... -- -- 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 ---

Re: Patch 8.0.0742

Hmm, why is MSVC unsupported? There is an MSVC2015 download on that GitHub page for WinPTY. -- -- 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 --- You

Re: MSVC 2015: GvimExt doesn't take SDK_INCLUDE_DIR

My fault, sorry. Ignore my previous e-mail :) -- -- 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 --- You received this message because you are subscribed

MSVC 2015: GvimExt doesn't take SDK_INCLUDE_DIR

While trying to build Vim/GVim with Visual Studio 14.0, I noticed that the SDK_INCLUDE_DIR="..." definition is ignored for GVimExt: >Bibliothek "gvimext.lib" und Objekt "gvimext.exp" werden erstellt. >if exist gvimext.dll.manifest mt -nologo -manifest > gvimext.dll.manifest

Re: Will there be 8.0 after 7.4.1999 ?

Is that important? -- -- 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 --- You received this message because you are subscribed to the Google Groups

Re: Strawberry Perl 5.24 doesn't work.

I already had the other patch. Whoops... Yours compiles, thank you! -- -- 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 --- You received this message

Strawberry Perl 5.24 doesn't work.

Well ... > if_perl.obj : error LNK2001: Nicht aufgelöstes externes Symbol > "__imp__Perl_savetmps". > gvim.exe : fatal error LNK1120: 1 nicht aufgelöste externe Verweise. :-( -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are

[PATCH] Compiler warning in if_ruby.c

Annoying. ;-) -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev"

Re: Vim 7.5 or Vim 8?

ASIO and Jobs alone should perfectly rectify going to 8.0. -- -- 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 --- You received this message because you

if_mzsch warnings

Random warning of the day: > if_mzsch.c > if_mzsch.c(551) : warning C4273: > 'scheme_external_get_thread_local_variables': Inkonsistente DLL-Bindung. >c:\users\hp\desktop\racket-x86\racket\include\schthread.h(450): Siehe > vorherige Definition von

Re: Patch 7.4.1437

Ken Takata schrob am Samstag, 27. Februar 2016 um 21:02 Zeit: > Attached patch should fix them. Confirmed. :-) -- -- 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

Re: Patch 7.4.1437

Bram Moolenaar schrob am Samstag, 27. Februar 2016 um 20:14 Zeit: > Adjust #ifdefs. Detect isnan() and isinf() functions with configure. > Use a replacement when missing. (Kazunobu Kuriyama) Sadly, that breaks on Windows (MSVC2010) again, probably related to Perl: > if_perl.c >

[PATCH] Compiler warning in ex_cmds2.c [after 7.4.1384]

Well, well. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev"

Re: Removing Win16 code

Bram Moolenaar schrob am Mittwoch, 17. Februar 2016 um 20:55 Zeit: > Does this even still build? I could set up a VM to test if this is what its future depends on. Why do we have a restriction to "Windows XP onwards" at all? -- -- You received this message from the "vim_dev" maillist. Do not

Re: Patch 7.4.1314

MSVC build is still broken. Interestingly, GVim compiles but Vim does not: > eval.obj : error LNK2001: Nicht aufgelöstes externes Symbol > "_channel_close". > vim.exe : fatal error LNK1120: 1 nicht aufgelöste externe Verweise. -- -- You received this message from the "vim_dev" maillist. Do

Re: Patch 7.4.1316

Thank you. :-) -- -- 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 --- You received this message because you are subscribed to the Google Groups

Re: Channel & job design

I have read your thoughts about msgpack vs. JSON and I just want to take this chance and propose to use S-expressions instead, JSON without the syntactic bloat. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For

[patch] more __ARGS

Now it compiles with all the features again ;-) -- -- 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 --- You received this message because you are

Re: Patch 7.4.1202

Bram Moolenaar schrob am Freitag, 29. Januar 2016 um 23:46 Zeit: > Patch 7.4.1202 > Problem:Still one more file still using __ARGS. > Solution: Remove __ARGS in the last file. No, close to last ... :-) you missed proto/if_mzsch.pro -- -- You received this message from the "vim_dev"

Re: if_mzscheme does not work.

Still not working on Windows: > raco.exe: Unrecognized command: ctool > > Usage: raco ... ... -- -- 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 ---

Re: if_mzscheme does not work.

Christian Brabandt schrob am Mittwoch, 6. Januar 2016 um 20:08 Zeit: > Is this a self-compiled racket? Yes, but that shouldn't matter at all because (as I stated in an earlier thread on this mailing list that has completely been ignored by everyone...) "raco ctool" has been removed from Racket

Re: if_mzscheme does not work.

Christian Brabandt schrob am Mittwoch, 6. Januar 2016 um 20:47 Zeit: > Where does it say so? http://download.racket-lang.org/v5.2.html "The Racket-to-C compiler (as accessed via `raco ctool' or `mzc') has been removed; Racket's JIT has long provided better performance, and the FFI provides

Re: Patch 7.4.1036

Wow, 50 patches in a week. Aiming for 7.4.2000, are we? :D -- -- 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 --- You received this message because you

Re: Updating runtime files without version control

Bram Moolenaar schrob am Freitag, 1. Januar 2016 um 22:30 Zeit: > I tried Ruby 2.2, but it appears it doesn't work with MSVC. Right, you'll need a self-built Ruby for that. This was discussed on this mailing list: https://groups.google.com/d/msg/vim_dev/P8l30hk9hyE/cG8wYjh3paMJ -- -- You

Re: Python 2.7.11 not working (probably after 1012)

Ahh ... that does the trick. Thank you! :) -- -- 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 --- You received this message because you are subscribed to

Python 2.7.11 not working (probably after 1012)

I updated my Python 2.7.10 to 2.7.11 and compiled Vim (Make_mvc, my compile.bat is available online [1]) again, now I get "the Python's site module is not available" every time I type :python (something). Has anything relevant changed in Python itself or was one of the last few dozen patches

Re: Python 2.7.11 not working (probably after 1012)

Renaming the registry key does not fix the issue for me though :/ -- -- 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 --- You received this message because

Re: Patch 7.4.970

Bram Moolenaar schrob am Sonntag, 13. Dezember 2015 um 14:45 Zeit: > If I look at https://tuxproject.de/projects/vim/ I don't see that > button. In fact I don't know how to download. Perhaps you can redo > that page. I would expect a nice big download button, with an > explanation of what is

Re: Patch 7.4.970

Bram Moolenaar schrob am Sonntag, 13. Dezember 2015 um 17:33 Zeit: > These are 7zip files. I don't think 7zip is included with the Windows > distribution. And then how to unpack? The text says it's an archive, > not an installer. A self-installing executable is what most users > prefer.

Re: Patch 7.4.970

Tony Mechelynck schrob am Sonntag, 13. Dezember 2015 um 01:22 Zeit: > In particular I've > heard that you should use MinGW directly rather than the MinGW > compiler included with Cygwin Both are horribly outdated though, and both require a simulated POSIX layer. I prefer the Visual Studio

Re: Patch 7.4.970

Bram Moolenaar schrob am Samstag, 12. Dezember 2015 um 21:32 Zeit: > I'm thinking about it. Especially for MS-Windows, the version provided > from the ftp site is quite old. Why not just add a link to up-to-date third-party builds (like mine, cough)? -- -- You received this message from the

Random Racket Ramblings

So, trying to compile Vim with MZSCHEME/DYN technically works even with Racket 6.2. The problem is that "raco ctool" has been removed from Racket 5.2 (!) in 2011, so this will fail (if_mzsch.c): > /* need to put it here for dynamic stuff to work */ > #if defined(INCLUDE_MZSCHEME_BASE) > # include

Re: MzScheme support on Windows is broken

KF Leong schrob am Freitag, 9. Oktober 2015 um 09:46 Zeit: > If MZSCHEME includes spaces, somehow the compilation fails... My first patch fixes this, but I still get "C not defined" ... :-( -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the

Re: MzScheme support on Windows is broken

That does NOT work for me, I compile my Vim with VS2010... Why doesn't it work with the default Racket distribution? -- -- 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

Re: MzScheme support on Windows is broken

^ OK, I get the same problems with a VC2010 build of Racket. :-( Help? -- -- 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 --- You received this message

Re: MzScheme support on Windows is broken

tux. schrob am Freitag, 25. September 2015 um 01:20 Zeit: > I tried to compile Vim with Racket (Make_mvc.mak) and Visual Studio > 2010. However, it seems that somewhere the path is not properly > escaped. > Racket is installed to C:\Program Files (x86)\Racket, I set LIBRACKET >

Re: MzScheme support on Windows is broken

*bump* -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group.

Re: MzScheme support on Windows is broken

Attached is what I have yet. However, it still fails to compile; but at least it finds my libraries yet. Any help? -- -- 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

MzScheme support on Windows is broken

I tried to compile Vim with Racket (Make_mvc.mak) and Visual Studio 2010. However, it seems that somewhere the path is not properly escaped. Racket is installed to C:\Program Files (x86)\Racket, I set LIBRACKET to the correct version (3m_9yeyy0 currently, this is also a part of the library's file

Re: [vim] Qt interface (#429)

Why is that so much work at all? I thought such a GUI would easily be possible by just adding buttons which send keystrokes to the underlying unmodified Vim...? Am 22. September 2015 12:20:18 MESZ, schrieb Christian Brabandt : >That is very unlikely to happen

Re: Mail from Vim Github Repository

Christian Brabandt schrob am Dienstag, 25. August 2015 um 19:26 Zeit: Did you run hg pull -u? Yes, but it did not change a thing. -- However, I (seem to) have found my mistake: I had local changes, mostly leftovers from the old repository. Thanks, I seem to have the right versions now. BTW:

[patch] Compiler warning for MSVC compilers with +sniff

Seems to work. -- -- 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 --- You received this message because you are subscribed to the Google Groups vim_dev

Re: Mail from Vim Github Repository

BTW: Having my local hg repository set to Bitbucket and typing hg pull does *not* pull the newest tags, it's still at 7.4.826 for me :/ -- -- 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

Re: Vim is moving from Google Code to Github

You should have mentioned the Hg mirrors too. :) -- -- 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 --- You received this message because you are subscribed

Re: Moving to github

Sorry, I lost track. Which Bitbucket repository is the current one? I found one by ZyX_I ...? tux. -- -- 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

Re: Moving to github

I'd like to stick with Mercurial, so yes, I'll use it. -- -- 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 --- You received this message because you are

Re: [patch] Fix missing, unnecessary symbol lookups with lua = 5.3

Patch looks ok, updated my Windows builds as requested by some of you: http://tuxproject.de/projects/vim Thanks :-) -- -- 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

Replace MzScheme by something newer

Vim has (in theory) had support for MzScheme for a while now; still, as MzScheme is dead (integrated in the new language Racket), it could be appropriate to replace MzScheme support by something different. While Racket seems to be the logical replacement, I'd go with a more common Lisp dialect

Re: Patch 7.4.705

Bram Moolenaar schrob am Dienstag, 21. April 2015 um 15:25 Zeit: Patch 7.4.705 Problem:Can't build with Ruby 2.2. Hmm. if_ruby.obj : error LNK2001: Nicht aufgelöstes externes Symbol _rb_gc_writebarrier_unprotect_promoted. msvc 2010. -- -- You received this message from the vim_dev

Re: Moving to GitHub: painless way to migrate local repository?

^ I'd like that! -- -- 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 --- You received this message because you are subscribed to the Google Groups vim_dev

Moving to GitHub: painless way to migrate local repository?

Given that I have a local copy of the Vim hg repository which includes some local source patches: What's the recommended way to switch to the GitHub repository? (Meh, git ...) Regards. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text

Re: Issue 341 in vim: Google Code will close

The big majority disagrees. Am 14. März 2015 05:01:12 MEZ, schrieb v...@googlecode.com: Status: New Owner: Labels: Type-Defect Priority-Medium New issue 341 by prfl...@gmail.com: Google Code will close https://code.google.com/p/vim/issues/detail?id=341

Re: New Icon for Windows.

I'll add this icon to my builds (tuxproject.de/projects/vim). Any license or may I just add it? Regards. -- -- 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

Re: Patch 7.4.570

Ken Takata schrob am Mittwoch, 14. Januar 2015 um 23:52 Zeit: Did you set RUBY_VER and RUBY_VER_LONG properly? MSVC 2010, RUBY_VER = 22, RUBY_VER_LONG = 2.2.0: I can reproduce Cesar's error. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below

Re: Dynamic ruby 2.2.0 broken

Works with MSVC. -- -- 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 --- You received this message because you are subscribed to the Google Groups vim_dev

Re: Patch 7.4.410

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am 19. August 2014 16:13:36 MESZ, schrieb Bram Moolenaar b...@moolenaar.net: Those numbers are for major and minor releases, not patchlevels. Why does 7.4.410 still identify as 7.4.280 then? I guess in most OSs it doesn't matter, but Windows

Re: Patch 7.4.410

Is there any reason VIM_VERSION_BUILD is never increased beyond 280? -- -- 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 --- You received this message

Re: Patch 7.4.399

I get a pretty lot of unresolved symbols with this build. (MSVC 2010) ex_docmd.obj : error LNK2001: Nicht aufgelöstes externes Symbol _crypt_get_key. fileio.obj : error LNK2001: Nicht aufgelöstes externes Symbol _crypt_encode_alloc. fileio.obj : error LNK2001: Nicht aufgelöstes externes

Re: Patch 7.4.401

Seems to work now. Thanks! :-) -- -- 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 --- You received this message because you are subscribed to the Google

Re: Why does Vim still have vi-compatibility mode?

Dmitry Frank schrob am Donnerstag, 29. Mai 2014 um 11:50 Zeit: and I can't really understand why developers keep it so carefully. What's wrong with that? If you don't want that, use NeoVim or something. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your

Re: [PATCH] Fix compilation failure with Ruby 2.1.0

Bram Moolenaar schrob am Sonntag, 2. Februar 2014 um 13:52 Zeit: Thanks. I would appreciate a few people verifying this patch works fine with different Ruby versions. My Windows builds work fine with this alternate patch:

Compatibility issue: Can't compile Vim with Ruby 2.1.0

Ruby 2.0.0 (MSVC x86) perfectly works - Ruby 2.1.0 (MSVC x86) throws errors: http://i.imgur.com/LAYVavM.png Any clues? -- -- 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

Re: ActivePerl 5.18.1 fails to compile

Cesar Romani schrob am Freitag, 29. November 2013 um 06:00 Zeit: libperl518.a needs to be added on the link line. Does that also solve the MSVC issue? -- -- 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

Re: ActivePerl 5.18.1 fails to compile

Well, so is there a recent Perl distribution for use with MSVC? :( -- -- 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 --- You received this message because

Re: ActivePerl 5.18.1 fails to compile

Wow. Looks like it's working. :-) Thank you! -- -- 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 --- You received this message because you are subscribed to

Re: ActivePerl 5.18.1 fails to compile

Konovalov, Vadim schrob am Donnerstag, 28. November 2013 um 07:18 Zeit: Correct solution is to use supported compiler that understand long long, such as mingw. What compiler you're using BTW? MSVC 2010, has never been a problem for all previous ActivePerl versions... Any better solution?

Re: ActivePerl 5.18.1 fails to compile

Konovalov, Vadim schrob am Mittwoch, 27. November 2013 um 06:46 Zeit: I can investigate later today, if you wish. I'd like you to. :) -- -- 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

Re: improving Vim - Kickstarter - brainstorming - goals - who wants to join?

Marc Weber schrob am Montag, 25. November 2013 um 14:26 Zeit: - focus on productivity That's what Vim does. - code reusage That's what's pointless for an editor. jm2c -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are

ActivePerl 5.18.1 fails to compile

Hmm, updated ActivePerl from 5.16.3 to 5.18.1 (yes, also in my compile.bat file); still, compiling if_perl.c fails with more than 100 errors (mostly missing brackets). Anyone who can confirm this? -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below

Re: vim.org website redesign/update

Leonard Ehrenfried schrob am Mittwoch, 6. November 2013 um 22:54 Zeit: I also happen to think that it doesn't do a very good job of explaining what vim is and how to install it. Sorry, but that's wrong IMO. :) -- -- You received this message from the vim_dev maillist. Do not top-post!

Ruby for MSVC?

Hi, I've seen that Ruby 2.0.0 is out. I thought I could include it with my Vim builds. Where can I find a MSVC-compatible version? Ruby itself only supports MingW. -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are replying to.

Vim can't compile with DYNAMIC_TCL and ActiveTcl 8.6.0.0

Weirdly, Vim fails to build with ActiveTcl 8.6.0.0 on MSVC2010, saying _Tcl_FindExecutable is an unresolved symbol...? -- -- 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

Re:

Tony Mechelynck schrob am Montag, 12. August 2013 um 23:27 Zeit: I use the 8.3 name PROGRA~1 instead of the equivalent Program Files or Program Files (x86) so I don't need to bother with spaces in the path (and I don't need quotes). If on your system it's PROGRA~2 or even PROGRA~3, you

Re:

Ah, thanks. I was confused due to the lack of .vcxproj files. -- -- 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 --- You received this message because you

Re: Release date for 7.4 ?

Zdenek Sekera schrob am Freitag, 19. Juli 2013 um 22:40 Zeit: Has the probable release date for 7.4 been set already? When it's done. -- -- 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

Re:

Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 06:53 Zeit: You should already have it. Oh, right, thanks! But why does it still make 7.3? :-/ (I use MS Windows, VS 2010.) -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are

Re:

Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 16:22 Zeit: Are you sure your current changeset (hg log -r . without the quotes) is on the default branch and is a descendant of v7-4a-001? hg tags says 7.4 is current. :-/ The hg up command did not change anything, version.h also says 7.4.

Re:

Tony Mechelynck schrob am Sonntag, 7. Juli 2013 um 16:47 Zeit: Did you install, or at leat run, your new Vim, to see its version? Yup, it's 7.3.some patch. I think it's C:\Program Files\Vim\vim74a or something, NOT ...\vim73 as it used to be. Yep, it is, I manually renamed the folder. But

Re: Patch 7.4a.001

Can I (somehow) rebase my vim73 repository to vim74? -- -- 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 --- You received this message because you are

Re: Patch 7.4a.001

Damn. So I'll have to merge my modifications all manually again? :-/ What's the command to clone vim74 again? -- -- 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

Re: Patch 7.4a.001

Tony Mechelynck schrob am Samstag, 6. Juli 2013 um 20:21 Zeit: hg fetch --switch-parent merges them every time I pull new changes Hmm.. hg: unknown command 'fetch' :-/ -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are

Re: Patch 7.4a.001

Ah, thanks! Now: abort: outstanding uncommitted changes...? -- -- 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 --- You received this message because you

Re: Patch 7.4a.001

I see. I commited my changes (hg commit -m ...), used hg fetch --switch-parent ... how can I pull 7.4 now? -- -- 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

Re: Patch 7.3.1002

What the... Bram is on a spree, eh? :-) -- -- 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 --- You received this message because you are subscribed to the

Re: compiling windows binary using cygwin fails

_MAX_PATH is actually defined (rather exclusively) in Make_cyg.mak (line 438) and reused subsequently. As a quick workaround, you could just specify its actual value. But I'd bet something in the compiler call is wrong for you. -- -- You received this message from the vim_dev maillist. Do not

  1   2   >