Re: Vim + MzScheme on Ubuntu

2007-02-14 Thread A.J.Mechelynck

Alexei Alexandrov wrote:

Hi Bram Moolenaar, you wrote:

I think the best method is to obtain all the files from subversion and
then get the latest runtime files with rsync.  Get spell files manually
(this can be done automatically if you use a language for the first

I tried to use the command given on the site to update Windows 
runtime files:

rsync -avzcP --delete .

It seems to work fine, but the result directory doesn't have spell directory at 
all. Is it bug or feature?

As Bram said earlier, the runtime/dos directory on the ftp site doesn't 
contain any spell files. With --delete, it will delete in the target directory 
tree whatever it doesn't find in the source tree.

If you download the full sources (unix+lang+extra) to some directory (let's 
say %HOME%\build\vim) creating there a tree starting at vim70, you can then 
maintain the runtime files (including the spell files) as follows (in Cygwin 
bash) (untested):

  cd $HOME/build/vim/vim70
  rsync -avzcP --delete --exclude=\dos\ ./runtime
  cd src
  export CONF_ARGS='--with-global-runtime=/cygdrive/c/PROGRA~1/vim'
  make config
  make installruntime

You will get runtime files with Unix ends-of-lines, but Vim-for-Windows can 
cope with that (provided that 'fileformats' includes unix, which is the 
default), and so does WordPad. Notepad can't swallow them but I guess you can 
live with that.

Best regards,
Show respect for age.  Drink good Scotch for a change.

Vim crashing while starting nibbles game

2007-02-14 Thread Hari Krishna Dara

After I updated the nibbles game, a user reported that his gvim crashes
while starting the game. He is using gvim on mandriva linux with
patchlevel upto 178. Strangely it doesn't crash on his console vim. I
couldn't reproduce the crash on XP and tried with gvim with patchlevels
148 as well as 191.

Here is the script page if anyone wants to try it and reproduce it:

Can anyone take a look at the below output I received from him and see
if there is any information about the problem?

here is what gvim outputs to the terminal after crashing
$ gvim
Fontconfig error: conf.d, line 1: no element found
[EMAIL PROTECTED] autoload]$ *** buffer overflow detected ***: gvim
terminated === Backtrace: =
=== Memory map: 
08048000-08214000 r-xp  03:05 230449 /usr/bin/gvim
08214000-08221000 rwxp 001cc000 03:05 230449 /usr/bin/gvim
08221000-087ef000 rwxp 08221000 00:00 0  [heap]
b586d000-b5877000 r-xp  03:05
392517 /lib/ b5877000-b5878000 rwxp 9000
03:05 392517 /lib/ b5898000-b58f8000 rwxs
 00:07 17039409   /SYSV (deleted) b58f8000-b58fe000
r-xp  03:05
344455 /usr/lib/gtk-2.0/2.10.0/loaders/
b58fe000-b58ff000 rwxp 5000 03:05
344455 /usr/lib/gtk-2.0/2.10.0/loaders/
b58ff000-b5ada000 r-xp  03:05
247080 /usr/share/icons/hicolor/icon-theme.cache b5ada000-b60f4000
r-xp  03:05 246307 /usr/share/icons/gnome/icon-theme.cache
b60f4000-b6102000 r-xp  03:05
377519 /usr/share/icons/Clearlooks/icon-theme.cache
b6102000-b6107000 r-xp  03:05
245343 /usr/share/locale/en_GB/LC_MESSAGES/
b6107000-b6118000 r-xp  03:05
396368 /usr/share/fonts/TTF/Vera.ttf b6118000-b611c000 r-xp
347050 /usr/lib/gtk-2.0/2.10.0/loaders/
b611c000-b611d000 rwxp 3000 03:05
347050 /usr/lib/gtk-2.0/2.10.0/loaders/
b611d000-b6131000 r-xp  03:05
299599 /usr/X11R6/lib/X11/fonts/drakfont/Type1/ProggySmall.pfb
b6131000-b6133000 r-xp  03:05
278892 /usr/lib/pango/1.6.0/modules/
b6133000-b6134000 rwxp 1000 03:05
278892 /usr/lib/pango/1.6.0/modules/
b6134000-b614 r-xp  03:05
392916 /usr/lib/gtk-2.0/2.10.0/engines/
b614-b6141000 rwxp c000 03:05
392916 /usr/lib/gtk-2.0/2.10.0/engines/
b6141000-b6147000 r-xp  03:05
246576 /usr/share/locale/en_GB/LC_MESSAGES/
b6147000-b614e000 r-xp  03:05
246849 /usr/share/locale/en_GB/LC_MESSAGES/
b614e000-b627a000 rwxp b614e000 00:00 0 b627a000-b627b000 r-xp 
03:05 229160 /usr/lib/gconv/ b627b000-b627d000 rwxp
 03:05 229160 /usr/lib/gconv/ b627d000-b6285000
r-xp  03:05 397071 /lib/
b6285000-b6287000 rwxp 8000 03:05
397071 /lib/ b6287000-b62a7000 r-xp 
249891 /usr/share/locale/en_GB/LC_MESSAGES/
b62a7000-b62ae000 r-xs  03:05
230370 /usr/lib/gconv/gconv-modules.cache b62ae000-b62e r-xp
 03:05 163875 /usr/share/locale/ISO-8859-1/LC_CTYPE
b62e-b62e1000 ---p b62e 00:00 0 b62e1000-b6ae5000 rwxp b62e1000
00:00 0 b6ae5000-b6b03000 r-xp  03:05
229513 /usr/lib/ b6b03000-b6b05000 rwxp 0001e000
03:05 229513 /usr/lib/ b6b05000-b6b0a000 r-xp
 03:05 237405 /usr/lib/ b6b0a000-b6b0b000
