The binary for Vim version 5.6 is now also available for the Macintosh. It
was compiled and packed by Dany St-Amant.
Directory: ftp://ftp.vim.org/pub/vim/mac
You will need StuffIt Expander 5.x to extract the files.
SIZE FILE CONTENTS
1688291 vim5.6.full.fat.sit Vim 5.6, FAT application + runtime files
298138 vim5.6.68k.sit Vim 5.6, 68k application only
624790 vim5.6.fat.sit Vim 5.6, FAT application only
333697 vim5.6.ppc.sit Vim 5.6, PowerPC application only
For more information on the Macintosh version, go to:
http://www3.sympatico.ca/dany.stamant/vim/
For discussions about the Macintosh version, use the vim-mac maillist. Send a
message to vim-help@... to find out how to subscribe.
Another note: ftp.vim.org has been moved to another (faster) machine.
I have not been able to upload files until today. Sorry for the delay.
It appears to work OK now. Let me know if you have persistent problems.
--
BLACK KNIGHT: I'm invincible!
ARTHUR: You're a looney.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\ \ Vim: http://www.vim.org ICCF Holland: http://www.vim.org/iccf / /
As you all know (or should know), Vim is distributed under the charityware
concept: If you like using Vim, you are requested to help a childrens centre
in Uganda. In March I visited the project to see how they are doing. Below
is my report. Hopefully this inspires you to (continue) support for the
project. I will certainly do that myself! You can also read it on the net,
with a couple of pictures:
http://www.vim.org/iccf/news.html
Also go there for more information on the project. If you have any remaining
questions, ask me.
Clinic
There is a small clinic at the project, which has been improved over the last
couple of years. More and more villagers know how to find the place. I was
there on a market day, when over a hundred patients came for medical help. It
was really crowded with patients waiting for treatment. On other days there
are around thirty patients. Overall there are more than two hundred patients
each week. Thus the clinic is providing a very important service to the
community. I have spoken with a few locals, who said they are very happy with
the medical help.
The patients pay a small fee for treatment and medicine. This doesn't cover
the actual cost though. Only through donations can we keep the clinic running,
since the patients are not able to pay a higher fee. The Lisbloem school in
Lisse (The Netherlands) raised a large amount, which has been used to buy a
solar powered fridge. It stores the medicines that have to be kept in a cool
place. The picture shows assistant nurse Boaz with the new fridge. Boaz is one
of the orphans that grew up at the centre while I was working there in 94/95.
He has been able to get an education through the sponsorship program. I was
happy to see he is now working for the centre.
There is one Ugandan nurse working full time, and a doctor visiting on market
days. Hopefully the quality of the service provided can be improved the coming
year. A small laboratory would be very useful, and more educated staff.
School
The vocational school had just been extended with a tailoring section. I
watched the pupils enjoying their first lessons. It is in a new building,
together with the carpentry section which started last year. The school now
goes from kindergarten, through primary and secondary to the vocational
school. All teachers are now Ugandans and have proper training. There is a
total of about four hundred children, who are enjoying the high quality of
this school.
Besides running the school in Kibaale, attention is given to teachers in
schools of nearby villages. Many of these have had no more training than
primary school themselves. Teacher training is now organised to improve their
knowledge and teaching abilities. The teacher resource centre provides them
with materials.
I really enjoyed watching the children going to school. And they stay until
late in the afternoon to play football and netball. Quite an improvement
compared to the situation in 1993, when I first visited the project. Only
three classes back then, and most teachers were not trained. Now the school is
an example for the area.
Sponsorship
Many children cannot afford to pay their school fees. Therefore sponsors pay
monthly to support them. I have visited eight of the sponsored children at
their homes. The picture shows Nabasagi Morine, one of our youngest children.
She is six years old and goes to the kindergarten class.
Generally, these families are only just able to manage their household. They
have the basic things like a house, some clothes and grow their own food.
Nothing more than that. One family was below the average level though. Their
house is leaking, there are no blankets for the children and no mattresses. I
have asked the manager to give them at least a couple of blankets. Hopefully
we find a way for them to be able to take care of themselves. That is better
than have them depend on our gifts.
There are still a lot of children who are not sponsored. Hopefully we will
find more sponsors this year. The office that takes care of the sponsored
children, called Kibaale Childrens Fund (KCF) is running very well. There are
two Ugandans, who visit the children, managed by a Canadian volunteer. They
make sure the children are able to attend school, visit them at home and take
them to hospital when needed. I accompanied three children to hospital,
together with an assistant nurse. The garden of the hospital looks great, but
the quality of the medical care is low. But there is no other place with a
qualified doctor and a laboratory. We might try to improve our own clinic to
work around this problem.
Conclusion
I can see quite a bit of improvement since my last visit in 1998. Roads have
been fixed, there is more traffic and business. The Kibaale Childrens Centre
is running very well and mainly with Ugandan staff. The school is operating
very well, and the clinic provides health care to many patients. The coming
time will be focused on maintaining the project and further improving the
quality. I will certainly support that.
- Bram Moolenaar
--
Any sufficiently advanced technology is indistinguishable from magic.
Arthur C. Clarke
/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\-\-- Vim: http://www.vim.org ---- ICCF Holland: http://www.vim.org/iccf --/-/
Vim is charityware. This means that I ask users of Vim to donate money to
help orphans in Uganda. Many people have done that, and there are a few Vim
users who have financially adopted a child. This helps the Ugandan children a
lot. Thanks to all who helped!
Still, there are people who can't afford a donation, or have another reason
why didn't didn't donate yet. For these people I have set up a page where you
can make a donation without paying anything!
How does this work? Many advertisers pay a small amount when you click on a
banner, to indicate you have seen it. Others give a percentage of the sales
generated from a click-through. I have collected a number of these items
here:
http://www.vim.org/iccf/click.html
There are links to information, search engines, books and music shops, etc.
I have checked that the links are useful or interesting, there is no junk
banner or porno site.
Please click around and make some money for the children in Uganda. There are
a few search engines, you might want to bookmark the page and use it when you
are searching for something.
If you think clicking on banners is a waste of time, consider donating
directly. You can find info here:
http://www.vim.org/iccf/donate.html
--
A M00se once bit my sister ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\-\-- Vim: http://www.vim.org ---- ICCF Holland: http://www.vim.org/iccf --/-/
Hello Vimmers,
This is a BETA version of Vim 5.7. It includes all patches that have been
sent out for 5.6, plus a few extras (new and updated syntax files, docs,
etc.).
The main reason for bringing out this beta version is that the DOS, Windows
and Amiga versions need testing, since there have been no patches for the
executables. And it doesn't hurt to give all the changes some more testing,
version 5.7 is supposed to be very reliable.
If all goes well, version 5.7 will be released in two weeks.
Note that all the files are under the "unreleased" directory at the ftp site.
There is an alternative way to obtain the latest Vim sources: CVS. You need
the cvs program for this. Info can be found at http://cvs.vim.org. It may
take a day before version 5.7a is available by CVS.
WHERE TO GET IT
---------------
You can find Vim 5.7a here:
ftp://ftp.vim.org/pub/vim/unreleased/
See this file for Mirrors:
ftp://ftp.vim.org/pub/vim/MIRRORS
FILE SYSTEM COMMENTS
unix/vim-5.7a-src.tar.gz Unix(*) Sources
unix/vim-5.6-5.7a-src.diff.gz sources diff with version 5.6
unix/vim-5.7a-rt.tar.gz Unix(*) runtime files
unix/vim-5.6-5.7a-rt.diff.gz runtime diff with version 5.6
extra/vim-5.7a-extra.tar.gz Unix(*) Extra sources and docs (Farsi, OLE, VisVim)
extra/vim-5.6-5.7a-extra.diff.gz diff with version 5.6
pc/vim57art.zip Win32 DOS and MS-Windows runtime files
pc/gvim57a.zip Win32 32 bit Windows 95/98/NT GUI binaries.
Recommended for Windows 95/98 and NT. The
best choice for syntax highlighting and
speed.
pc/gvim57aole.zip Win32 32 bit Windows 95/98/NT GUI binaries, with
OLE support and VisVim.
pc/gvim57a_s.zip Win32s 32 bit Windows 3.1/3.11 GUI binaries.
Requires Win32s.
pc/vim57aw32.zip Win32 32 bit Windows console binaries.
Recommended for Windows NT, not for 95/98.
Supports long file names.
pc/vim57ad32.zip MS-DOS 32 bit protected mode binaries.
Recommended for MS-DOS, Windows 3.1 and
Windows 95/98 console. It is compiled with
DJGPP, it may need a DPMI driver (CWSDPMI
is included). Supports long file names on
Windows 95/98.
pc/vim57ad16.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/vim57asrc.zip PC Sources for PC versions (with CR-LF).
os2/vim57art.zip OS/2 runtime files (same as pc/vim57art.zip)
os2/vim57aos2.zip OS/2 binaries
(use the Unix and extra archives for OS/2
sources)
amiga/vim57art.tgz Amiga runtime files
amiga/vim57abin.tgz Amiga Binary
amiga/vim57abig.tgz Amiga Binary with more features
amiga/vim57asrc.tgz Amiga Sources for Amiga
doc/vim57ahtml.zip all Documentation converted to HTML
(*) 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
unzip file.zip
WHAT IS NEW
-----------
This is the complete list of changes since version 5.6.
Added:
New syntax files:
stp Stored Procedures (Jeff Lanzarotta)
snnsnet, snnspat, snnsres SNNS (Davide Alberani)
mel MEL (Robert Minsk)
ruby Ruby (Mirko Nasato)
tli TealInfo (Kurt W. Andrews)
ora Oracle config file (Sandor Kopanyi)
abaqus Abaqus (Carl Osterwisch)
jproperties Java Properties (Simon Baldwin)
apache Apache config (Allan Kelly)
csp CSP (Jan Bredereke)
samba Samba config (Rafael Garcia-Suarez)
kscript KDE script (Thomas Capricelli)
hb Hyper Builder (Alejandro Forero Cuervo)
fortran Fortran (rewritten) (Ajit J. Thakkar)
sml SML (Fabrizio Zeno Cornelli)
cvs CVS commit (Matt Dunford)
aspperl ASP Perl (Aaron Hope)
bc BC calculator (Vladimir Scholtz)
Included Exuberant ctags 3.5.1. (Darren Hiebert)
"display" and "fold" arguments for syntax items. For future extension, they
are ignored now.
strftime() function for the Macintosh.
Fixed:
The 16 bit MS-DOS version is now compiled with Bcc 3.1 instead of 4.0. The
executable is smaller.
When a "make test" failed, the output file was lost. Rename it to
test99.failed to be able to see what went wrong.
After sourcing bugreport.vim, it's not clear that bugreport.txt has been
written in the current directory. Edit bugreport.txt to avoid that.
Adding IME support when using Makefile.w32 didn't work. (Taro Muraoka)
Win32 console: Mouse drags were passed on even when the mouse didn't move.
Perl interface: In Buffers(), type of argument to SvPV() was int, should be
STRLEN. (Tony Leneis)
Problem with prototype for index() on AIX 4.3.0. Added check for _AIX43 in
os_unix.h. (Jake Hamby)
Mappings in mswin.vim could break when some commands are mapped. Add "nore"
to most mappings to avoid re-mapping.
modify_fname() made a copy of a file name for ":p" when it already was a full
path name, which is a bit slow.
Win32 with Borland C++ 5.5: Pass the path to the compiler on to xxd and ctags,
to avoid depending on $PATH. Fixed "make clean".
Many fixes to Macintosh specific parts: (mostly by Dany StAmant)
- Only one Help menu.
- No more crash when removing a menu item.
- Support as External Editor for Codewarior (still some little glitches).
- Popup menu support.
- Fixed crash when pasting after application switch.
- Color from rgb.txt properly displayed.
- 'isprint' default includes all chars above '~'. (Axel Kielhorn)
- mac_expandpath() was leaking memory.
- Add digraphs table. (Axel Kielhorn)
- Multi-byte support: (Kenichi Asai)
Switch keyscript when going in/out of Insert mode.
Draw multi-byte character correctly.
Don't use mblen() but highest bit of char to detect multi-byte char.
Display value of multi-byte in statusline (also for other systems).
Fixes for VMS: (Zoltan Arpadffy) (also see patch 5.6.045 below)
- Added Makefile_vms.mms and vimrc.vms to src/testdir to be able to run the
tests.
- Various fixes.
- Set 'undolevels' to 1000 by default.
- Made mch_settitle() equivalent to the one in os_unix.c.
RiscOS: A few prototypes for os_riscos.c were outdated. Generate prototypes
automatically.
Previously released patches:
Patch 5.6.001
Problem: When using "set bs=0 si cin", Inserting "#<BS>" or "}<BS>" which
reduces the indent doesn't delete the "#" or "}". (Lorton)
Solution: Adjust ai_col in ins_try_si().
Files: src/edit.c
Patch 5.6.002
Problem: When using the vim.vim syntax file, a comment with all uppercase
characters causes a hang.
Solution: Adjust pattern for vimCommentTitle (Charles Campbell)
Files: runtime/syntax/vim.vim
Patch 5.6.003
Problem: GTK GUI: Loading a user defined toolbar bitmap gives a warning
about the colormap. Probably because the window has not been
opened yet.
Solution: Use gdk_pixmap_colormap_create_from_xpm() to convert the xpm file.
(Keith Radebaugh)
Files: src/gui_gtk.c
Patch 5.6.004 (extra)
Problem: Win32 GUI with IME: When setting 'guifont' to "*", the font
requester appears twice.
Solution: In gui_mch_init_font() don't call get_logfont() but copy
norm_logfont from fh. (Yasuhiro Matsumoto)
Files: src/gui_w32.c
Patch 5.6.005
Problem: When 'winminheight' is zero, CTRL-W - with a big number causes a
crash. (David Kotchan)
Solution: Check for negative window height in win_setheight().
Files: src/window.c
Patch 5.6.006
Problem: GTK GUI: Bold font cannot always be used. Memory is freed too
early in gui_mch_init_font().
Solution: Move call to g_free() to after where sdup is used. (Artem Hodyush)
Files: src/gui_gtk_x11.c
Patch 5.6.007 (extra)
Problem: Win32 IME: Font is not changed when screen font is changed. And
IME composition window does not trace the cursor.
Solution: Initialize IME font. When cursor is moved, set IME composition
window with ImeSetCompositionWindow(). Add call to
ImmReleaseContext() in several places. (Taro Muraoka)
Files: src/gui.c, src/gui_w32.c, src/proto/gui_w32.pro
Patch 5.6.008 (extra)
Problem: Win32: When two files exist with the same name but different case
(through NFS or Samba), fixing the file name case could cause the
wrong one to be edited.
Solution: Prefer a perfect match above a match while ignoring case in
fname_case(). (Flemming Madsen)
Files: src/os_win32.c
Patch 5.6.009 (extra)
Problem: Win32 GUI: Garbage in Windows Explorer help line when selecting
"Edit with Vim" popup menu entry.
Solution: Only return the help line when called with the GCS_HELPTEXT flag.
(Tianmiao Hu)
Files: GvimExt/gvimext.cpp
Patch 5.6.010
Problem: A file name which contains a TAB was not read correctly from the
viminfo file and the ":ls" listing was not aligned properly.
Solution: Parse the buffer list lines in the viminfo file from the end
backwards. Count a Tab for two characters to align the ":ls" list.
Files: src/buffer.c
Patch 5.6.011
Problem: When 'columns' is huge (using a tiny font) and 'statusline' is
used, Vim can crash.
Solution: Limit maxlen to MAXPATHL in win_redr_custom(). (John Mullin)
Files: src/screen.c
Patch 5.6.012
Problem: When using "zsh" for /bin/sh, toolcheck may hang until "exit" is
typed. (Kuratczyk)
Solution: Add "-c exit" when checking for the shell version.
Files: src/toolcheck
Patch 5.6.013
Problem: Multibyte char in tooltip is broken.
Solution: Consider multibyte char in replace_termcodes(). (Taro Muraoka)
Files: src/term.c
Patch 5.6.014
Problem: When cursor is at the end of line and the character under cursor
is a multibyte character, "yl" doesn't yank 1 multibyte-char.
(Takuhiro Nishioka)
Solution: Recognize a multibyte-char at end-of-line correctly in oneright().
(Taro Muraoka)
Also: make "+quickfix" in ":version" output appear alphabetically.
Files: src/edit.c
Patch 5.6.015
Problem: New xterm delete key sends <Esc>[3~ by default.
Solution: Added <kDel> and <kIns> to make the set of keypad keys complete.
Files: src/edit.c, src/ex_getln.c, src/keymap.h, src/misc1.c,
src/misc2.c, src/normal.c, src/os_unix.c, src/term.c
Patch 5.6.016
Problem: When deleting a search string from history from inside a mapping,
another entry is deleted too. (Benji Fisher)
Solution: Reset last_maptick when deleting the last entry of the search
history. Also: Increment maptick when starting a mapping from
typed characters to avoid a just added search string being
overwritten or removed from history.
Files: src/ex_getln.c, src/getchar.c
Patch 5.6.017
Problem: ":s/e/\^M/" should replace an "e" with a CTRL-M, not split the
line. (Calder)
Solution: Replace the backslash with a CTRL-V internally. (Stephen P. Wall)
Files: src/ex_cmds.c
Patch 5.6.018
Problem: ":help [:digit:]" takes a long time to jump to the wrong place.
Solution: Insert a backslash to avoid the special meaning of '[]'.
Files: src/ex_cmds.c
Patch 5.6.019
Problem: "snd.c", "snd.java", etc. were recognized as "mail" filetype.
Solution: Make pattern for mail filetype more strict.
Files: runtime/filetype.vim
Patch 5.6.020 (extra)
Problem: The DJGPP version eats processor time (Walter Briscoe).
Solution: Call __dpmi_yield() in the busy-wait loop.
Files: src/os_msdos.c
Patch 5.6.021
Problem: When 'selection' is "exclusive", a double mouse click in Insert
mode doesn't select last char in line. (Lutz)
Solution: Allow leaving the cursor on the NUL past the line in this case.
Files: src/edit.c
Patch 5.6.022
Problem: ":e \~<Tab>" expands to ":e ~\$ceelen", which doesn't work.
Solution: Re-insert the backslash before the '~'.
Files: src/ex_getln.c
Patch 5.6.023 (extra)
Problem: Various warnings for the Ming compiler.
Solution: Changes to avoid the warnings. (Bill McCarthy)
Files: src/ex_cmds.c, src/gui_w32.c, src/os_w32exe.c, src/os_win32.c,
src/syntax.c, src/vim.rc
Patch 5.6.024 (extra)
Problem: Win32 console: Entering CTRL-_ requires the shift key. (Kotchan)
Solution: Specifically catch keycode 0xBD, like the GUI.
Files: src/os_win32.c
Patch 5.6.025
Problem: GTK GUI: Starting the GUI could be interrupted by a SIGWINCH.
(Nils Lohner)
Solution: Repeat the read() call to get the gui_in_use value when
interrupted by a signal.
Files: src/gui.c
Patch 5.6.026 (extra)
Problem: Win32 GUI: Toolbar bitmaps are searched for in
$VIMRUNTIME/bitmaps, while GTK looks in $VIM/bitmaps. (Keith
Radebaugh)
Solution: Use $VIM/bitmaps for both, because these are not part of the
distribution but defined by the user.
Files: src/gui_w32.c, runtime/doc/gui.txt
Patch 5.6.027
Problem: TCL: Crash when using a Tcl script (reported for Win32).
Solution: Call Tcl_FindExecutable() in main(). (Brent Fulgham)
Files: src/main.c
Patch 5.6.028
Problem: Xterm patch level 126 sends codes for mouse scroll wheel.
Fully works with xterm patch level 131.
Solution: Recognize the codes for button 4 (0x60) and button 5 (0x61).
Files: src/term.c
Patch 5.6.029
Problem: GTK GUI: Shortcut keys cannot be used for a dialog. (Johannes
Zellner)
Solution: Add support for shortcut keys. (Marcin Dalecki)
Files: src/gui_gtk.c
Patch 5.6.030
Problem: When closing a window and 'ea' is set, Vim can crash. (Yasuhiro
Matsumoto)
Solution: Set "curbuf" to a valid value in win_close().
Files: src/window.c
Patch 5.6.031
Problem: Multi-byte: When a double-byte character ends in CSI, Vim waits
for another character to be typed.
Solution: Recognize the CSI as the second byte of a character and don't wait
for another one. (Yasuhiro Matsumoto)
Files: src/getchar.c
Patch 5.6.032
Problem: Functions with an argument that is a line number don't all accept
".", "$", etc. (Ralf Arens)
Solution: Add get_art_lnum() and use it for setline(), line2byte() and
synID().
Files: src/eval.c
Patch 5.6.033
Problem: Multi-byte: "f " sometimes skips to the second space. (Sung-Hyun
Nam)
Solution: Change logic in searchc() to skip trailing byte of a double-byte
character.
Also: Ask for second byte when searching for double-byte
character. (Park Chong-Dae)
Files: src/search.c
Patch 5.6.034 (extra)
Problem: Compiling with Borland C++ 5.5 fails on tolower() and toupper().
Solution: Use TO_LOWER() and TO_UPPER() instead. Also adjust the Makefile
to make using bcc 5.5 easier.
Files: src/edit.c, src/ex_docmd.c, src/misc1.c, src/Makefile.bor
Patch 5.6.035
Problem: Listing the"+comments" feature in the ":version" output depended
on the wrong ID. (Stephen P. Wall)
Solution: Change "CRYPTV" to "COMMENTS".
Files: src/version.c
Patch 5.6.036
Problem: GTK GUI: Copy/paste text doesn't work between gvim and Eterm.
Solution: Support TEXT and COMPOUND_TEXT selection targets. (ChiDeok Hwang)
Files: src/gui_gtk_x11.c
Patch 5.6.037
Problem: Multi-byte: Can't use "f" command with multi-byte character in GUI.
Solution: Enable XIM in Normal mode for the GUI. (Sung-Hyun Nam)
Files: src/gui_gtk_x11.c, src/multbyte.c
Patch 5.6.038
Problem: Multi-clicks in GUI are interpreted as a mouse wheel click. When
'ttymouse' is "xterm" a mouse click is interpreted as a mouse
wheel click.
Solution: Don't recognize the mouse wheel in check_termcode() in the GUI.
Use 0x43 for a mouse drag in do_xterm_trace(), not 0x63.
Files: src/term.c, src/os_unix.c
Patch 5.6.039
Problem: Motif GUI under KDE: When trying to logout, Vim hangs up the
system. (Hermann Rochholz)
Solution: When handling the WM_SAVE_YOURSELF event, set the WM_COMMAND
property of the window to let the session manager know we finished
saving ourselves.
Files: src/gui_x11.c
Patch 5.6.040
Problem: When using ":s" command, matching the regexp is done twice.
Solution: After copying the matched line, adjust the pointers instead of
finding the match again. (Loic Grenie) Added vim_regnewptr().
Files: src/ex_cmds.c, src/regexp.c, src/proto/regexp.pro
Patch 5.6.041
Problem: GUI: Athena, Motif and GTK don't give more than 10 dialog buttons.
Solution: Remove the limit on the number of buttons.
Also support the 'v' flag in 'guioptions'.
For GTK: Center the buttons.
Files: src/gui_athena.c, src/gui_gtk.c, src/gui_motif.c
Patch 5.6.042
Problem: When doing "vim -u vimrc" and vimrc contains ":q", the cursor in
the terminal can remain off.
Solution: Call cursor_on() in mch_windexit().
Files: src/os_unix.c
Patch 5.6.043 (extra)
Problem: Win32 GUI: When selecting guifont with the dialog, 'guifont'
doesn't include the bold or italic attributes.
Solution: Append ":i" and/or ":b" to 'guifont' in gui_mch_init_font().
Files: src/gui_w32.c
Patch 5.6.044 (extra)
Problem: MS-DOS and Windows: The line that dosinst.exe appends to
autoexec.bat to set PATH is wrong when Vim is in a directory with
an embedded space.
Solution: Use double quotes for the value when there is an embedded space.
Files: src/dosinst.c
Patch 5.6.045 (extra) (fixed version)
Problem: VMS: Various small problems.
Solution: Many small changes. (Zoltan Arpadffy)
File name modifier ":h" keeps the path separator.
File name modifier ":e" also removes version.
Compile with MAX_FEAT by default.
When checking for autocommands ignore version in file name.
Be aware of file names being case insensitive.
Added vt320 builtin termcap.
Be prepared for an empty default_vim_dir.
Files: runtime/gvimrc_example.vim, runtime/vimrc_example.vim,
runtime/doc/os_vms.txt, src/eval.c, src/feature.h, src/fileio.c,
src/gui_motif.c, src/gui_vms_conf.h, src/main.c, src/memline.c,
src/misc1.c, src/option.c, src/os_vms_conf.h, src/os_vms.c,
src/os_vms.h, src/os_vms.mms, src/tag.c, src/term.c, src/version.c
Patch 5.6.046
Problem: Systems with backslash in file name: With 'shellslash' set, "vim
*/*.c" only uses a slash for the first file name. (Har'El)
Solution: Fix slashes in file name arguments after reading the vimrc file.
Files: src/option.c
Patch 5.6.047
Problem: $CPPFLAGS is not passed on to ctags configure.
Solution: Add it. (Walter Briscoe)
Files: src/config.mk.in, src/Makefile
Patch 5.6.048
Problem: CTRL-R in Command-line mode is documented to insert text as typed,
but inserts text literally.
Solution: Make CTRL-R insert text as typed, use CTRL-R CTRL-R to insert
literally. This is consistent with Insert mode. But characters
that end Command-line mode are inserted literally.
Files: runtime/doc/index.txt, runtime/doc/cmdline.txt, src/ex_getln.c,
src/ops.c, src/proto/ops.pro
Patch 5.6.049
Problem: Documentation for [!] after ":ijump" is wrong way around. (Benji
Fisher)
Solution: Fix the documentation. Also improve the code to check for a match
after a /* */ comment.
Files: runtime/doc/tagsearch.txt, src/search.c
Patch 5.6.050
Problem: Replacing is wrong when replacing a single-byte char with
double-byte char or the other way around.
Solution: Shift the text after the character when it is replaced.
(Yasuhiro Matsumoto)
Files: src/normal.c, src/misc1.c
Patch 5.6.051
Problem: ":tprev" and ":tnext" don't give an error message when trying to
go before the first or beyond the last tag. (Robert Webb)
Solution: Added error messages. Also: Delay a second when a file-read
message is going to overwrite an error message, otherwise it won't
be seen.
Files: src/fileio.c, src/tag.c
Patch 5.6.052
Problem: Multi-byte: When an Ex command has a '|' or '"' as a second byte,
it terminates the command.
Solution: Skip second byte of multi-byte char when checking for '|' and '"'.
(Asai Kenichi)
Files: src/ex_docmd.c
Patch 5.6.053
Problem: CTRL-] doesn't work on a tag that contains a '|'. (Cesar Crusius)
Solution: Escape '|', '"' and '\' in tag names when using CTRL-] and also
for command-line completion.
Files: src/ex_getln.c, src/normal.c
Patch 5.6.054
Problem: When using ":e" and ":e #" the cursor is put in the first column
when 'startofline' is set. (Cordell)
Solution: Use the last known column when 'startofline' is set.
Also, use ECMD_LAST more often to simplify the code.
Files: src/buffer.c, src/ex_cmds.c, src/ex_docmd.c, src/proto/buffer.pro
Patch 5.6.055
Problem: When 'statusline' only contains a text without "%" and doesn't fit
in the window, Vim crashes. (Ron Aaron)
Solution: Don't use the pointer for the first item if there is no item.
Files: src/screen.c
Patch 5.6.056 (extra)
Problem: MS-DOS: F11 and F12 don't work when 'bioskey' is set.
Solution: Use enhanced keyboard functions. (Vince Negri)
Detect presence of enhanced keybard and set bioskey_read and
bioskey_ready.
Files: src/os_msdos.c
Patch 5.6.057 (extra)
Problem: Win32 GUI: Multi-byte characters are wrong in dialogs and tear-off
menus.
Solution: Use system font instead of a fixed font. (Matsumoto, Muraoka)
Files: src/gui_w32.c
Patch 5.6.058
Problem: When the 'a' flag is not in 'guioptions', non-Windows systems
copy Visually selected text to the clipboard/selection on a yank
or delete command anyway. On Windows it isn't done even when the
'a' flag is included.
Solution: Respect the 'a' flag in 'guioptions' on all systems.
Files: src/normal.c
Patch 5.6.059 (extra)
Problem: When moving the cursor over italic text and the characters spill
over to the cell on the right, that spill-over is deleted.
Noticed in the Win32 GUI, can happen on other systems too.
Solution: Redraw italic text starting from a blank, like this is already
done for bold text. (Vince Negri)
Files: src/gui.c, src/gui.h, src/gui_w32.c
Patch 5.6.060
Problem: Some bold characters spill over the the cell on the left, that
spill-over can remain sometimes.
Solution: Redraw a characters when the next character was bold and needs
redrawing. (Robert Webb)
Files: src/screen.c
Patch 5.6.061
Problem: When xterm sends 8-bit controls, recognizing the version response
doesn't work.
When using CSI instead of <Esc>[ for the termcap color codes,
using 16 colors doesn't work. (Neil Bird)
Solution: Also accept CSI in place of <Esc>[ for the version string.
Also check for CSI when handling colors 8-15 in term_color().
Use CSI for builtin xterm termcap entries when 'term' contains
"8bit".
Files: runtime/doc/term.txt, src/ex_cmds.c, src/option.c, src/term.c,
src/os_unix.c, src/proto/option.pro, src/proto/term.pro
Patch 5.6.062
Problem: The documentation says that setting 'smartindent' doesn't have an
effect when 'cindent' is set, but it does make a difference for
lines starting with "#". (Neil Bird)
Solution: Really ignore 'smartindent' when 'cindent' is set.
Files: src/misc1.c, src/ops.c
Patch 5.6.063
Problem: Using "I" in Visual-block mode doesn't accept a count. (Johannes
Zellner)
Solution: Pass the count on to do_insert() and edit(). (Allan Kelly)
Files: src/normal.c, src/ops.c, src/proto/ops.pro
Patch 5.6.064
Problem: MS-DOS and Win32 console: Mouse doesn't work correctly after
including patch 5.6.28. (Vince Negri)
Solution: Don't check for mouse scroll wheel when the mouse code contains
the number of clicks.
Files: src/term.c
Patch 5.6.065
Problem: After moving the cursor around in Insert mode, typing a space can
still trigger an abbreviation. (Benji Fisher)
Solution: Don't check for an abbreviation after moving around in Insert mode.
Files: src/edit.c
Patch 5.6.066
Problem: Still a few bold character spill-over remains after patch 60.
Solution: Clear character just in front of blanking out rest of the line.
(Robert Webb)
Files: src/screen.c
Patch 5.6.067
Problem: When a file name contains a NL, the viminfo file is corrupted.
Solution: Use viminfo_writestring() to convert the NL to CTRL-V n.
Also fix the Buffers menu and listing a menu name with a newline.
Files: runtime/menu.vim, src/buffer.c, src/mark.c, src/menu.c
Patch 5.6.068
Problem: Compiling the Perl interface doesn't work with Perl 5.6.0.
(Bernhard Rosenkraenzer)
Solution: Also check xs_apiversion for the version number when prepending
defines for PL_*.
Files: src/Makefile
Patch 5.6.069
Problem: "go" doesn't always end up at the right character when
'fileformat' is "dos". (Bruce DeVisser)
Solution: Correct computations in ml_find_line_or_offset().
Files: src/memline.
Patch 5.6.070 (depends on 5.6.068)
Problem: Compiling the Perl interface doesn't work with Perl 5.6.0.
(Bernhard Rosenkraenzer)
Solution: Simpler check instead of the one from patch 68.
Files: src/Makefile
Patch 5.6.071
Problem: "A" in Visual block mode on a Tab positions the cursor one char to
the right. (Michael Haumann)
Solution: Correct the column computation in op_insert().
Files: src/ops.c
Patch 5.6.072
Problem: When starting Vim with "vim +startinsert", it enters Insert mode
only after typing the first command. (Andrew Pimlott)
Solution: Insert a dummy command in the stuff buffer.
Files: src/main.c
Patch 5.6.073 (extra) (depends on 5.6.034)
Problem: Win32 GUI: When compiled with Bcc 5.5 menus don't work.
In dosinst.c toupper() and tolower() give an "internal compiler
error" for Bcc 5.5.
Solution: Define WINVER to 4 to avoid compiling for Windows 2000. (Dan
Sharp) Also cleaned up compilation arguments.
Use our own implementation of toupper() in dosinst.c. Use
mytoupper() instead of tolower().
Files: src/Makefile.bor, src/dosinst.c
Patch 5.6.074 (extra)
Problem: Entering CSI directly doesn't always work, because it's recognized
as the start of a special key. Mostly a problem with multi-byte
in the GUI.
Solution: Use K_CSI for a typed CSI character. Use <CSI> for a normal CSI,
<xCSI> for a CSI typed in the GUI.
Files: runtime/doc/intro.txt, src/getchar.c, src/gui_amiga.c,
src/gui_gtk_x11.c, src/gui_mac.c, src/gui_riscos.c, src/gui_w32.c,
src/keymap.h, src/misc2.c
Patch 5.6.075
Problem: When using "I" or "A" in Visual block mode while 'sts' is set may
change spaces to a Tab the inserted text is not correct. (Mike
Steed) And some other problems when using "A" to append after the
end of the line.
Solution: Check for change in spaces/tabs after inserting the text. Append
spaces to fill the gap between the end-of-line and the right edge
of the block.
Files: src/ops.c
Patch 5.6.076
Problem: GTK GUI: Mapping <M-Space> doesn't work.
Solution: Don't use the "Alt" modifier twice in key_press_event().
Files: src/gui_gtk_x11.c
Patch 5.6.077
Problem: GUI: When interrupting an external program with CTRL-C, gvim might
crash. (Benjamin Korvemaker)
Solution: Avoid using a NULL pointer in ui_inchar_undo().
Files: src/ui.c
Patch 5.6.078
Problem: Locale doesn't always work on FreeBSD. (David O'Brien)
Solution: Link with the "xpg4" library when available.
Files: src/configure.in, src/configure
Patch 5.6.079
Problem: Vim could crash when several Tcl interpreters are created and
destroyed.
Solution: handle the "exit" command and nested ":tcl" commands better. (Ingo
Wilken)
Files: runtime/doc/if_tcl.txt, src/if_tcl.c
Patch 5.6.080
Problem: When jumping to a tag, generating the tags file and jumping to the
same tag again uses the old search pattern. (Sung-Hyun Nam)
Solution: Flush cached tag matches when executing an external command.
Files: src/misc2.c, src/proto/tag.pro, src/tag.c
Patch 5.6.081
Problem: ":syn include" uses a level for the included file, this confuses
contained items included at the same level.
Solution: Use a unique tag for each included file. Changed sp_syn_inc_lvl
to sp_syn_inc_tag. (Scott Bigham)
Files: src/syntax.c, src/structs.h
Patch 5.6.082
Problem: When using cscope, Vim can crash.
Solution: Initialize tag_fname in find_tags(). (Anton Blanchard)
Files: src/tag.c
Patch 5.6.083 (extra)
Problem: Win32: The visual beep can't be seen. (Eric Roesinger)
Solution: Flush the output before waiting with GdiFlush(). (Maurice S. Barnum)
Also: Allow specifying the delay in t_vb for the GUI.
Files: src/gui.c, src/gui_amiga.c, src/gui_gtk_x11.c, src/gui_mac.c,
src/gui_riscos.c, src/gui_w32.c, src/gui_x11.c, src/gui_beos.cc,
src/proto/gui_amiga.pro, src/proto/gui_gtk_x11.pro,
src/proto/gui_mac.pro, src/proto/gui_riscos.pro,
src/proto/gui_w32.pro, src/proto/gui_x11.pro,
src/proto/gui_beos.pro
Patch 5.6.084 (depends on 5.6.074)
Problem: GUI: Entering CSI doesn't always work for Athena and Motif.
Solution: Handle typed CSI as <xCSI> (forgot this bit in 5.6.074).
Files: src/gui_x11.c
Patch 5.6.085
Problem: Multi-byte: Using "r" to replace a double-byte char with a
single-byte char moved the cursor one character. (Matsumoto)
Also, using a count when replacing a single-byte char with a
double-byte char didn't work.
Solution: Don't use del_char() to delete the second byte.
Get "ptr" again after calling ins_char().
Files: src/normal.c
Patch 5.6.086 (extra)
Problem: Win32: When using libcall() and the returned value is not a valid
pointer, Vim crashes.
Solution: Use IsBadStringPtr() to check if the pointer is valid.
Files: src/os_win32.c
Patch 5.6.087
Problem: Multi-byte: Commands and messages with multi-byte characters are
displayed wrong.
Solution: Detect double-byte characters. (Yasuhiro Matsumoto)
Files: src/ex_getln.c, src/message.c, src/misc2.c, src/screen.c
Patch 5.6.088
Problem: Multi-byte with Motif or Athena: The message "XIM requires
fontset" is annoying when Vim was compiled with XIM support but it
is not being used.
Solution: Remove that message.
Files: src/multbyte.c
Patch 5.6.089
Problem: On non-Unix systems it's possible to overwrite a read-only file
without using "!".
Solution: Check if the file permissions allow overwriting before moving the
file to become the backup file.
Files: src/fileio.c
Patch 5.6.090
Problem: When editing a file in "/home/dir/home/dir" this was replaced with
"~~". (Andreas Jellinghaus)
Solution: Replace the home directory only once in home_replace().
Files: src/misc1.c
Patch 5.6.091
Problem: When editing many "no file" files, can't create swap file, because
.sw[a-p] have all been used. (Neil Bird)
Solution: Also use ".sv[a-z]", ".su[a-z]", etc.
Files: src/memline.c
Patch 5.6.092
Problem: FreeBSD: When setting $TERM to a non-valid terminal name, Vim
hangs in tputs().
Solution: After tgetent() returns an error code, call it again with the
terminal name "dumb". This apparently creates an environment in
which tputs() doesn't fail.
Files: src/term.c
Patch 5.6.093 (extra)
Problem: Win32 GUI: "ls | gvim -" will show a message box about reading
stdin when Vim exits. (Donohue)
Solution: Don't write a message about the file read from stdin until the GUI
has started.
Files: src/fileio.c
Patch 5.6.094
Problem: Problem with multi-byte string for ":echo var".
Solution: Check for length in msg_outtrans_len_attr(). (Sung-Hyun Nam)
Also make do_echo() aware of multi-byte characters.
Files: src/eval.c, src/message.c
Patch 5.6.095
Problem: With an Emacs TAGS file that include another a relative path
doesn't always work.
Solution: Use expand_tag_fname() on the name of the included file.
(Utz-Uwe Haus)
Files: src/tag.c
Patch 5.6.096
Problem: Unix: When editing many files, startup can be slow. (Paul
Ackersviller)
Solution: Halve the number of stat() calls used to add a file to the buffer
list.
Files: src/buffer.c
--
The average life of an organization chart is six months. You can safely
ignore any order from your boss that would take six months to complete.
(Scott Adams - The Dilbert principle)
/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\-\-- Vim: http://www.vim.org ---- ICCF Holland: http://www.vim.org/iccf --/-/
Announcing: Vim (Vi IMproved) version 5.7
Author: Bram Moolenaar et al.
Announcement
------------
This is a bug-fix release of Vim. Since version 5.6 bugs have been fixed and
a few improvements have been made.
Vim 5.7 has been tested by quite a few people over the past weeks, and there
are no big changes since version 5.6. 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/2000, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and Amiga.
For more information, see "http://www.vim.org".
New since version 5.6
---------------------
Not much:
- 19 new syntax files.
- "explorer.vim" script, works like a file browser.
And many bug fixes! This version is aimed at stability.
See ":help version-5.7" 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.7-src.tar.gz Unix(*) Sources.
unix/vim-5.7-rt.tar.gz Unix(*) Runtime files.
extra/vim-5.7-extra.tar.gz Unix(*) Extra sources and docs (Farsi, OLE, VisVim).
unix/vim-5.6-5.7-rt.diff.gz Runtime diff with version 5.6.
unix/vim-5.6-5.7-src.diff.gz Sources diff with version 5.6.
extra/vim-5.6-5.7-extra.diff.gz Extra diff with version 5.6.
pc/vim57rt.zip Win32 MS-DOS and MS-Windows runtime files.
pc/gvim57.zip Win32 32 bit MS-Windows 95/98/NT/2000 GUI
binaries.
Recommended for MS-Windows 95/98/NT/2000.
The best choice for syntax highlighting and
speed.
pc/gvim57ole.zip Win32 32 bit MS-Windows 95/98/NT/2000 GUI
binaries, with OLE support and VisVim.
pc/gvim57_s.zip Win32s 32 bit MS-Windows 3.1/3.11 GUI binaries.
Requires Win32s.
pc/vim57w32.zip Win32 32 bit MS-Windows 95/98/NT/2000 console
binaries. Recommended for Windows NT/2000,
NOT for 95/98. Supports long file names.
pc/vim57d32.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/2000).
pc/vim57d16.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/vim57src.zip PC Sources for PC versions (with CR-LF).
os2/vim57rt.zip OS/2 Runtime files (same as pc/vim57rt.zip).
os2/vim57os2.zip OS/2 Binaries.
(use the Unix archives for sources)
amiga/vim57rt.tgz Amiga Runtime files.
amiga/vim57bin.tgz Amiga Binaries.
amiga/vim57big.tgz Amiga Binaries with more features.
amiga/vim57src.tgz Amiga Sources for Amiga.
doc/vim57html.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:
103. When you find yourself in the "Computer" section of Barnes & Noble
enjoying yourself.
/-/-- Bram Moolenaar --- Bram@... --- http://www.moolenaar.net --\-\
\-\-- Vim: http://www.vim.org ---- ICCF Holland: http://www.vim.org/iccf --/-/
Invitation for Vim presentation
There will be a presentation about Vim on the WAN event (We Are Networking).
This is a camp site in the north-east of Holland where computer enthousiasts
meet for a week. More info about WAN: http://www.wan.nl .
I will do the presentation on Saturday July 29, starting at 14:30h. Everybody
is welcome to listen and discuss about Vim. If possible, there will also be a
workshop to tackle some Vim issues. Perhaps we can implement a new feature
together?
There is an entrance fee, they provide a whole program for that. Before my
presentation there is another one on Sendmail. You can spend the night there
(if you bring a tent). I have never been there before, but it looks like
there is going to be a lot of fun besides the serious computer stuff.
Depending on the audience the presentation will be in Dutch or English. There
will be plenty of time to meet Vim users and developers (and me!).
--
Microsoft's definition of a boolean: TRUE, FALSE, MAYBE
"Embrace and extend"...?
/// Bram Moolenaar Bram@... http://www.moolenaar.net \\\
\\\ Vim: http://www.vim.org ICCF Holland: http://iccf-holland.org ///
There will be two conferences at which I will give a speech related to Vim.
Both are in the Netherlands, in "De Reehorst", Ede.
Tuesday October 10: Linux2000 conference http://www.linux2000.nl
Time: 12.10 - 12.55
Title: The continuing story of Vim
Entrance is free, but you do need to register in advance. See the web site.
The conference starts on Monday. Eric S. Raymond will do two speeches, should
be interesting.
Thursday November 9: NLUUG najaarsconferentie http://www.nluug.nl
Time: 15:30 - 16:15
Title: Seven habits of effective text editing
I'm not sure if the entrance is free. It certainly is for members of the
NLUUG. Check the web site.
I expect to do both speeches in Dutch, but if there are a few people who don't
understand Dutch I'll switch to English.
--
hundred-and-one symptoms of being an internet addict:
130. You can't get out of your desk even if it's time to eat or time
to go to the bathroom.
/// Bram Moolenaar Bram@... http://www.moolenaar.net \\\
\\\ Vim: http://www.vim.org ICCF Holland: http://iccf-holland.org ///
Yesterday I have done a presentation on the Linux2000 conference in Ede,
Holland. About a hundred people attended and hopefully enjoyed it.
The conference was quite interesting and well attended (about 1500 attendees).
Eric S. Raymond did two speeches. He has a nice way of explaining things!
For those who are interested, the paper and presentation slides (with notes)
of the presentation I did are available on my web site:
http://www.moolenaar.net
The paper is small and plain text. The presentation is in PowerPoint format,
about 230 Kbyte. I also added a PostScript version of it, but it's very big
(over 600 Kbyte when gzip'ed) and in ghostview it didn't look nice. But it's
readable. If someone knows how to make a better PostScript file (or PDF), let
me know.
The presentation I will do on November 9, at the NLUUG najaarsconferentie,
will be a completely different one:
Thursday November 9: NLUUG najaarsconferentie
URL: http://www.nluug.nl/events/nj2000
Location: the Netherlands, in Ede.
Time: 15:30 - 16:15
Title: Seven habits of effective text editing
I'm not sure if the entrance is free. It certainly is for members of the
NLUUG. Check the web site.
I expect to do the speech in Dutch, but if there are a few people who don't
understand Dutch I'll switch to English.
--
hundred-and-one symptoms of being an internet addict:
130. You can't get out of your desk even if it's time to eat or time
to go to the bathroom.
/// Bram Moolenaar Bram@... http://www.moolenaar.net \\\
\\\ Vim: http://www.vim.org ICCF Holland: http://iccf-holland.org ///
Last Thursday I have done a presentation at the NLUUG conference in Ede,
Holland. About two hundred people attended and hopefully enjoyed it.
The title of the presentation is:
Seven habits of effective text editing
For those who are interested, the paper and presentation slides (with notes)
of the presentation I did are available on my web site:
http://www.moolenaar.net
The paper is small and available as plain text, MS-Word, PostScript and PDF.
The presentation was made in PowerPoint format, also available as PostScript
and PDF. Thanks to Yochai Meromi for generating the PDF files.
You probably want to get both the paper and the presentation, because the
paper contains better text and the presentation has a few nice pictures.
--
hundred-and-one symptoms of being an internet addict:
102. When filling out your driver's license application, you give
your IP address.
/// Bram Moolenaar Bram@... http://www.moolenaar.net \\\
\\\ Vim: http://www.vim.org ICCF Holland: http://iccf-holland.org ///
I have made a desktop calendar for 2001. On one side there is the usual
12-month info. On the other side you can find brief info about Vim and its
charity: ICCF-Holland.
It is available in English (A4 and Letter) and Dutch (A4), as PostScript
(compressed with gzip) and PDF. You can download it from my web site:
http://www.moolenaar.net
Merry Christmas and a Vim new year!
--
hundred-and-one symptoms of being an internet addict:
80. At parties, you introduce your spouse as your "service provider."
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim - http://www.vim.org -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Finally, the first book about Vim is here!
It's written by Steve Oualline and published by New Riders.
It is about 600 pages, and contains an awful lot of information.
For beginners it starts with explaining the basic commands, with pictures and
lots of examples. Gradually more advanced commands are introduced. Although
these are explained with less detail.
There is a large appendix that lists all the commands and options. A quick
reference as well.
You can find more information through this link:
http://www.iccf.nl/click5.html
This also allows you to order the book with a few on-line book stores where a
percentage of the sales goes to ICCF holland, to help children in Uganda.
You can find the book in other stores as well (might take some time before it
is available).
The book is published under the Open Publication License. I plan to include
parts of the text in the user manual for Vim 6.0. But that is still many
months away.
--
If VIM were a woman, I'd marry her. Slim, organized, helpful
and beautiful; what's not to like? --David A. Rogers
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim - http://www.vim.org -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Hello Vimmers,
This is a BETA version of Vim 5.8. It includes all patches that have been
sent out for 5.7, plus about 70 new syntax files.
The main reason for bringing out this beta version is that the syntax files
need testing. There are many new ones and the existing ones have been updated
and made ready for Vim 6.0 (which will still be unstable for a while). All
syntax file maintainers, please check for any problems!
If all goes well, version 5.8 will be released in about two weeks.
Note that all the files are under the "unreleased" directory at the ftp site.
It should also be available through CVS soon. See http://vim.sf.net.
WHERE TO GET IT
---------------
You can find Vim 5.8a here:
ftp://ftp.vim.org/pub/vim/unreleased/
See this file for Mirrors:
ftp://ftp.vim.org/pub/vim/MIRRORS
FILE SYSTEM COMMENTS
unix/vim-5.8a-src.tar.gz Unix(*) Sources
unix/vim-5.7-5.8a-src.diff.gz sources diff with version 5.7
unix/vim-5.8a-rt.tar.gz Unix(*) runtime files
unix/vim-5.7-5.8a-rt.diff.gz runtime diff with version 5.7
extra/vim-5.8a-extra.tar.gz Unix(*) Extra sources and docs (Farsi, OLE, VisVim)
extra/vim-5.7-5.8a-extra.diff.gz diff with version 5.7
pc/vim58art.zip Win32 DOS and MS-Windows runtime files
pc/gvim58a.zip Win32 32 bit Windows 95/98/NT GUI binaries.
Recommended for Windows 95/98 and NT. The
best choice for syntax highlighting and
speed.
pc/gvim58aole.zip Win32 32 bit Windows 95/98/NT GUI binaries, with
OLE support and VisVim.
pc/gvim58a_s.zip Win32s 32 bit Windows 3.1/3.11 GUI binaries.
Requires Win32s.
pc/vim58aw32.zip Win32 32 bit Windows console binaries.
Recommended for Windows NT, not for 95/98.
Supports long file names.
pc/vim58ad32.zip MS-DOS 32 bit protected mode binaries.
Recommended for MS-DOS, Windows 3.1 and
Windows 95/98 console. It is compiled with
DJGPP, it may need a DPMI driver (CWSDPMI
is included). Supports long file names on
Windows 95/98.
pc/vim58ad16.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/vim58asrc.zip PC Sources for PC versions (with CR-LF).
os2/vim58art.zip OS/2 runtime files (same as pc/vim58art.zip)
os2/vim58aos2.zip OS/2 binaries
(use the Unix and extra archives for OS/2
sources)
amiga/vim58art.tgz Amiga runtime files
amiga/vim58abin.tgz Amiga Binary
amiga/vim58abig.tgz Amiga Binary with more features
amiga/vim58asrc.tgz Amiga Sources for Amiga
doc/vim58ahtml.zip all Documentation converted to HTML
(*) 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
unzip file.zip
WHAT IS NEW
-----------
This is the complete list of changes since version 5.7.
Changed
-------
Ctags is no longer included with Vim. It has grown into a project of its own.
You can find it here: http://ctags.sf.net. It is highly recommended as a Vim
companion when you are writing programs.
Added
-----
New syntax files:
acedb AceDB (Stewart Morris)
aflex Aflex (Mathieu Clabaut)
antlr Antlr (Mathieu Clabaut)
asm68k 68000 Assembly (Steve Wall)
automake Automake (John Williams)
ayacc Ayacc (Mathieu Clabaut)
b B (Mathieu Clabaut)
bindzone BIND zone (glory hump)
blank Blank (Rafal Sulejman)
cfg Configure files (Igor Prischepoff)
changelog ChangeLog (Gediminas Paulauskas)
cl Clever (Phil Uren)
crontab Crontab (John Hoelzel)
csc Essbase script (Raul Segura Acevedo)
cynlib Cynlib(C++) (Phil Derrick)
cynpp Cyn++ (Phil Derrick)
debchangelog Debian Changelog (Wichert Akkerman)
debcontrol Debian Control (Wichert Akkerman)
dns DNS zone file (Jehsom)
dtml Zope's DTML (Jean Jordaan)
dylan Dylan, Dylan-intr and Dylan-lid (Brent Fulgham)
ecd Embedix Component Description (John Beppu)
fgl Informix 4GL (Rafal Sulejman)
foxpro FoxPro (Powing Tse)
gsp GNU Server Pages (Nathaniel Harward)
hercules Hercules (Avant! Corporation) (Dana Edwards)
htmlos HTML/OS by Aestiva (Jason Rust)
iss Inno Setup (Dominique Stephan)
jam Jam (Ralf Lemke)
jess Jess (Paul Baleme)
lprolog LambdaProlog (Markus Mottl)
ia64 Intel Itanium (parth malwankar)
kix Kixtart (Nigel Gibbs)
mgp MaGic Point (Gerfried Fuchs)
mason Mason (HTML with Perl) (Andrew Smith)
mma Mathematica (Wolfgang Waltenberger)
nqc Not Quite C (Stefan Scherer)
omnimark Omnimark (Paul Terray)
openroad OpenROAD (Luis Moreno Serrano)
named BIND configuration (glory hump)
papp PApp (Marc Lehmann)
pic PIC assembly (Aleksandar Veselinovic)
ppwiz PPWizard (Stefan Schwarzer)
progress Progress (Phil Uren)
psf Product Specification File (Rex Barzee)
r R (Tom Payne)
registry MS-Windows registry (Dominique Stephan)
robots Robots.txt (Dominique Stephan)
rtf Rich Text Format (Dominique Stephan)
setl SETL (Alex Poylisher)
sgmldecl SGML Declarations (Daniel A. Molina W.)
sinda Sinda input (Adrian Nagle)
sindacmp Sinda compare (Adrian Nagle)
sindaout Sinda output (Adrian Nagle)
smith SMITH (Rafal Sulejman)
snobol4 Snobol 4 (Rafal Sulejman)
strace Strace (David Necas)
tak TAK input (Adrian Nagle)
takcmp TAK compare (Adrian Nagle)
takout TAK output (Adrian Nagle)
tasm Turbo assembly (FooLman)
texmf TeX configuration (David Necas)
trasys Trasys input (Adrian Nagle)
tssgm TSS Geometry (Adrian Nagle)
tssop TSS Optics (Adrian Nagle)
tsscl TSS Command line (Adrian Nagle)
virata Virata Configuration Script (Manuel M.H. Stol)
vsejcl VSE JCL (David Ondrejko)
wdiff Wordwise diff (Gerfried Fuchs)
wsh Windows Scripting Host (Paul Moore)
xkb X Keyboard Extension (David Necas)
Renamed php3 to php, it now also supports php4 (Lutz Eymers)
Patch 5.7.015
Problem: Syntax files for Vim 6.0 can't be used with 5.x.
Solution: Add the "default" argument to the ":highlight" command: Ignore the
command if highlighting was already specified.
Files: src/syntax.c
Generate the Syntax menu with makemenu.vim, so that it doesn't have to be done
when Vim is starting up. Reduces the startup time of the GUI.
Fixed
-----
Conversion of docs to HTML didn't convert "|tag|s" to a hyperlink.
Fixed compiling under NeXT. (Jeroen C.M. Goudswaard)
optwin.vim gave an error when used in Vi compatible mode ('cpo' contains 'C').
Tcl interpreter: "buffer" command didn't check for precense of an argument.
(Dave Bodenstab)
dosinst.c: Added checks for too long file name.
Amiga: a file name starting with a colon was considered absolute but it isn't.
Amiga: ":pwd" added a slash when in the root of a drive.
Macintosh: Warnings for unused variables. (Bernhard Pruemmer)
Unix: When catching a deadly signal, handle it in such a way that it's
unlikely that Vim will hang. Call _exit() instead of exit() in case of a
severe problem.
Setting the window title from nothing to something didn't work after patch 29.
Check for ownership of .exrc and .vimrc was done with stat(). Use lstat() as
well for extra security.
Win32 GUI: Printing a file with 'fileformat' "unix" didn't work. Set
'fileformat' to "dos" before writing the temp file.
Unix: Could start waiting for a character when checking for a CTRL-C typed
when an X event is received.
Could not use Perl and Python at the same time on FreeBSD, because Perl used
"-lc" and Python used the threaded C library.
Previosly released patches for Vim 5.7:
Patch 5.7.001
Problem: When the current buffer is crypted, and another modified buffer
isn't, ":wall" will encrypt the other buffer.
Solution: In buf_write() use "buf" instead of "curbuf" to check for the
crypt key.
Files: src/fileio.c
Patch 5.7.002
Problem: When 'showmode' is set, using "CTRL-O :r file" waits three seconds
before displaying the read text. (Wichert Akkerman)
Solution: Set "keep_msg" to the file message so that the screen is redrawn
before the three seconds wait for displaying the mode message.
Files: src/fileio.c
Patch 5.7.003
Problem: Searching for "[[:cntrl:]]" doesn't work.
Solution: Exclude NUL from the matching characters, it terminates the list.
Files: src/regexp.c
Patch 5.7.004
Problem: GTK: When selecting a new font, Vim can crash.
Solution: In gui_mch_init_font() unreference the old font, not the new one.
Files: src/gui_gtk_x11.c
Patch 5.7.005
Problem: Multibyte: Inserting a wrapped line corrupts kterm screen.
Pasting TEXT/COMPOUND_TEXT into Vim does not work.
On Motif no XIM status line is displayed even though it is
available.
Solution: Don't use xterm trick for wrapping lines for multibyte mode.
Correct a missing "break", added TEXT/COMPOUND_TEXT selection
request.
Add XIMStatusArea fallback code.
(Katsuhito Nagano)
Files: src/gui_gtk_x11.c, src/multbyte.c, src/screen.c, src/ui.c
Patch 5.7.006
Problem: GUI: redrawing the non-Visual selection is wrong when the window
is unobscured. (Jean-Pierre Etienne)
Solution: Redraw the selection properly and don't clear it. Added "len"
argument to clip_may_redraw_selection().
Files: src/gui.c, src/ui.c, src/proto/ui.pro
Patch 5.7.007
Problem: Python: Crash when using the current buffer twice.
Solution: Increase the reference count for buffer and window objects.
(Johannes Zellner)
Files: src/if_python.c
Patch 5.7.008
Problem: In Ex mode, backspacing over the first TAB doesn't work properly.
(Wichert Akkerman)
Solution: Switch the cursor on before printing the newline.
Files: src/ex_getln.c
Patch 5.7.009 (extra)
Problem: Mac: Crash when using a long file.
Solution: Don't redefine malloc() and free(), because it will break using
realloc().
Files: src/os_mac.h
Patch 5.7.010
Problem: When using CTRL-A on a very long number Vim can crash. (Michael
Naumann)
Solution: Truncate the length of the new number to avoid a buffer overflow.
Files: src/ops.c
Patch 5.7.011 (extra)
Problem: Win32 GUI on NT 5 and Win98: Displaying Hebrew is reversed.
Solution: Output each character separately, to avoid that Windows reverses
the text for some fonts. (Ron Aaron)
Files: src/gui_w32.c
Patch 5.7.012
Problem: When using "-complete=buffer" for ":command" the user command
fails.
Solution: In a user command don't replace the buffer name with a count for
the buffer number.
Files: src/ex_docmd.c
Patch 5.7.013
Problem: "gD" didn't always find a match in the first line, depending on
the column the search started at.
Solution: Reset the column to zero before starting to search.
Files: src/normal.c
Patch 5.7.014
Problem: Rot13 encoding was done on characters with accents, which is
wrong. (Sven Gottwald)
Solution: Only do rot13 encoding on ASCII characters.
Files: src/ops.c
Patch 5.7.016
Problem: When hitting 'n' for a ":s///c" command, the ignore-case flag was
not restored, some matches were skipped. (Daniel Blaustein)
Solution: Restore the reg_ic variable when 'n' was hit.
Files: src/ex_cmds.c
Patch 5.7.017
Problem: When using a Vim script for Vim 6.0 with <SID> before a function
name, it produces an error message even when inside an "if version
>= 600". (Charles Campbell)
Solution: Ignore errors in the function name when the function is not going
to be defined.
Files: src/eval.c
Patch 5.7.018
Problem: When running "rvim" or "vim -Z" it was still possible to execute a
shell command with system() and backtick-expansion. (Antonios A.
Kavarnos)
Solution: Disallow executing a shell command in get_cmd_output() and
mch_expand_wildcards().
Files: src/misc1.c, src/os_unix.c
Patch 5.7.019
Problem: Multibyte: In a substitute string, a multi-byte character isn't
skipped properly, can be a problem when the second byte is a
backslash.
Solution: Skip an extra byte for a double-byte character. (Muraoka Taro)
Files: src/ex_cmds.c
Patch 5.7.020
Problem: Compilation doesn't work on MacOS-X.
Solution: Add a couple of #ifdefs. (Jamie Curmi)
Files: src/regexp.c, src/ctags/general.h
Patch 5.7.021
Problem: Vim sometimes produces a beep when started in an xterm. Only
happens when compiled without mouse support.
Solution: Requesting the xterm version results in a K_IGNORE. This wasn't
handled when mouse support is disabled. Accept K_IGNORE always.
Files: src/normal.c
Patch 5.7.022
Problem: %v in 'statusline' is not displayed when it's equal to %c.
Solution: Check if %V or %v is used and handle them differently.
Files: src/screen.c
Patch 5.7.023
Problem: Crash when a WinLeave autocommand deletes the buffer in the other
window.
Solution: Check that after executing the WinLeave autocommands there still
is a window to be closed. Also update the test that was supposed
to check for this problem.
Files: src/window.c, testdir/test13.in, testdir/test13.ok
Patch 5.7.024
Problem: Evaluating an expression for 'statusline' can have side effects.
Solution: Evaluate the expression in a sandbox.
Files: src/edit.c, src/eval.c, src/proto/eval.pro, src/ex_cmds.c,
src/ex_cmds.h, src/ex_docmd.c, src/globals.h, src/option.c,
src/screen.c, src/undo.c
Patch 5.7.025 (fixed)
Problem: Creating a temp file has a race condition.
Solution: Create a private directory to write the temp files in.
Files: src/fileio.c, src/misc1.c, src/proto/misc1.pro,
src/proto/fileio.pro, src/memline.c, src/os_unix.h
Patch 5.7.026 (extra)
Problem: Creating a temp file has a race condition.
Solution: Create a private directory to write the temp files in.
This is the extra part of patch 5.7.025.
Files: src/os_msdos.h
Patch 5.7.027
Problem: Starting to edit a file can cause a crash. For example when in
Insert mode, using CTRL-O :help abbr<Tab> to scroll the screen and
then <CR>, which edits a help file. (Robert Bogomip)
Solution: Check if keep_msg is NULL before copying it.
Files: src/fileio.c
Patch 5.7.028
Problem: Creating a backup or swap file could fail in rare situations.
Solution: Use O_EXCL for open().
Files: src/fileio.c, src/memfile.c
Patch 5.7.029
Problem: Editing a file with an extremely long name crashed Vim.
Solution: Check for length of the name when setting the window title.
Files: src/buffer.c
Patch 5.7.030
Problem: A ":make" or ":grep" command with a very long argument could cause
a crash.
Solution: Allocate the buffer for the shell command.
Files: src/ex_docmd.c
--
hundred-and-one symptoms of being an internet addict:
224. You set up your own Web page. You set up a Web page for each
of your kids... and your pets.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Hello Vimmer,
You might be interested in this article, which appeared in the June 2001 issue
of Linux Journal. It is about the relation between software in third world
countries. It's very well written and gives you a good idea of what people in
Africa really need. The last section is about Vim in Uganda.
Title: Algorithms in Africa
More common sense and less zeal may be the key to bridging the
information gap.
Author: Wayne Marshall
URL: http://www2.linuxjournal.com/lj-issues/issue86/4657.html
You could also get the magazine, the cover text appears to apply to Vim as
well. :-)
--
MICHAEL PALIN PLAYED: 1ST SOLDIER WITH A KEEN INTEREST IN BIRDS, DENNIS, MR
DUCK (A VILLAGE CARPENTER WHO IS ALMOST KEENER THAN
ANYONE ELSE TO BURN WITCHES), THREE-HEADED KNIGHT, SIR
GALAHAD, KING OF SWAMP CASTLE, BROTHER MAYNARD'S ROOMATE
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Announcing: Vim (Vi IMproved) version 5.8
Author: Bram Moolenaar et al.
Announcement
------------
This is a minor release of Vim. Since version 5.7 has been released (almost
a year ago!) bugs have been fixed and many syntax files have been added.
Vim 5.8 has been tested by quite a few people over the past weeks, and there
are no big changes since version 5.7. This should be the most stable Vim
version ever. But it's free software, the usual disclaimers apply.
Development of Vim 6.0, the next major release, continues. That version
contains many new features and is an unstable version.
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/ME/NT/2000/XP, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and
Amiga.
For more information, see "http://www.vim.org" and "http://vim.sf.net".
New since version 5.7
---------------------
74 new syntax files.
Quite a few bug fixes. This version is aimed at stability.
A few security problems were fixed.
Ctags is no longer included, it has grown into a project of its own. You can
find it at http://ctags.sf.net.
See ":help version-5.8" 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.8-src.tar.gz Unix(*) Sources.
unix/vim-5.8-rt.tar.gz Unix(*) Runtime files.
extra/vim-5.8-extra.tar.gz Unix(*) Extra sources and docs (Farsi, OLE, VisVim).
unix/vim-5.7-5.8-rt.diff.gz Runtime diff with version 5.7.
unix/vim-5.7-5.8-src.diff.gz Sources diff with version 5.7.
extra/vim-5.7-5.8-extra.diff.gz Extra diff with version 5.7.
pc/vim58rt.zip Win32 MS-DOS and MS-Windows runtime files. This
doesn't fit on a floppy, alternatively get
the next two files.
pc/vim58rt1.zip Win32 Same, except the syntax files.
pc/vim58rt2.zip Win32 Same, only the syntax files.
pc/gvim58.zip Win32 32 bit MS-Windows 95/98/NT/2000 GUI
binaries.
Recommended for MS-Windows 95/98/NT/2000.
The best choice for syntax highlighting and
speed.
pc/gvim58ole.zip Win32 32 bit MS-Windows 95/98/NT/2000 GUI
binaries, with OLE support and VisVim.
pc/gvim58_s.zip Win32s 32 bit MS-Windows 3.1/3.11 GUI binaries.
Requires Win32s.
pc/vim58w32.zip Win32 32 bit MS-Windows 95/98/NT/2000 console
binaries. Recommended for Windows NT/2000,
NOT for 95/98. Supports long file names.
pc/vim58d32.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/2000).
pc/vim58d16.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/vim58src.zip PC Sources for PC versions (with CR-LF).
os2/vim58rt.zip OS/2 Runtime files (same as pc/vim58rt.zip).
os2/vim58os2.zip OS/2 Binaries.
(use the Unix archives for sources)
amiga/vim58rt.tgz Amiga Runtime files.
amiga/vim58bin.tgz Amiga Binaries.
amiga/vim58big.tgz Amiga Binaries with more features.
amiga/vim58src.tgz Amiga Sources for Amiga.
doc/vim58html.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!
--
"Oh, no! NOT the Spanish Inquisition!"
"NOBODY expects the Spanish Inquisition!!!"
-- Monty Python sketch --
"Oh, no! NOT another option!"
"EVERYBODY expects another option!!!"
-- Discussion in vim-dev mailing list --
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Short version:
New site. http://vim.sf.net. Enjoy!
Long version:
Inspired by www.php.net, Scott Johnston and Jonathan Morace have written a
portal for Vim users called Vim online (http://vim.sf.net). It combines the
vim-tips site and some of the concepts from the VUR. Scripts and tips can be
added by the site and then rated by the community.
(http://vim.sf.net/karma.php)
As you release modifications of your scripts you can add them as new versions
to the original script you uploaded. Users can download the version of their
choice. Scripts can be uploaded as single text files or as compressed bundles
(zip,tar,gzip) if a script requires several different files.
Bug reports should go to vimonline-support@... or you can
contact them directly at scrott@... and
jmorace@.... Please include browser information and screen
shots if applicable.
Enjoy!
--
hundred-and-one symptoms of being an internet addict:
92. It takes you two hours to check all 14 of your mailboxes.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
I have started a list of mistakes in the Vim book. This varies from simple
typos to annoying errors in examples.
You can find the page here:
http://www.moolenaar.net/vim_errata.html
If you find a mistake in the book that isn't in the list yet, or perhaps an
item in the errata list that's wrong, send me a message. Preferably use the
same format as used on the page.
--
ARTHUR: Charge!
[They all charge with swords drawn towards the RABBIT. A tremendous twenty
second fight with Peckinpahish shots and borrowing heavily also on the
Kung Fu and karate-type films ensues, in which some four KNIGHTS are
comprehensively killed.]
ARTHUR: Run away! Run away!
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Announcing: Vim (Vi IMproved) version 6.0ap
Author: Bram Moolenaar et al.
Announcement
------------
This is a BETA test version of Vim. It is a huge step from Vim 5.x. Many,
many new features and improvements have been included. For an overview, with
a few screendumps, look here:
http://vim.sf.net/whyvim.php
Vim 6.0 has been in alpha testing for quite a while. Although it appears to
work well, it needs to be tested before we can say it is really stable.
Expect to run into a few problems.
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/ME/NT/2000/XP, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and
Amiga.
For more information, see http://vim.sf.net.
New since version 5.8
---------------------
The number of changes is huge. These are just the main new items:
Folding - momentarily hide part of the text
Vertically split windows - mixed with horizontal splits
Diff mode - show and remove differences between files
Easy Vim: click-and-type - for those who really don't like two modes
User manual - learn to use Vim, reads like a book
Flexible indenting - automatic indenting for any language
Extended search patterns - more regexp power than you will need
UTF-8 support - Unicode allows editing nearly all languages
Multi-language support - translated messages and menus
Plugin support - drop a script in a directory and you can use it
Filetype plugins - an easy way to setup for editing a type of file
File browser - browse directories, also on a terminal
Editing files over a network - read and write a remote files directly
command-line editing window - use any Vim command to edit an Ex command
Debugging mode - debug your Vim functions and scripts
Cursor in virtual position - edit tables and draw ASCII pictures
Debugger interface - use Vim with Sun Visual Workshop
Communication between Vims - let one Vim tell another Vim what to do
Printing - print with syntax colors (MS-Windows only)
Quickfix extended - see error messages in a window and jump there
Writing files improved - rename or copy to make a backup file
Argument list - select groups of files to work on
Restore a View - save the looks of a window and restore it later
Color schemes - quickly switch between different color setups
See this page for the details:
http://vim.sf.net/htmldoc/version6.html
Where to get it
---------------
Information about which files to download for what system:
http://vim.sf.net/download.php
If you already know what to get, download it from here:
ftp://ftp.vim.org/pub/vim/unreleased
Or use one of the mirrors, see:
ftp://ftp.vim.org/pub/vim/MIRRORS
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://groups.yahoo.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://groups.yahoo.com/group/vimdev.
Subject specific lists:
Multi-byte issues: vim-multibyte http://groups.yahoo.com/group/vim-multibyte
Macintosh issues: vim-mac http://groups.yahoo.com/group/vim-mac
Reporting bugs
--------------
Send them to <bugs@...>. Please describe the problem precisely. 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 starting
without your own vimrc file: "vim -u NONE -U NONE". 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!
--
From "know your smileys":
:-X My lips are sealed
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Announcing: Vim (Vi IMproved) version 6.0ar BETA
Author: Bram Moolenaar et al.
Announcement
------------
This is a BETA test version of Vim. It is a huge step from Vim 5.x. Many,
many new features and improvements have been included. For an overview, with
a few screendumps, look here:
http://vim.sf.net/whyvim.php
After two weeks of beta testing it looks quite good. Some bugs have been
found and fixed. Bug reports are still coming in, thus beta testing will
continue (estimation: five or six weeks). Fortunately, no real big problems
have been found.
If you are upgrading from Vim 5.x, please look out for problems you run into.
Vim 6.0 is mostly backwards compatible, but not 100%. Check out ":help
version6" for known incompatibilities. If you find a problem that can be
solved, please report it to me.
Details about changes since the first beta can be found in these messages:
http://groups.yahoo.com/group/vimdev/message/23413http://groups.yahoo.com/group/vimdev/message/23598
If you are using ":hardcopy" on a non-MS-Windows system, get this patch:
http://groups.yahoo.com/group/vimdev/message/23606
Currently we are still working on three main issues. Hopefully these can be
finished soon, so that we can wrap up the beta testing:
- Make --remote-wait work for MS-Windows and related inter-Vim communication.
- Improve printing, mostly for PostScript.
- Font/fontset issues for Motif and Athena.
We could use a bit of help!
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/ME/NT/2000/XP, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and
Amiga.
For more information, see http://vim.sf.net.
New since version 5.8
---------------------
The number of changes is huge. These are just the main new items:
Folding - momentarily hide part of the text
Vertically split windows - mixed with horizontal splits
Diff mode - show and remove differences between files
Easy Vim: click-and-type - for those who really don't like two modes
User manual - learn to use Vim, reads like a book
Flexible indenting - automatic indenting for any language
Extended search patterns - more regexp power than you will need
UTF-8 support - Unicode allows editing nearly all languages
Multi-language support - translated messages and menus
Plugin support - drop a script in a directory and you can use it
Filetype plugins - an easy way to setup for editing a type of file
File browser - browse directories, also on a terminal
Editing files over a network - read and write a remote files directly
command-line editing window - use any Vim command to edit an Ex command
Debugging mode - debug your Vim functions and scripts
Cursor in virtual position - edit tables and draw ASCII pictures
Debugger interface - use Vim with Sun Visual Workshop
Communication between Vims - let one Vim tell another Vim what to do
Printing - print with syntax colors
Quickfix extended - see error messages in a window and jump there
Writing files improved - rename or copy to make a backup file
Argument list - select groups of files to work on
Restore a View - save the looks of a window and restore it later
Color schemes - quickly switch between different color setups
See this page for the details:
http://vim.sf.net/htmldoc/version6.html
Where to get it
---------------
Information about which files to download for what system:
http://vim.sf.net/download.php
If you already know what to get, download it from here:
ftp://ftp.vim.org/pub/vim/unreleased
Or use one of the mirrors, see:
ftp://ftp.vim.org/pub/vim/MIRRORS
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://groups.yahoo.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://groups.yahoo.com/group/vimdev.
Subject specific lists:
Multi-byte issues: vim-multibyte http://groups.yahoo.com/group/vim-multibyte
Macintosh issues: vim-mac http://groups.yahoo.com/group/vim-mac
Reporting bugs
--------------
Send them to <bugs@...>. Please describe the problem precisely. 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 starting
without your own vimrc file: "vim -u NONE -U NONE". 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!
--
"I love deadlines. I especially like the whooshing sound they
make as they go flying by."
-- Douglas Adams
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
An article appeared on the Linux Journal web site:
"Vi IMproved--Vim and Happy Hacking Keyboard Lite 2"
Written by Don Marti. Despite the title it's also a review on the Vim
book by Steve Oualline. You can read it here:
http://www.linuxjournal.com/articles/linux_review/0055.html
If you want to get a copy of the Vim book, using the URL below will give
a percentage of the sales to poor children in Uganda:
http://www.vim.org/iccf/click5.html
The second quarter of 2001 resulted in about $700. Thanks to all who
helped!
--
If your life is a hard drive,
Christ can be your backup.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Announcing: Vim (Vi IMproved) version 6.0au BETA
Author: Bram Moolenaar et al.
Announcement
------------
This is a BETA test version of Vim. Vim 6.0 is a huge step from Vim
5.x. Many, many new features and improvements have been included. For
an overview, with a few screendumps, look here:
http://vim.sf.net/whyvim.php
After five weeks of beta testing it looks very good. Bugs have been found
and fixed. All main issues have been taken care of. Thanks to all people
who reported problems and helped fixing them!
The main items that have been done the past weeks is the client-server
functionality and PostScript printing. The client-server communication now
also works well on MS-Windows. The "--remote" argument and friends are now
portable between Unix and MS-Windows. PostScript printing has been enhanced
to support more settings and work better with various printers.
Bug reports are still coming in, thus beta testing will continue (estimation:
two weeks). If you notice a problem, please report it! It would be annoying
if Vim 6.0 will be released with a problem that could have been fixed if you
would have reported it.
If you are upgrading from Vim 5.x, please look out for problems you run into.
Vim 6.0 is mostly backwards compatible, but not 100%. Check out ":help
version6" for known incompatibilities. If you find a problem that can be
solved, please report it to me.
Details about changes since the first beta can be found in these messages:
6.0aq http://groups.yahoo.com/group/vimdev/message/23413
6.0ar http://groups.yahoo.com/group/vimdev/message/23598
6.0as http://groups.yahoo.com/group/vimdev/message/23730
6.0at http://groups.yahoo.com/group/vimdev/message/23941
6.0au http://groups.yahoo.com/group/vimdev/message/24252
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/ME/NT/2000/XP, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and
Amiga.
For more information, see http://vim.sf.net.
New since version 5.8
---------------------
The number of changes is huge. These are just the main new items:
Folding - momentarily hide part of the text
Vertically split windows - mixed with horizontal splits
Diff mode - show and remove differences between files
Easy Vim: click-and-type - for those who really don't like two modes
User manual - learn to use Vim, reads like a book
Flexible indenting - automatic indenting for any language
Extended search patterns - more regexp power than you will need
UTF-8 support - Unicode allows editing nearly all languages
Multi-language support - translated messages and menus
Plugin support - drop a script in a directory and you can use it
Filetype plugins - an easy way to setup for editing a type of file
File browser - browse directories, also on a terminal
Editing files over a network - read and write a remote files directly
command-line editing window - use any Vim command to edit an Ex command
Debugging mode - debug your Vim functions and scripts
Cursor in virtual position - edit tables and draw ASCII pictures
Debugger interface - use Vim with Sun Visual Workshop
Communication between Vims - let one Vim tell another Vim what to do
Printing - print with syntax colors
Quickfix extended - see error messages in a window and jump there
Writing files improved - rename or copy to make a backup file
Argument list - select groups of files to work on
Restore a View - save the looks of a window and restore it later
Color schemes - quickly switch between different color setups
See this page for the details:
http://vim.sf.net/htmldoc/version6.html
Where to get it
---------------
Information about which files to download for what system:
http://vim.sf.net/download.php
If you already know what to get, download it from here:
ftp://ftp.vim.org/pub/vim/unreleased
Or use one of the mirrors, see:
ftp://ftp.vim.org/pub/vim/MIRRORS
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://groups.yahoo.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://groups.yahoo.com/group/vimdev.
Subject specific lists:
Multi-byte issues: vim-multibyte http://groups.yahoo.com/group/vim-multibyte
Macintosh issues: vim-mac http://groups.yahoo.com/group/vim-mac
Reporting bugs
--------------
Send them to <bugs@...>. Please describe the problem precisely. 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 starting
without your own vimrc file: "vim -u NONE -U NONE". Try different machines
if possible. See ":help bugs" in Vim. Send me a patch 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!
--
It is illegal for anyone to give lighted cigars to dogs, cats, and other
domesticated animal kept as pets.
[real standing law in Illinois, United States of America]
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
This is about Vim's charity, helping poor children in Uganda.
NEWSLETTER
Jackie Ammeter, the person that handles the administration of sponsored
children in Kibaale, has written a nice overview with news about
progress at the project. You can find it here:
http://www.iccf.nl/news.html
USA TAX RETURN
It's always nice if the tax people pay part of a donation to a charity.
So far this was only possible for people living the Holland and Canada.
It has now become clear that donations to KCF in Vancouver are valid for
a tax return when you live in the USA. This has been confirmed by a
lawyer in the USA. Here is the updated information:
USA and Canada: Contact Kibaale Children's Fund (KCF) in Surrey, Canada. They
take care of the Canadian sponsors for the children in
Kibaale. You can send them a one time donation directly.
Please send me a note so that know what has been donated
because of Vim. Ask KCF for information about sponsorship.
Kibaale Children's Fund c/o Pacific Academy
10238-168 Street
Surrey, B.C. V4N 1Z4
Canada
Phone: 604-581-5353
If you make a donation to Kibaale Children's Fund (KCF) you
will receive a tax receipt which can be submitted with your
tax return (under the Free Trade Agreement tax receipts issued
by an organization registered in Canada are fully accepted by
the IRS in the USA).
We are still working on a method to make tax reduction possible in
Germany.
--
hundred-and-one symptoms of being an internet addict:
143. You dream in pallettes of 216 websafe colors.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Announcing: Vim (Vi IMproved) version 6.0ax BETA
Author: Bram Moolenaar et al.
Announcement
------------
This is a BETA test version of Vim. Vim 6.0 is a huge step from Vim
5.x. Many, many new features and improvements have been included. For
an overview, with a few screendumps, look here:
http://vim.sf.net/whyvim.php
The past two weeks many bugs have been fixed. This release is to check
if no mistakes were made. If nothing important comes up, 6.0 will be
released in a few days. Thanks to all people who reported problems and
helped fixing them!
If you notice a problem, please report it! It would be annoying if Vim
6.0 will be released with a problem that could have been fixed if you
would have reported it.
If you are upgrading from Vim 5.x, please look out for problems you run into.
Vim 6.0 is mostly backwards compatible, but not 100%. Check out ":help
version6" for known incompatibilities. If you find a problem that can be
solved, please report it to me.
Details about changes since the first beta can be found in these messages:
6.0aq http://groups.yahoo.com/group/vimdev/message/23413
6.0ar http://groups.yahoo.com/group/vimdev/message/23598
6.0as http://groups.yahoo.com/group/vimdev/message/23730
6.0at http://groups.yahoo.com/group/vimdev/message/23941
6.0au http://groups.yahoo.com/group/vimdev/message/24252
6.0av http://groups.yahoo.com/group/vimdev/message/24546
6.0aw http://groups.yahoo.com/group/vimdev/message/24841
6.0ax http://groups.yahoo.com/group/vimdev/message/25061
You can find the most recent patches here:
ftp://ftp.vim.org/pub/vim/unreleased/patches
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/ME/NT/2000/XP, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and
Amiga.
For more information, see http://vim.sf.net.
New since version 5.8
---------------------
The number of changes is huge. These are just the main new items:
Folding - momentarily hide part of the text
Vertically split windows - mixed with horizontal splits
Diff mode - show and remove differences between files
Easy Vim: click-and-type - for those who really don't like two modes
User manual - learn to use Vim, reads like a book
Flexible indenting - automatic indenting for any language
Extended search patterns - more regexp power than you will need
UTF-8 support - Unicode allows editing nearly all languages
Multi-language support - translated messages and menus
Plugin support - drop a script in a directory and you can use it
Filetype plugins - an easy way to setup for editing a type of file
File browser - browse directories, also on a terminal
Editing files over a network - read and write a remote files directly
command-line editing window - use any Vim command to edit an Ex command
Debugging mode - debug your Vim functions and scripts
Cursor in virtual position - edit tables and draw ASCII pictures
Debugger interface - use Vim with Sun Visual Workshop
Communication between Vims - let one Vim tell another Vim what to do
Printing - print with syntax colors
Quickfix extended - see error messages in a window and jump there
Writing files improved - rename or copy to make a backup file
Argument list - select groups of files to work on
Restore a View - save the looks of a window and restore it later
Color schemes - quickly switch between different color setups
See this page for the details:
http://vim.sf.net/htmldoc/version6.html
Where to get it
---------------
Information about which files to download for what system:
http://vim.sf.net/download.php
If you already know what to get, download it from here:
ftp://ftp.vim.org/pub/vim/unreleased
Or use one of the mirrors, see:
ftp://ftp.vim.org/pub/vim/MIRRORS
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://groups.yahoo.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://groups.yahoo.com/group/vimdev.
Subject specific lists:
Multi-byte issues: vim-multibyte http://groups.yahoo.com/group/vim-multibyte
Macintosh issues: vim-mac http://groups.yahoo.com/group/vim-mac
Reporting bugs
--------------
Send them to <bugs@...>. Please describe the problem precisely. 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 starting
without your own vimrc file: "vim -u NONE -U NONE". Try different machines
if possible. See ":help bugs" in Vim. Send me a patch 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!
--
SIGFUN -- signature too funny (core dumped)
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Announcing: Vim (Vi IMproved) version 6.0
Author: Bram Moolenaar et al.
Announcement
------------
This is a major new version of Vim. Vim 6.0 is a huge step from Vim
5.x. Many, many new features and improvements have been included. For
an overview, with a few screendumps, look here:
http://vim.sf.net/whyvim.php
The alpha and beta testing has taken more than a year. Many problems
have been fixed in the previous weeks, which is also a hint that more
problems will be found in the future. Thus the usual disclaimers apply.
Otherwise, Vim 6.0 has been tested quite a bit, thus it's ready for
daily work.
One problem has already been noticed and fixed: Using the "sh" syntax
may cause error messages. Get patch 6.0.001 to fix that. Or get the
new sh.vim syntax file. You can find the most recent patches here:
ftp://ftp.vim.org/pub/vim/patches/
Upgrading from Vim 5.x to Vim 6.0 should be easy. Vim 6.0 is mostly
backwards compatible. But this is a major new release, the new features
may cause a few problems. If something goes wrong, first check out
":help version6" for known incompatibilities.
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/ME/NT/2000/XP, OS/2, Atari MiNT, BeOS, VMS, RISC OS, Macintosh and
Amiga.
For more information, see http://vim.sf.net. This is also a great place
to find Vim tips and scripts!
New since version 5.8
---------------------
The number of changes is huge. These are just the main new items:
Folding - momentarily hide part of the text
Vertically split windows - mixed with horizontal splits
Diff mode - show and remove differences between files
Easy Vim: click-and-type - for those who really don't like two modes
User manual - learn to use Vim, reads like a book
Flexible indenting - automatic indenting for any language
Extended search patterns - more regexp power than you will need
UTF-8 support - Unicode allows editing nearly all languages
Multi-language support - translated messages and menus
Plugin support - drop a script in a directory and you can use it
Filetype plugins - an easy way to setup for editing a type of file
File browser - browse directories, also on a terminal
Editing files over a network - read and write a remote file directly
command-line editing window - use any Vim command to edit an Ex command
Debugging mode - debug your Vim functions and scripts
Cursor in virtual position - edit tables and draw ASCII pictures
Debugger interface - use Vim with Sun Visual Workshop
Communication between Vims - let one Vim tell another Vim what to do
Printing - print with syntax colors
Quickfix extended - see error messages in a window and jump there
Writing files improved - rename or copy to make a backup file
Argument list - select groups of files to work on
Restore a View - save the looks of a window and restore it later
Color schemes - quickly switch between different color setups
See this page for the details:
http://vim.sf.net/htmldoc/version6.html
Where to get it
---------------
Information about which files to download for what system:
http://vim.sf.net/download.php
If you already know what to get, download it from here:
ftp://ftp.vim.org/pub/vim/
Or use one of the mirrors, see:
ftp://ftp.vim.org/pub/vim/MIRRORS
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://groups.yahoo.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://groups.yahoo.com/group/vimdev.
Subject specific lists:
Multi-byte issues: vim-multibyte http://groups.yahoo.com/group/vim-multibyte
Macintosh issues: vim-mac http://groups.yahoo.com/group/vim-mac
Reporting bugs
--------------
Send them to <bugs@...>. Please describe the problem precisely. 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 starting
without your own vimrc file: "vim -u NONE -U NONE". Try different machines
if possible. See ":help bugs" in Vim. Send me a patch 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!
--
How To Keep A Healthy Level Of Insanity:
1. At lunch time, sit in your parked car with sunglasses on and point
a hair dryer at passing cars. See if they slow down.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
In the first two weeks of October I have visited the Kibaale Childrens
Centre in Uganda. This is Vim's charityware.
Use one of these links:
http://www.vim.org/iccf/news.htmlhttp://iccf-holland.org/news.htmlhttp://www.iccf.nl/news.html
Use the "more pictures" link to get an impression of what I have seen
in Kibaale.
A few notes:
- For people in Germany there is now a way to get a tax reduction if you
donate money towards the project. See this page (in German):
http://www.vim.org/iccf/germany.html
- The amounts for sponsoring a child have been raised. Mainly because
the dollar has become more expensive (thus counted in US dollars the
amounts didn't change much). At the same time we switched to the
Euro (the guilder disappears January 2002). The amounts should now be
enough to cover the actual costs for sponsoring a child. The last
year part of the one-time donations had to be used to fill the gap.
We rather use them for something else, like keeping the clinic
running.
I have a list of 15 children that are waiting to be sponsored. Don't
disappoint them!
--
hundred-and-one symptoms of being an internet addict:
15. Your heart races faster and beats irregularly each time you see a new WWW
site address in print or on TV, even though you've never had heart
problems before.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
[This is only interesting for inhabitants of Germany.]
As you all know, Vim users are asked to help poor children in Uganda.
Donations for the children can now be done through the German
organization MISEROER. MISEROER then sends the money to the project in
Uganda. Using this method allows for getting a tax reduction in
Germany. This can also be used for sponsoring a child.
More information can be found by using one of these links:
http://www.vim.org/iccf/germany.htmlhttp://iccf-holland.org/germany.htmlhttp://www.iccf.nl/germany.html
--
hundred-and-one symptoms of being an internet addict:
162. You go outside and look for a brightness knob to turn down the sun.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
You can find a Vim desktop calendar here:
http://www.moolenaar.net/
On one side there is an easy-to-read 2002 calendar. On the other side
there is brief info on Vim and ICCF Holland.
You can print this on one sheet of paper, fold it and add a bit of glue
to make it stand on your desk.
It is available in Dutch and English, PostScript and PDF, A4 and Letter
paper.
Happy Vimming in 2002!
--
hundred-and-one symptoms of being an internet addict:
256. You are able to write down over 250 symptoms of being an internet
addict, even though they only asked for 101.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
There have been a few remarks on the Vim license. I have attempted to
adjust the license to make more people happy with how Vim can be
distributed. If you care about this, please read the draft below and
let me know if you have a problem with it. If a discussion is
necessary, let's do that in the vim-dev maillist.
The main difference is that the license should now be GPL-compatible
(this is not yet confirmed by the FSF though). This avoids that linking
with a GPL'ed library makes it impossible to distribute Vim. Debian had
a problem with this.
To make this possible I had to add the possibility to distribute Vim
within a small group of people, without the requirement to send the
maintainer a copy of changes, when asked for.
The result is that the Vim license is more "free" than before. If you
have contributed code to Vim and do not agree with this new license,
this is the time to speak up.
==============================================================================
SUMMARY
Vim is Charityware. You can use and copy it as much as you like, but you are
encouraged to make a donation for needy children in Uganda. Please see |kcc|
below or visit the ICCF web site, available at these mirrors:
http://iccf-holland.org/ *iccf* *ICCF*
http://www.vim.org/iccf/http://www.iccf.nl/
The Open Publication License applies to the Vim documentation, see
|manual-copyright|.
LICENSE DETAILS
I) There are no restrictions on distributing unmodified copies of Vim except
that they must include this license text. You can also distribute
unmodified parts of Vim, likewise unrestricted except that they must
include this license text. You are also allowed to include executables
that you made from the unmodified Vim sources, plus your own usage
examples and Vim scripts.
II) It is allowed to distribute a modified version of Vim, with executables
and/or source code, when the following four conditions are met:
1) This license text must be included unmodified.
2) The modified Vim must be distributed in one of the following five ways:
a) If you make changes to Vim, you must clearly describe in the
distribution how to contact you. When the maintainer asks you (in
any way) for a copy of the modified Vim you distributed, you must
make your changes, including source code, available to the
maintainer without fee. The maintainer reserves the right to
include your changes in the official version of Vim. What the
maintainer will do with your changes and under what license they
will be distributed is negotiable. If there has been no
negotiation, then this license also applies to your changes.
The current maintainer is Bram Moolenaar <Bram@...>. If this
changes it will be announced in appropriate places (most likely
vim.sf.net, www.vim.org and/or comp.editors). When it is completely
impossible to contact the maintainer, the obligation to send him
your changes ceases. Once the maintainer has confirmed that he
has received your changes they will not have to be sent again.
b) If you have received a modified Vim that was distributed as
mentioned under a) you are allowed to further distribute it
unmodified, as mentioned at I). If you make additional changes the
text under a) applies to those changes.
c) Provide all the changes, including source code, with every copy of
the modified Vim you distribute. This may be done in the form of a
context diff. You can choose what license to use for new code you
add. The changes and their license must not restrict others from
making their own changes to the official version of Vim.
d) When you have a modified Vim which includes all changes, as
mentioned under c), you can distribute it without the source code
for the changes if the following three conditions are met:
- The license that applies to the changes permits you to distribute
the changes to the Vim maintainer without fee or restriction, and
permits the Vim maintainer to include the changes in the official
version of Vim without fee or restriction.
- You keep the changes for at least three years after last
distributing the corresponding modified Vim. When the maintainer
or someone who you distributed the modified Vim to asks you (in
any way) for the changes within this period, you must make them
available to him.
- You clearly describe in the distribution how to contact you. This
contact information must remain valid for at least three years
after last distributing the corresponding modified Vim, or as long
as possible.
e) When the GNU General Public License (GPL) applies to the changes,
you can distribute the modified Vim under the GNU GPL.
3) A message must be added, at least in the output of the ":version"
command and in the intro screen, such that the user of the modified Vim
is able to see that it was modified. When distributing as mentioned
under 2)e) adding the message is only required for as far as this does
not conflict with the license used for the changes.
4) The contact information as mentioned under 2) must not be removed or
changed, except that the person himself can make corrections.
III) If you distribute a modified version of Vim, you are encouraged to use
the Vim license for your changes and make them available to the
maintainer, including the source code. The preferred way to do this is
by e-mail or by uploading the files to a server and e-mailing the URL.
If the number of changes is small (e.g., a modified Makefile) e-mailing a
context diff will do. The e-mail address to be used is
<maintainer@...>
IV) It is not allowed to remove this license from the distribution of the Vim
sources, parts of it or from a modified version. You may use this
license for previous Vim releases instead of the license that they came
with, at your option.
=== end of license ===
Note:
- If you are happy with Vim, please express that by reading the rest of this
file and consider helping needy children in Uganda.
- If you link Vim with a library that goes under the GNU GPL, this limits
further distribution to the GNU GPL. Also when you didn't actually change
anything in Vim.
==============================================================================
--
SOLDIER: What? A swallow carrying a coconut?
ARTHUR: It could grip it by the husk ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
Financial Report
As you all know, Vim users are asked to help needy children in Uganda.
Most of the donations and sponsorships are handled by the ICCF Holland
foundation. The financial report for 2001 is now available here:
http://iccf-holland.org/2001.htmlhttp://www.vim.org/iccf/2001.htmlhttp://www.iccf.nl/2001.html
I'm glad to see that we have been able to send more money to Uganda than
ever before. This is very much needed, since the project keeps on
growing. Recently the clinic was extended with a laboratory. In
January the school will be extended with two more classes. This means
there are about fifty more children to be sponsored. If you were
thinking of sponsoring, this is a good moment to start!
Amazon
The sales of the Vim book and other items through Amazon was a new
source of income in 2001. Please consider using the links on these
pages if you buy something at Amazon USA, UK, DE or FR. Then ICCF
Holland gets 5% or 15% of the sales and it doesn't cost you anything!
http://iccf-holland.org/click.htmlhttp://www.vim.org/iccf/click.htmlhttp://www.iccf.nl/click.html
--
hundred-and-one symptoms of being an internet addict:
31. You code your homework in HTML and give your instructor the URL.
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///
There have been a few remarks on the updated Vim license. Although only
details have been changed, this could still change the meaning of the
license. Therefore I consider it necessary to again ask all Vim
developers to check out this new version.
The intention of this new license is to make more people happy about how
Vim can be distributed.
The main difference is that the license should now be GPL-compatible
(this is not yet confirmed by the FSF though). This avoids that linking
with a GPL'ed library makes it impossible to distribute Vim. Debian had
a problem with this.
To make this possible I had to add the possibility to distribute Vim
without the requirement to send the maintainer a copy of changes, when
asked for. This distribution should then be done with the source code
being available or under the GNU GPL.
The result is that the Vim license is more "free" than before. If you
have contributed code to Vim and do not agree with this new license,
this is the time to speak up!
If a discussion is necessary, let's do that in the vim-dev maillist.
Replying to the vim-announce maillist won't work.
==============================================================================
SUMMARY
Vim is Charityware. You can use and copy it as much as you like, but you are
encouraged to make a donation for needy children in Uganda. Please see |kcc|
below or visit the ICCF web site, available at these mirrors:
http://iccf-holland.org/ *iccf* *ICCF*
http://www.vim.org/iccf/http://www.iccf.nl/
The Open Publication License applies to the Vim documentation, see
|manual-copyright|.
=== begin of license ===
VIM LICENSE
I) There are no restrictions on distributing unmodified copies of Vim except
that they must include this license text. You can also distribute
unmodified parts of Vim, likewise unrestricted except that they must
include this license text. You are also allowed to include executables
that you made from the unmodified Vim sources, plus your own usage
examples and Vim scripts.
II) It is allowed to distribute a modified version of Vim, including
executables and/or source code, when the following four conditions are
met:
1) This license text must be included unmodified.
2) The modified Vim must be distributed in one of the following five ways:
a) If you make changes to Vim, you must clearly describe in the
distribution how to contact you. When the maintainer asks you (in
any way) for a copy of the modified Vim you distributed, you must
make your changes, including source code, available to the
maintainer without fee. The maintainer reserves the right to
include your changes in the official version of Vim. What the
maintainer will do with your changes and under what license they
will be distributed is negotiable. If there has been no
negotiation, then this license also applies to your changes.
The current maintainer is Bram Moolenaar <Bram@...>. If this
changes it will be announced in appropriate places (most likely
vim.sf.net, www.vim.org and/or comp.editors). When it is completely
impossible to contact the maintainer, the obligation to send him
your changes ceases. Once the maintainer has confirmed that he
has received your changes they will not have to be sent again.
b) If you have received a modified Vim that was distributed as
mentioned under a) you are allowed to further distribute it
unmodified, as mentioned at I). If you make additional changes the
text under a) applies to those changes.
c) Provide all the changes, including source code, with every copy of
the modified Vim you distribute. This may be done in the form of a
context diff. You can choose what license to use for new code you
add. The changes and their license must not restrict others from
making their own changes to the official version of Vim.
d) When you have a modified Vim which includes changes as mentioned
under c), you can distribute it without the source code for the
changes if the following three conditions are met:
- The license that applies to the changes permits you to distribute
the changes to the Vim maintainer without fee or restriction, and
permits the Vim maintainer to include the changes in the official
version of Vim without fee or restriction.
- You keep the changes for at least three years after last
distributing the corresponding modified Vim. When the maintainer
or someone who you distributed the modified Vim to asks you (in
any way) for the changes within this period, you must make them
available to him.
- You clearly describe in the distribution how to contact you. This
contact information must remain valid for at least three years
after last distributing the corresponding modified Vim, or as long
as possible.
e) When the GNU General Public License (GPL) applies to the changes,
you can distribute the modified Vim under the GNU GPL version 2 or
any later version.
3) A message must be added, at least in the output of the ":version"
command and in the intro screen, such that the user of the modified Vim
is able to see that it was modified. When distributing as mentioned
under 2)e) adding the message is only required for as far as this does
not conflict with the license used for the changes.
4) The contact information as mentioned under 2) must not be removed or
changed, except that the person himself can make corrections.
III) If you distribute a modified version of Vim, you are encouraged to use
the Vim license for your changes and make them available to the
maintainer, including the source code. The preferred way to do this is
by e-mail or by uploading the files to a server and e-mailing the URL.
If the number of changes is small (e.g., a modified Makefile) e-mailing a
context diff will do. The e-mail address to be used is
<maintainer@...>
IV) It is not allowed to remove this license from the distribution of the Vim
sources, parts of it or from a modified version. You may use this
license for previous Vim releases instead of the license that they came
with, at your option.
=== end of license ===
Note:
- If you are happy with Vim, please express that by reading the rest of this
file and consider helping needy children in Uganda.
- If you link Vim with a library that goes under the GNU GPL, this limits
further distribution to the GNU GPL. Also when you didn't actually change
anything in Vim.
- Once a change is included that goes under the GNU GPL, this forces all
further changes to also be made under the GNU GPL or a compatible license.
- If you distribute a modified version of Vim, you can include your name and
contact information with the "--with-modified-by" configure argument or the
MODIFIED_BY define.
==============================================================================
--
SOLDIER: What? A swallow carrying a coconut?
ARTHUR: It could grip it by the husk ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@... -- http://www.moolenaar.net \\\
((( Creator of Vim -- http://vim.sf.net -- ftp://ftp.vim.org/pub/vim )))
\\\ Help me helping AIDS orphans in Uganda - http://iccf-holland.org ///