Gvim with mzscheme
John Sampson
I have been looking for a precompiled version of Vim for Microsoft Windows
with extension to allow Scheme code to be included in the same way as
Python code
is in the available Windows precompiled version. I believe it is
intended to be possible
for Vim to be compiled this way.
Is a precompiled version available anywhere?
Regards
_John Sampson_
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4251 (20090716) __________
The message was checked by ESET NOD32 Antivirus.
John Beckett
> I have been looking for a precompiled version of Vim for
> Microsoft Windows with extension to allow Scheme code to be
> included in the same way as Python code is in the available
> Windows precompiled version.
I have never tried it, but I believe that what it says at
the following is correct (MzScheme is available):
http://vim.wikia.com/wiki/Download
John
Tony Mechelynck
>
> Hello -
>
> I have been looking for a precompiled version of Vim for Microsoft Windows
> with extension to allow Scheme code to be included in the same way as
> Python code
> is in the available Windows precompiled version. I believe it is
> intended to be possible
> for Vim to be compiled this way.
>
> Is a precompiled version available anywhere?
>
> Regards
>
> _John Sampson_
For Windows there is. Steve Hall's bugfixed Vim distribution for Windows
(currently at patchlevel 7.2.228) includes almost everything that one
could wish for, including executables with and without GUI, and compiled
with (among others) +mzscheme/dyn +perl/dyn +python/dyn +ruby/dyn
+tcl/dyn. See its ":version" text at
https://sourceforge.net/project/shownotes.php?group_id=43866&release_id=696157
and/or download it from the "gvim 7.2.228.exe" link at
https://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721
This build, however, only has "Normal" features. This means that it
lacks (for instance) profiling, RTL editing, and keymaps. If you need
these, you will either have to compile Vim yourself (see my Compiling
HowTo for Windows at
http://users.skynet.be/antoine.mechelynck/vim/compile.htm ). Older
builds from the URL above have Big or Huge features, but without +mzscheme.
Best regards,
Tony.
--
If the American dream is for Americans only, it will remain our dream
and never be our destiny.
-- René de Visme Williamson
Steve Hall
>
> For Windows there is. Steve Hall's bugfixed Vim distribution for
> Windows (currently at patchlevel 7.2.228) includes almost everything
> that one could wish for, including executables with and without GUI,
> and compiled with (among others) +mzscheme/dyn +perl/dyn +python/dyn
> +ruby/dyn +tcl/dyn. See its ":version" text at
> https://sourceforge.net/project/shownotes.php?group_id=43866&release_id=696157
> and/or download it from the "gvim 7.2.228.exe" link at
> https://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721
>
> This build, however, only has "Normal" features. This means that it
> lacks (for instance) profiling, RTL editing, and keymaps. If you
> need these, you will either have to compile Vim yourself (see my
> Compiling HowTo for Windows at
> http://users.skynet.be/antoine.mechelynck/vim/compile.htm ). Older
> builds from the URL above have Big or Huge features, but without
> +mzscheme.
I've just uploaded a new 7.2.234 that uses the "HUGE" feature build.
(After yet another new box setup, configuration, test process.)
--
Steve Hall [ digitect dancingpaper com ]
Tony Mechelynck
Ah, great. Well, John, the ":version" URL has changed but you can get at
it by clicking the rightmost icon (which says "Release notes" at
mouseover) on the "vim" line near the bottom of the download page.
Best regards,
Tony.
--
Major Premise: Sixty men can do a piece of work sixty times as quickly
as one man.
Minor Premise: One man can dig a posthole in sixty seconds.
Conclusion: Sixty men can dig a posthole in one second.
-- Ambrose Bierce, "The Devil's Dictionary"
John Beckett
> I've just uploaded a new 7.2.234 that uses the "HUGE" feature
> build. (After yet another new box setup, configuration, test
> process.)
Steve: Thanks for the valuable service you provide for Windows
users.
I'm wondering how we at the Vim Tips wiki can provide clear
advice to users about how to download the different versions
("Vim with Cream" and "Vim without Cream")?
This page is probably a bit confusing for those not familiar
with the system:
http://sourceforge.net/projects/cream/files/
Currently there are three sections labelled:
- Newest Files
- Cream
- Vim
I think some extra text would be useful to clarify. Perhaps:
- Newest Files
- Cream (Vim with Cream)
- Vim (standard Vim without Cream)
Also, in the overview at the top of the page, you might add:
---start---
Files on this page are for Microsoft Windows.
Files named "cream-xxx" provide Vim with Cream.
Files named "gvim-xxx" provide standard Vim without Cream.
With scripting enabled in your browser, click "+" to expand a
section to see the available files.
---end---
Following is what the Vim Tips wiki currently says for your two
downloads. I guess the URL for standard Vim should be changed to
the files URL above. Do you want any other changes?
http://vim.wikia.com/wiki/Download
---start extract---
Which version of Vim should I use?
* I want a fully patched standard Vim for Windows,
without compiling it myself.
Use Cream's "standard" Vim (this is easiest and best for Windows
users on 32-bit systems).
http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721
* I want Vim configured like Notepad for Windows.
See the Cream versions at http://cream.sourceforge.net/download.html
---end---
John
Steve Hall
>
> I'm wondering how we at the Vim Tips wiki can provide clear
> advice to users about how to download the different versions
> ("Vim with Cream" and "Vim without Cream")?
>
> This page is probably a bit confusing for those not familiar
> with the system:
> http://sourceforge.net/projects/cream/files/
Unfortunately, I do not believe there is a way to edit the SF.net
files pages. They are dynamically generated from the project and files
in the download system and some limited metadata associated with each.
There is no way that I know to provide separate pages for the two
different file strains.
> Following is what the Vim Tips wiki currently says for your two
> downloads. I guess the URL for standard Vim should be changed to the
> files URL above. Do you want any other changes?
> http://vim.wikia.com/wiki/Download
>
> ---start extract---
> Which version of Vim should I use?
> * I want a fully patched standard Vim for Windows,
> without compiling it myself.
>
> Use Cream's "standard" Vim (this is easiest and best for Windows
> users on 32-bit systems).
> http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721
>
> * I want Vim configured like Notepad for Windows.
>
> See the Cream versions at http://cream.sourceforge.net/download.html
> ---end---
I'm not sure how to clarify this on the SF.net download page, which is
why I always direct users to your last URL above, the Cream Download
page.
The SF files system (the entire project system actually) has changed
so many times since I started this project that I finally tired of
maintaining links to specific files and keeping the HTML updated. At
one point, it was possible to link to specific file sets, but their
latest shiny version apparently removed this functionality.
About the best that could be done now is to link directly to specific
files, like:
http://sourceforge.net/projects/cream/files/Vim/gvim-7-2-234.exe/download
But these change pretty frequently. If someone really wanted to keep
the Wiki up to date, they should sign up to monitor the package's
releases.
About the only thing I might change on the Wiki page is the reference
to Notepad, I doubt anybody on Windows needs that. :)
KF Leong
> (After yet another new box setup, configuration, test process.)
I am been wondering if possible for your distribution to include the
updated runtime files?
Rgds,
KF
Tony Mechelynck
AFAIK, Steve's distributions have always included runtime files updated
to the date-time of building.
Best regards,
Tony.
--
There was a young lady of Norway
Who hung by her toes in a doorway.
She said to her beau
"Just look at me Joe
I think I've discovered one more way."
John Beckett
> Unfortunately, I do not believe there is a way to edit the
> SF.net files pages. They are dynamically generated from the
> project and files in the download system and some limited
> metadata associated with each.
OK, thanks for explanation.
I don't want to link to an individual file, so I'll think about
some way of wording the wiki so it doesn't need to be updated.
> About the only thing I might change on the Wiki page is the
> reference to Notepad
Please suggest some short alternative wording.
http://vim.wikia.com/wiki/Download
currently says this for Cream:
I want Vim configured like Notepad for Windows.
The text used to read:
I am very comfortable with the Windows way
of doing things (CUA).
Possible text:
I want an easy-to-use configuration with common menus
and standard keyboard shortcuts.
John
Steve Hall
>
> I don't want to link to an individual file, so I'll think about
> some way of wording the wiki so it doesn't need to be updated.
Perhaps someone here knows how to point to specifically to SF.net
packages, rather than an entire project's files?
> > About the only thing I might change on the Wiki page is the
> > reference to Notepad
>
> Please suggest some short alternative wording.
[...]
>
> Possible text:
> I want an easy-to-use configuration with common menus
> and standard keyboard shortcuts.
I like that. It's obviously subjective (nearly OT here), but I think
makes sense in the larger context of potential text editor users.
KF Leong
> to the date-time of building.
>
files from the FTP, e.g. plugin/netrwPlugin.vim, version is dated Aug
01, 2008, whereas on the FTP site, it is dated Aug 10, 2008, and
numerous others since updated.
It is minor but ... :)
Rgds,
KF
Steve Hall
>
> The newest build (7.2.238) from Steve does not include updated
> runtime files from the FTP, e.g. plugin/netrwPlugin.vim, version is
> dated Aug 01, 2008, whereas on the FTP site, it is dated Aug 10,
> 2008, and numerous others since updated.
>
> It is minor but ... :)
The build script automatically builds from the default Vim .tbz, lang,
and extra tarballs and then updates from the FTP site. (In case anyone
is interested in the details, our build script is licensed under the
GPL and available here:
http://cream.cvs.sourceforge.net/viewvc/cream/misc/vim-build.bat )
This process favors automation and repeatability, so there are no
humans checking timestamps to verify version problems. Since our build
machine was just re-built from scratch, it appears to me that there
may be file date/version problems between the Vim sources and the FTP
site. We've had problems with this before, particularly related to
netrw, can any of the file/FTP site maintainers comment?
Tony Mechelynck
I stand corrected.
Best regards,
Tony.
--
Is your job running? You'd better go catch it!
Tony Mechelynck
You're building using Cygwin, aren't you? Maybe you could keep your
runtimes up-to-date by rsync (if Cygwin has a version of that program)?
The script I use for that on Linux is
#!/bin/bash
date
rsync -avzcP --delete --exclude="/dos/" \
ftp.nluug.nl::Vim/runtime/ ./runtime/ 2>&1 | tee rsync.log
vim -es -u NONE -c '%s/^.*\r//' -cx rsync.log
(the last line because rsync uses CR without LF to overwrite its
"progress report" on the terminal). It is meant to be run after cd'ing
to the top vim72 directory, parent of runtime/ src/ etc. You may or may
not want to change some of the options.
Best regards,
Tony.
--
People will do tomorrow what they did today because that is what they
did yesterday.
Steve Hall
>
> You're building using Cygwin, aren't you? Maybe you could keep your
> runtimes up-to-date by rsync (if Cygwin has a version of that
program)?
Rsync does not work for me due to firewall issues. But I use wget -N
which should at least bring down the updated files, if not remove the
ones no longer necessary. (This isn't the problem is it?)