rwxp 4000 03:05 237405 /usr/lib/
b6b0b000-b6b0d000 r-xp  03:05
229771 /usr/lib/ b6b0d000-b6b0e000 rwxp 1000
03:05 229771 /usr/lib/ b6b0e000-b6b0f000 rwxp
b6b0e000 00:00 0 b6b0f000-b6b14000 r-xp  03:05
397055 /lib/ b6b14000-b6b16000 rwxp 4000 03:05
397055 /lib/ b6b16000-b6b3d000 rwxp b6b16000 00:00 0
b6b3d000-b6b4d000 r-xp  03:05 397064 /lib/
b6b4d000-b6b4f000 rwxp 0001 03:05 397064 /lib/
b6b4f000-b6b51000 rwxp b6b4f000 00:00 0 b6b51000-b6b55000 r-xp 
03:05 425586 /lib/ b6b55000-b6b56000 rwxp 3000
03:05 425586 /lib/ b6b56000-b6b64000 r-xp 
03:05 397083 /lib/ b6b64000-b6b66000 rwxp e000
03:05 397083 /lib/ b6b66000-b6b68000 rwxp b6b66000
00:00 0 b6b68000-b6b77000 r-xp  03:05
232189 /usr/lib/ b6b77000-b6b78000 rwxp
e000 03:05 232189 /usr/lib/
b6b78000-b6b79000 rwxp b6b78000 00:00 0 b6b79000-b6b84000 r-xp 
03:05 229248 

Subject: Re: vim on cygwin using win32 clipboard

2007-02-14 Thread Bram Moolenaar

Frodak Baksik wrote:

 I realized that I forgot to update the dependency data for winclip.c
 in makefile.  The following is a patch after vim_patch.diff is
 Index: Makefile


 Also, is there anything I can do to help get the original patch accepted?

Ask a few people to try it out and report their results here.

Support your right to bare arms!  Wear short sleeves!

 /// Bram Moolenaar -- [EMAIL PROTECTED] --   \\\
///sponsor Vim, vote for features -- \\\
\\\download, build and distribute --
 \\\help me help AIDS victims --

Re: Multiple Opens to Write

2007-02-14 Thread Bram Moolenaar

Bill McCarthy wrote:

 I'm alpha testing software for Windows that archives files
 whenever they are opened for writing.  Testing with Gvim, I
 noticed that the program's log showed multiple open for
 write entries by simply opening a file with Gvim and doing
 a :wq command.
 The author of the software wrote:
 I downloaded Gvim and traced its file writes -- it
 actually is opening the file for writing *4* times
 for each save.  (Why, I can't begin to imagine, but
 it's the sort of thing you get when you port between
 various OS's without redoing the code.)
 I've made some changes to build 6 so that it will
 only archive it  log it once, ignoring the
 Why isn't opening the file for writing just once good

Well, look in the source code: src/fileio.c, search for open(.  Isn't
at least one of the writes for the backup file?

Would you care for a drink?   I mean, if it were, like,
disabled and you had to look after it?

 /// Bram Moolenaar -- [EMAIL PROTECTED] --   \\\
///sponsor Vim, vote for features -- \\\
\\\download, build and distribute --
 \\\help me help AIDS victims --

Re: RFC: use hunspell dictionaries

2007-02-14 Thread Bram Moolenaar

Karsten Hopp wrote:

 Caolan McNamara wrote a patch for vim-7 to use hunspell dictionaries directly.
 This allows us to use one single set of dictionaries for OpenOffice, maybe 
 and vim.
 Please have a look at his comments at
 and at the patch available at
 Comments welcome, either here on this list or in the bugzilla.

Interesting idea.

It appears it doesn't handle words with non-words characters in them.

Would be a good idea to compare, both the quality and speed, for
checking and making suggestions.  Especially for more complicated

The patch is crude, has a few hard-coded paths and hardly any comments,
but it's good for trying it out.

.signature 4 lines, 50 characters written

 /// Bram Moolenaar -- [EMAIL PROTECTED] --   \\\
///sponsor Vim, vote for features -- \\\
\\\download, build and distribute --
 \\\help me help AIDS victims --

RE: Win64-related patches

2007-02-14 Thread Michael Wookey
 Michael Wookey wrote:
   One bug that I didn't fix. Build gvim.exe with OLE=no, run 'gvim -
   and watch it crash while trying to display an error message.
  This seems to fix the bug...
  Index: src/message.c
  --- src/message.c   (revision 212)
  +++ src/message.c   (working copy)
  @@ -2987,7 +2987,7 @@
* If 'verbosefile' is set write message in that file.
* Must come before the rest because of updating msg_col.
  -if (*p_vfile != NUL)
  +if (p_vfile  *p_vfile != NUL)
  verbose_write(s, maxlen);
   if (redir_fd != NULL
  Index: src/misc2.c
  --- src/misc2.c (revision 212)
  +++ src/misc2.c (working copy)
  @@ -1748,7 +1748,7 @@
  return NULL;
  -while ((b = *p) != NUL)
  +while (p  (b = *p) != NUL)
  if (b == c)
  return p;
 Well, that may fix it, but the problem is that the order of
 initializations is violated.  Normally all option pointers are not
 What is the message that triggers this problem?  That message should
 probably be changed to mch_errmsg().

The actual error message wrapper is src/gui_w32:ole_error() which just
wraps EMSG2().  When calling gvim -register, the error propagates from

I agree that the above patch fixes the symptom of the bug, but not the
true cause.