Announcing: Vim (Vi IMproved) version 5.6
Author: Bram Moolenaar et al.
Announcement
------------
This is a bug-fix release of Vim. Since version 5.5 bugs have been fixed and
a few improvements have been made.
Vim 5.6 has been tested by quite a few people over the past weeks, and there
are no big changes since version 5.5. This should be the most stable Vim
version ever. But it's free software, the usual disclaimers apply.
What is Vim?
------------
Vim is an almost 100% compatible version of the UNIX editor Vi. Many new
features have been added: Multi level undo, syntax highlighting, command line
history, filename completion, block operations, etc. Those who don't know Vi
can probably skip this message, unless you are prepared to learn something new
and useful. Vim is especially recommended for editing programs.
Vim runs on almost any Unix flavor, MS-DOS, MS-Windows 3.1, MS-Windows
95/98/NT, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and Amiga.
For more information, see "http://www.vim.org".
New since version 5.5
---------------------
Not much:
- New "Edit with Vim" popup menu entry for MS-Windows. Avoids problems with
the MS Office taskbar.
- 18 new syntax files.
- "z+" and "z^" commands.
And many bug fixes! This version is aimed at stability.
See ":help version-5.6" in Vim for the details.
Where to get it
---------------
You can find a list of distribution sites at
ftp://ftp.vim.org/pub/vim/MIRRORS
Suggested locations:
ftp://ftp.<country>.vim.org/pub/vim/
ftp://ftp.vim.org/pub/vim/
Replace <country> with a country code, e.g.:
ftp://ftp.us.vim.org/pub/vim/
What is available
-----------------
Note that for all systems the distribution is split into an archive with
runtime files (documentation, syntax files, etc.) and a binary and/or source
archive. You should download at least two archives!
FILE SYSTEM COMMENTS
unix/vim-5.6-src.tar.gz Unix(*) Sources.
unix/vim-5.6-rt.tar.gz Unix(*) Runtime files.
extra/vim-5.6-extra.tar.gz Unix(*) Extra sources and docs (Farsi, OLE, VisVim).
unix/vim-5.5-5.6-rt.diff.gz Runtime diff with version 5.5.
unix/vim-5.5-5.6-src.diff.gz Sources diff with version 5.5.
extra/vim-5.5-5.6-extra.diff.gz Extra diff with version 5.5.
pc/vim56rt.zip Win32 MS-DOS and MS-Windows runtime files.
pc/gvim56.zip Win32 32 bit MS-Windows 95/98/NT GUI binaries.
Recommended for MS-Windows 95/98/NT.
The best choice for syntax highlighting and
speed.
pc/gvim56ole.zip Win32 32 bit MS-Windows 95/98/NT GUI binaries,
with OLE support and VisVim.
pc/gvim56_s.zip Win32s 32 bit MS-Windows 3.1/3.11 GUI binaries.
Requires Win32s.
pc/vim56w32.zip Win32 32 bit MS-Windows 95/98/NT console binaries.
Recommended for Windows NT, NOT for 95/98.
Supports long file names.
pc/vim56d32.zip MS-DOS 32 bit protected mode binaries.
Recommended for MS-DOS, MS-Windows 3.1 and
MS-Windows 95/98 console. It is compiled
with DJGPP, it may need a DPMI driver
(CWSDPMI is included). Supports long file
names on MS-Windows 95/98 (NOT on NT).
pc/vim56d16.zip MS-DOS 16 bit real mode binaries.
Runs on most MS-DOS systems, but is
restricted to using 640K memory. Small
version, without e.g., syntax highlighting
and autocommands.
pc/vim56src.zip PC Sources for PC versions (with CR-LF).
os2/vim56rt.zip OS/2 Runtime files (same as for PC).
os2/vim56os2.zip OS/2 Binaries.
(use the Unix+extra archives for sources)
amiga/vim56rt.tgz Amiga Runtime files.
amiga/vim56bin.tgz Amiga Binaries.
amiga/vim56big.tgz Amiga Binaries with more features.
amiga/vim56src.tgz Amiga Sources for Amiga.
doc/vim56html.zip all Documentation converted to HTML.
patches/* all Recent patches.
(*) Also for BeOS, OS/2, VMS, Macintosh and Atari MiNT
The contents of the source archives depends on the specified system. To
obtain the full sources and docs, get the three Unix archives.
system file type Unpack with
Unix file.tar.gz gunzip file.tar.gz; tar xf file.tar
Amiga file.tgz gzip -d file.tgz; tar xf file.tar
PC file.zip pkunzip -d file.zip
or: unzip file.zip
Mailing lists
-------------
For user questions you can turn to the Vim mailing list. There are a lot of
tips, scripts and solutions. You can ask your Vim questions, but only if you
subscribe. See http://www.vim.org/mail.html. An archive is kept at
http://www.egroups.com/group/vim.
If you want to help developing Vim or get the latest patches, subscribe to the
vim-dev mailing list. An archive is kept at
http://www.egroups.com/group/vimdev.
Subject specific lists:
Multi-byte issues: vim-multibyte http://www.egroups.com/group/vim-multibyte
Macintosh issues: vim-mac http://www.egroups.com/group/vim-mac
Reporting bugs
--------------
Send them to <Bram@...>. Please be brief, all the time spent on answering
mail is subtracted from the time that is spent on improving Vim! Always give
a reproducable example and try to find out which settings or other things
influence the appearance of the bug. Try different machines if possible. See
":help bugs" in Vim. Send me patches if you can!
If something needs discussing with other developers, send a message to the
vim-dev mailing list. You need to subscribe first.
Happy Vimming!
--
hundred-and-one symptoms of being an internet addict:
195. Your cat has its own home page.
--/-/---- Bram Moolenaar ---- Bram@... ---- Bram@... ---\-\--
\ \ www.vim.org/iccf www.moolenaar.net www.vim.org / /
Taro Muraoka wrote:
> It works very good. Thank you Bram for fix.
>
> First two locations were made by me Taro Muraoka. And I had forgot to think
> about 8-bit character. Second two were originated by other. He probably
> thought IsLeadByte() is very high cost and this code is not needed for UNIX's
> encoding EUC. Multibyte of EUC consist of 0x80-0xFF, but multibyte of
> Shift-JIS consist of 0x40-0xFF.
Thanks for checking. I have included these fixes. I didn't include the one
for the regexp code yet, I'll do that later.
IsLeadByte() isn't high cost, but IsTrailByte() is, because it starts looking
at the start of the string.
This multi-byte code is really two-byte code. For Vim 6.0 we will have to
change it all drastically to support UTF-8. Perhaps the multi-byte codes that
are supported until now can be converted to UTF-8? The main advantage will be
that you can edit two buffers with different encoding at the same time.
--
hundred-and-one symptoms of being an internet addict:
193. You ask your girlfriend to drive home so you can sit back with
your PDA and download the information to your laptop
--/-/---- Bram Moolenaar ---- Bram@... ---- Bram@... ---\-\--
\ \ www.vim.org/iccf www.moolenaar.net www.vim.org / /
Bram Moolenaar wrote:
> Looks like a good fix. However, I don't see why is_dbcs isn't tested in the
> first two locations, and specifically compared to DBCS_JPN in the second two.
>
> Also, I don't understand why the second two should only be used for Win32.
> Wouldn't they be required for all systems?
>
> Please consider this change instead:
>
> *** ../vim-5.6a.28/src/search.c Wed Dec 29 12:11:01 1999
> --- src/search.c Sat Jan 15 21:12:19 2000
:
:
(omit)
It works very good. Thank you Bram for fix.
First two locations were made by me Taro Muraoka. And I had forgot to think
about 8-bit character. Second two were originated by other. He probably
thought IsLeadByte() is very high cost and this code is not needed for UNIX's
encoding EUC. Multibyte of EUC consist of 0x80-0xFF, but multibyte of
Shift-JIS consist of 0x40-0xFF.
----
Taro Muraoka mailto:koron@...
Bram Moolenaar wrote:
> I suspect this can cause problems when using 8-bit characters in a menu. I
> think it's better to use is_dbcs here, even though that's actually for buffer
> text. How about this patch instead:
>
> *** ../vim-5.6a.28/src/menu.c Mon Dec 20 09:59:12 1999
> --- src/menu.c Sat Jan 15 21:24:15 2000
> ***************
> *** 1010,1021 ****
> --- 1010,1027 ----
> char_u *p;
>
> for (p = name; *p && *p != '.'; p++)
> + {
> if (*p == '\\' || *p == Ctrl('V'))
> {
> mch_memmove(p, p + 1, STRLEN(p));
> if (*p == NUL)
> break;
> }
> + #ifdef MULTI_BYTE
> + else if (is_dbcs && IsLeadByte(*p) && p[1] != NUL)
> + ++p; /* skip multibyte char */
> + #endif
> + }
> if (*p)
> *p++ = NUL;
> return p;
Yes, indeed to use is_dbcs is better way. But there is one very very small
problem and question. If multibyte menu user did not set 'fileencoding' before
menu.vim was loaded, buffer would be initialized wrong. In this case user lose
all chances to correct this. Menu is not updated, even if user type ":set
fe=japan" in vim session.
Of cource it is one easy solution that distribute multibyte menu.vim with a
comment "WARNING: Do not forget to set 'fileencoding' option in your _vimrc.
Just add line 'set fe=japan' in your _vimrc". Anoter way, at top of multibyte
menu.vim distribute, add "set fe=japan". Or is there any good way to reload
menu buffer?
Post script...
Screen shot of gVim with Japanese menu is available here.
http://ixeris.bios.ics.saitama-u.ac.jp/~koron/software/img/gvim-5.6a.21-00.gif
----
Taro Muraoka koron@...
----
Taro Muraoka mailto:koron@...
Taro Muraoka wrote:
> -Regular expression search and substitute. (16K)
> Please test.
I'm glad Taro looked into this and made a patch.
One question, like with the other ones: Doesn't is_dbcs need to be used here?
--
hundred-and-one symptoms of being an internet addict:
189. You put your e-mail address in the upper left-hand corner of envelopes.
--/-/---- Bram Moolenaar ---- Bram@... ---- Bram@... ---\-\--
\ \ www.vim.org/iccf www.moolenaar.net www.vim.org / /
Hello Vimmers,
I have created a desktop calendar for the year 2000, with some info about Vim
and ICCF Holland on the back. Useful, and may attract some attention at the
same time. It also has my Christmas and new year wishes on the bottom.
There are six files available (in .zip format to reduce the size):
Nederlands, A4, Corel Draw Nederlands, A4, PostScript
English, A4, Corel Draw English, A4, PostScript
English, Letter, Corel Draw English, Letter, PostScript
With the GhostScript program you can print the PostScript version on almost
any printer. It looks better on a color printer.
You can find it at: http://www.moolenaar.net
You are allowed to change it and pass on the modified version.
I wish you all a merry Christmas and a Vimmy 2000!
- Bram
--
The Characters and incidents portrayed and the names used are fictitious and
any similarity to the names, characters, or history of any person is entirely
accidental and unintentional.
Signed RICHARD M. NIXON
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
--/-/---- Bram Moolenaar ---- Bram@... ---- Bram@... ---\-\--
\ \ www.vim.org/iccf www.moolenaar.net www.vim.org / /
Taro Muraoka wrote:
> I made some patches for multibyte.
> May I post these patches to here?
>
> list of pathes
> -Regular expression search and substitute. (16K)
> -Simple search in search.c. (2K)
> -Special multibyte character cannot be used in menu. (1K)
I would welcome sending small patches to vim-multibyte. This gives
subscribers a chance to say something about them, which helps me to decide if
they should be included.
Your patch for multibyte characters in a menu is probably the one that
resulted in patch 5.6a.028:
*** ../vim-5.6a.27/src/gui_w32.c Wed Jan 12 21:20:04 2000
--- src/gui_w32.c Fri Jan 14 20:14:43 2000
***************
*** 5014,5019 ****
--- 5014,5032 ----
{
int nChar = 0;
+ #ifdef MULTI_BYTE
+ int len = lstrlen(lpAnsiIn) + 1; /* include NUL character */
+ int i;
+
+ nChar = MultiByteToWideChar(
+ CP_OEMCP,
+ MB_PRECOMPOSED,
+ lpAnsiIn, len,
+ lpWCStr, len);
+ for (i = 0; i < nChar; ++i)
+ if (lpWCStr[i] == (WORD)'\t') /* replace tabs with spaces */
+ lpWCStr[i] = (WORD)' ';
+ #else
do
{
if (*lpAnsiIn == '\t')
***************
*** 5022,5027 ****
--- 5035,5041 ----
*lpWCStr++ = (WORD)*lpAnsiIn;
nChar++;
} while (*lpAnsiIn++);
+ #endif
return nChar;
}
*** ../vim-5.6a.27/src/version.c Fri Jan 14 22:49:13 2000
--- src/version.c Fri Jan 14 22:48:51 2000
***************
*** 420,421 ****
--- 420,423 ----
{ /* Add new patch number below this line */
+ /**/
+ 28,
/**/
--
hundred-and-one symptoms of being an internet addict:
181. You make up words that go with the "happy tune" your modem makes
while dialing your ISP.
--/-/---- Bram Moolenaar ---- Bram@... ---- Bram@... ---\-\--
\ \ www.vim.org/iccf www.moolenaar.net www.vim.org / /
I made some patches for multibyte.
May I post these patches to here?
list of pathes
-Regular expression search and substitute. (16K)
-Simple search in search.c. (2K)
-Special multibyte character cannot be used in menu. (1K)
Thanks.
----
Taro Muraoka koron@...
Vince Negri wrote:
> > This was sent to the vim-multibyte group. Are you subscribed there?
> I already have too much email - can't really face joining another list! :)
Well, I got a warning from egroups that the list would be deleted, because
there was no message for the past 90 days... I wouldn't worry about getting
too much extra email! :-)
> > Anyway, this looks OK, except that the special handling of the TAB is
> > missing.
>
> Yes, the way to fix this is probably:
>
> int len = lstrlen( lpAnsiIn ) + 1; /* include NULL character */
> retval = MultiByteToWideChar(
> CP_OEMCP,
> MB_PRECOMPOSED,
> lpAnsiIn, len,
> lpWCStr, len
> );
>
> if (retval)
> {
> /* walk along lpWCStr string, turning tabs to spaces */
> ]
>
> return retval;
I'll send this back to the vim-multibyte list. Comments, anyone?
--
hundred-and-one symptoms of being an internet addict:
123. You ask the car dealer to install an extra cigarette lighter
on your new car to power your notebook.
--/-/---- Bram Moolenaar ---- Bram@... ---- Bram@... ---\-\--
\ \ www.vim.org/iccf www.moolenaar.net www.vim.org / /
Thank you Taro
(about patch)
but...
Last parameter of function "MultiByteToWideChar"
is the size, in wide characters, of the buffer pointed
to by the lpWideCharStr parameter.
If this work ..., may be broken a few buffers.
int nChar = 0;
nChar = MultiByteToWideChar(
CP_OEMCP,
MB_PRECOMPOSED,
lpAnsiIn,
-1,
lpWCStr,
sizeof(lpAnsiIn)
);
return nChar;
[There is a discussion on the linux-utf8 maillist about file encodings. Here
is a reply about the 'fileencoding' option in Vim which you might find
interesting.]
Date: Tue, 2 Nov 1999 20:31:59 +0100 (CET)
From: PILCH Hartmut <phm@...>
To: linux-utf8@...
cc: perl-unicode@...
Subject: Re: Correct use of UTF-8 under Unix
Message-ID: <Pine.LNX.4.10.9911022028010.7046-100000@...>
On Tue, 2 Nov 1999, Bram Moolenaar wrote:
> So, what now? I certainly would like Vim to be able to handle multiple
> encodings. The easy way out is to let the user set the 'fileencoding' option.
> This is actually already working, with these values:
> ansi default setting, good for most Western languages
> japan set to use shift-JIS (Windows CP 932) encoding
> korea set to use Korean DBCS
> prc use simplified Chinese encoding
> taiwan use traditional Chinese encoding
For Japan, Shift-JIS is definitely not enough. You need at least also
EUC-Japan and iso-2022-jp-2. For the others the situation is similar.
Emacs uses the MIME names, as does Java.
Also, Emacs subdivides your 'fileencoding' into a
'coding-system-for-read' and a 'coding-system-for-write'.
If in doubt, it is a good idea to follow the Emacs naming. Emacs is
not yet UTF8 based, but it has thouroughly designed multi-coding
capabilities with many years of experience and it is the only
multilingual system that has been in use on Linux. Therefore it
would also be very helpful, if your vim was able to read the
multilingual encodings used by Emacs: iso-2022-7bit and emacs-mule.
Thanks to Otfried Cheong's conversion frontend, I am currently using
Emacs with the "unicode-utf8" encoding (is that a MIME name?), but
the other two multilingual encodings will keep staying around for
quite a while, since it will take a lot of effort to move the core
of Emacs to Unicode.
--
phm
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
On Thu, Jul 15, 1999 at 05:12:50 +0900, Chi-Deok Hwang wrote:
>
> It is possible to use the separate widget for status area, but not separate
> window. Then client window will be mainwin and focus window be drawarea.
> And GtkLabel or something containing status area will have mainwin's window
> as it's parent window.
> It is clean and really I wanted this senario. But old vim's layout/resizing
> code was too hackish to implement this. My main aim was to try fix this
> horrible resizing codes.
> Next time I or Nam will remove XIM code from gui_gtk_f.c.
And now, here is a patch for it from Chi-Deok Hwang.
I applied this to VIM-5.5.28 and have no problem yet.
This also fixes the ':set guioptions+=b'.
namsh
--- gui_gtk_f.c.orig Wed Oct 20 21:32:46 1999
+++ gui_gtk_f.c Wed Oct 20 21:52:27 1999
@@ -399,12 +399,6 @@
requisition->width = form->width;
requisition->height = form->height;
-#ifdef USE_XIM
- /*
- * FIXME: This isn't the proper place to do this!
- */
- requisition->height += xim_get_status_area_height();
-#endif
tmp_list = form->children;
@@ -798,10 +792,6 @@
event.y = widget->allocation.y;
event.width = widget->allocation.width;
event.height = widget->allocation.height;
-
-#ifdef USE_XIM
- event.height -= xim_get_status_area_height();
-#endif
gtk_widget_event (widget, (GdkEvent*) &event);
}
--- gui_gtk_x11.c.orig Wed Oct 20 21:32:55 1999
+++ gui_gtk_x11.c Wed Oct 20 22:15:38 1999
@@ -1614,6 +1614,15 @@
/* Adjust input management behaviour to the capabilities of the new
* fontset */
xim_decide_input_style();
+ if (xim_get_status_area_height()) {
+ /* status area is required */
+ /* just create the empty label so that
+ mainwin will allocate the extra space for status area */
+ GtkWidget *label = gtk_label_new(" ");
+ gtk_widget_set_usize(label, 20, gui.char_height + 2);
+ gtk_box_pack_end(GTK_BOX(GTK_BIN(gui.mainwin)->child), label, FALSE, FALSE,
0);
+ gtk_widget_show(label);
+ }
#endif
/* Preserve the logical dimensions of the screen. */
--- multbyte.c.orig Wed Oct 20 21:41:02 1999
+++ multbyte.c Wed Oct 20 22:30:23 1999
@@ -397,19 +397,19 @@
return;
attr = xic_attr;
- widget = gui.drawarea;
attrmask = 0;
style = gdk_ic_get_style(xic);
if ((style & GDK_IM_STATUS_MASK) == GDK_IM_STATUS_AREA)
{
if (gui.fontset && gui.fontset->type == GDK_FONT_FONTSET)
{
+ widget = gui.mainwin;
gdk_window_get_size(widget->window, &width, &height);
attrmask |= GDK_IC_STATUS_AREA;
- attr->status_area.x = gui.border_offset;
- attr->status_area.y = height - gui.char_height - gui.border_offset;
- attr->status_area.width = width - 2 * gui.border_offset;
+ attr->status_area.x = 0;
+ attr->status_area.y = height - gui.char_height - 1;
+ attr->status_area.width = width;
attr->status_area.height = gui.char_height;
}
}
@@ -815,7 +815,7 @@
if (!gdk_im_ready())
{
- EMSG("Your GTK+ does not support XIM");
+ EMSG("Input Method Server is not running");
return;
}
if ((xic_attr = gdk_ic_attr_new()) != NULL)
@@ -828,7 +828,7 @@
GtkWidget *widget = gui.drawarea;
attr->style = xim_input_style;
- attr->client_window = widget->window;
+ attr->client_window = gui.mainwin->window;
if ((colormap = gtk_widget_get_colormap(widget)) !=
gtk_widget_get_default_colormap())
@@ -871,13 +871,13 @@
}
else
{
+ gdk_window_get_size(gui.mainwin->window, &width, &height);
attrmask |= GDK_IC_STATUS_AREA_REQ;
- attr->status_area.x = gui.border_offset;
- attr->status_area.y = height - gui.char_height - gui.border_offset;
- attr->status_area.width = width - 2*gui.border_offset;
+ attr->status_area.x = 0;
+ attr->status_area.y = height - gui.char_height - 1;
+ attr->status_area.width = width;
attr->status_area.height = gui.char_height;
attr->status_fontset = gui.fontset;
- attr->preedit_area.height -= gui.char_height;
}
}
#endif
Hi, fellow Vim users in California!
I am currently in Arcata (near Eureka) and I will be coming down to
San Francisco on Tuesday October 12th. I will probably take a look
at the Berkeley campus and maybe to meet some of you guys there.
So if you have some spare time on either of Oct 12-14 - let me know! :-)
I might not be able to check my email on my way until
I get into Sacramento on the weekend before (Oct 9/10).
Sven
Axel Kielhorn has compiled Vim 5.5 for the MacIntosh and created .sit
archives. Patches up to 5.5.002 have been included.
Syntax highlighting is not supported for 68k.
You will need StuffIt Expander 5.x to extract the files.
The files are located at ftp://ftp.vim.org/pub/vim/mac/
SIZE FILE CONTENTS
1136568 vim55rt.sit Vim 5.5 runtime files packed for Mac
746557 vim55bin.sit Vim 5.5 Mac 68k and PPC binaries
If you have problems, please contact Axel Kielhorn <A.Kielhorn@...>.
More info: http://www.tu-bs.de/~i0080108/macvim.html.
--
hundred-and-one symptoms of being an internet addict:
199. You read this entire list of symptoms, looking for something
that doesn't describe you.
--/-/---- Bram Moolenaar ---- Bram@... ---- Bram@... ---\-\--
\ \ www.vim.org/iccf www.moolenaar.net www.vim.org / /
Announcing: Vim (Vi IMproved) version 5.5
Author: Bram Moolenaar et al.
Announcement
------------
This is a bug-fix release of Vim. Since version 5.4 bugs have been fixed, and
some items cleaned up.
Vim 5.5 has been tested by quite a few people over the past weeks, and there
are no big changes since version 5.4. This should be the most stable Vim
version ever. But it's free software, the usual disclaimers apply.
What is Vim?
------------
Vim is an almost 100% compatible version of the UNIX editor Vi. Many new
features have been added: Multi level undo, syntax highlighting, command line
history, filename completion, block operations, etc. Those who don't know Vi
can probably skip this message, unless you are prepared to learn something new
and useful. Vim is especially recommended for editing programs.
Vim runs on almost any Unix flavor, MS-DOS, MS-Windows 3.1, MS-Windows
95/98/NT, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and Amiga.
For more information, see "http://www.vim.org".
New since version 5.4
---------------------
Not much:
- Support for a mouse scroll wheel in X11 (GTK, Athena and Motif). Should
also work in an xterm when translations are installed.
- Support for decompression of bzip2 files in the example vimrc file.
- Handling of patch numbers, they show up in the ":version" output.
- Uninstall program for MS-Windows, for those that have a problem with the
"Edit with Vim" popup menu entry.
And many bug fixes! This version is aimed at stability.
See ":help version-5.5" in Vim for the details.
Where to get it
---------------
You can find a list of distribution sites at
ftp://ftp.vim.org/pub/vim/MIRRORS
Suggested locations:
ftp://ftp.<country>.vim.org/pub/vim/
ftp://ftp.vim.org/pub/vim/
Replace <country> with a country code, e.g.:
ftp://ftp.us.vim.org/pub/vim/
What is available
-----------------
Note that for all systems the distribution is split into an archive with
runtime files (documentation, syntax files, etc.) and a binary and/or source
archive. You should download at least two archives.
FILE SYSTEM COMMENTS
unix/vim-5.5-src.tar.gz Unix(*) Sources.
unix/vim-5.5-rt.tar.gz Unix(*) Runtime files.
extra/vim-5.5-extra.tar.gz Unix(*) Extra sources and docs (Farsi, OLE, VisVim).
unix/vim-5.4-5.5-rt.diff.gz Runtime diff with version 5.4.
unix/vim-5.4-5.5-src.diff.gz Sources diff with version 5.4.
extra/vim-5.4-5.5-extra.diff.gz Extra diff with version 5.4.
pc/vim55rt.zip Win32 MS-DOS and MS-Windows runtime files.
pc/gvim55.zip Win32 32 bit MS-Windows 95/98/NT GUI binaries.
Recommended for MS-Windows 95/98/NT.
The best choice for syntax highlighting and
speed.
pc/gvim55ole.zip Win32 32 bit MS-Windows 95/98/NT GUI binaries,
with OLE support and VisVim.
pc/gvim55_s.zip Win32s 32 bit MS-Windows 3.1/3.11 GUI binaries.
Requires Win32s.
pc/vim55w32.zip Win32 32 bit MS-Windows 95/98/NT console binaries.
Recommended for Windows NT, NOT for 95/98.
Supports long file names.
pc/vim55d32.zip MS-DOS 32 bit protected mode binaries.
Recommended for MS-DOS, MS-Windows 3.1 and
MS-Windows 95/98 console. It is compiled
with DJGPP, it may need a DPMI driver
(CWSDPMI is included). Supports long file
names on MS-Windows 95/98 (NOT on NT).
pc/vim55d16.zip MS-DOS 16 bit real mode binaries.
Runs on most MS-DOS systems, but is
restricted to using 640K memory. Small
version, without e.g., syntax highlighting
and autocommands.
pc/vim55src.zip PC Sources for PC versions (with CR-LF).
os2/vim55rt.zip OS/2 Runtime files (same as for PC).
os2/vim55os2.zip OS/2 Binaries.
(use the Unix+extra archives for sources)
amiga/vim55rt.tgz Amiga Runtime files.
amiga/vim55bin.tgz Amiga Binaries.
amiga/vim55big.tgz Amiga Binaries with more features.
amiga/vim55src.tgz Amiga Sources for Amiga.
doc/vim55html.zip all Documentation converted to HTML.
patches/* all Recent patches.
(*) Also for BeOS, OS/2, VMS, Macintosh and Atari MiNT
The contents of the source archives depends on the specified system. To
obtain the full sources and docs, get the three Unix archives.
system file type Unpack with
Unix file.tar.gz gunzip file.tar.gz; tar xf file.tar
Amiga file.tgz gzip -d file.tgz; tar xf file.tar
PC file.zip pkunzip -d file.zip
or: unzip file.zip
Mailing lists
-------------
For user questions you can turn to the Vim mailing list. There are a lot of
tips, scripts and solutions. You can ask your Vim questions, but only if you
subscribe. See http://www.vim.org/mail.html. An archive is kept at
http://www.egroups.com/group/vim.
If you want to help developing Vim or get the latest patches, subscribe to the
vim-dev mailing list. An archive is kept at
http://www.egroups.com/group/vimdev.
Reporting bugs
--------------
Send them to <Bram@...>. Please be brief, all the time spent on answering
mail is subtracted from the time that is spent on improving Vim! Always give
a reproducable example and try to find out which settings or other things
influence the appearance of the bug. Try different machines if possible. See
":help bugs" in Vim. Send me patches if you can!
If something needs discussing with other developers, send a message to the
vim-dev mailing list. You need to subscribe first.
Happy Vimming!
--
hundred-and-one symptoms of being an internet addict:
141. You'd rather go to http://www.weather.com/ than look out your window.
--/-/---- Bram Moolenaar ---- Bram@... ---- Bram@... ---\-\--
\ \ www.vim.org/iccf www.moolenaar.net www.vim.org / /
This is the final test in order to check, wether egroups finaly can handle
the archive correctly.
Sorry for the interruption,
cheers,
oec
maillinglistmanager
Welcome to the vim-multibyte maillist!
This list is to be used for multi-byte user issues of Vim (Vi IMproved) and
some development. Also see the "vim" and "vimdev" maillists.
NOTE: Don't send messages to vim-multibyte@egroups.com, use
vim-multibyte@.... Otherwise the subscribers will not get your message,
it will only be archived at egroups.
--
hundred-and-one symptoms of being an internet addict:
91. It's Saturday afternoon in the middle of may and you are on computer.
--/-/---- Bram Moolenaar ---- Bram@... ---- Bram@... ---\-\--
\ \ www.vim.org/iccf www.moolenaar.net www.vim.org / /
Multi-byte aspects of Vim (Vi IMproved)
Mostly for users, but also for development.
Original address: vim-multibyte@...
Also see the "vim" and "vimdev" lists.