patch 7.0.243 (extra)
Patch 7.0.243 (extra)
Problem:Win32: When GvimExt is built with MSVC 2005 or later, the Edit
with vim context menu doesn't appear in the Windows Explorer.
Solution: Embed the linker manifest file into the resources of GvimExt.dll.
(Mathias Michaelis)
Files: src/GvimExt/Makefile
*** ../vim-7.0.242/src/GvimExt/Makefile Tue Mar 7 00:12:38 2006
--- src/GvimExt/MakefileSat May 5 12:47:27 2007
***
*** 19,24
--- 19,25
# $(implib) /NOLOGO -machine:$(CPU) -def:gvimext.def $** -out:gvimext.lib
# $(link) $(dlllflags) -base:0x1C00 -out:$*.dll $** $(olelibsdll)
shell32.lib gvimext.lib comctl32.lib gvimext.exp
$(link) $(lflags) -dll -def:gvimext.def -base:0x1C00 -out:$*.dll $**
$(olelibsdll) shell32.lib comctl32.lib
+ if exist $*.dll.manifest mt -nologo -manifest $*.dll.manifest
-outputresource:$*.dll;2
gvimext.obj: gvimext.h
***
*** 34,36
--- 35,38
- if exist gvimext.exp del gvimext.exp
- if exist gvimext.obj del gvimext.obj
- if exist gvimext.res del gvimext.res
+ - if exist gvimext.dll.manifest del gvimext.dll.manifest
*** ../vim-7.0.242/src/version.cFri May 4 22:31:31 2007
--- src/version.c Sat May 5 12:54:21 2007
***
*** 668,669
--- 668,671
{ /* Add new patch number below this line */
+ /**/
+ 243,
/**/
--
hundred-and-one symptoms of being an internet addict:
50. The last girl you picked up was only a jpeg.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
Vim version 7.1a BETA has been released
Announcing: Vim (Vi IMproved) version 7.1a BETA This is a BETA release of Vim 7.1. It consists of Vim 7.0 plus all patches and updated runtime files. I expect this to be stable, since the patches have been used by many people already. This BETA is mainly to check that the files has been setup properly. It's been almost a year since the last one! Please report every problem you find! It will only be a few days until the 7.1 release, so please take a little time right now to check it out. Once you have installed Vim 7.1a BETA you can find details about the changes since Vim 7.0 with :help version-7.1. Testing --- This is a BETA test version. Please give it a good test and report anything that isn't right. That includes a crash but also a typo in the documentation. I will not make an Amiga or OS/2 binary for Vim 7.1a. A Mac version is hopefully available soon on http://macvim.org/ Where to get it --- All files can be found below this directory: ftp://ftp.vim.org/pub/vim/unstable/ Information about which files to download for what system (don't use the links, they are still for Vim 7.0): http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1a is also available from CVS (when it works again) and with Aap: http://www.vim.org/develop.php An overview of the files: UNIX: unix/vim-7.1a.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1a-extra.tar.gz extra files extra/vim-7.1a-lang.tar.gz multi-language files doc/vim71ahtml.zip help files converted to HTML MS-WINDOWS: pc/gvim71a.exe self-installing, includes all runtime files pc/vim71art.zip runtime files pc/vim71alang.zip files for translated messages and menus pc/gvim71a.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71aole.zip GUI binary with OLE support pc/gvim71a_s.zipGUI binary for Windows 3.1 (untested) pc/vim71ad16.zip16 bit console version for MS-DOS pc/vim71ad32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71aw32.zipconsole version for Windows NT/2000/XP pc/vim71asrc.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1a.diff.gz sources + runtime files extra/vim-7.0-7.1a-extra.diff.gz extra files extra/vim-7.0-7.1a-lang.diff.gzmulti-language files 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/maillist.php#vim If you want to help Vim development or get the latest patches, subscribe to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev Subject specific lists: Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte Macintosh issues: http://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Send them to [EMAIL PROTECTED]. 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 reproducible 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. 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! -- hundred-and-one symptoms of being an internet addict: 53. To find out what time it is, you send yourself an e-mail and check the Date: field. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Patch: virtcol([123,'$'])
Hi Bram, On 26-Mar-2007 18:25, Bram Moolenaar wrote: Michael Schaap wrote: Here's a patch to make virtcol([123, '$']) do the right thing. If it looks good to you, can you include it? Looks good, I'll include it. Thanks! It appears that this didn't make it into 7.1a. Probably slipped through the cracks? :-) Thanks, - Michael
Re: Favorite little-known feature
On Fri, 04 May 2007 21:37:21 -0500, Tim Chase [EMAIL PROTECTED] wrote: -dark corners of the regexp engine...especially back-references if you've never used them before; and the power of the :s command, along with the \= replacement for expression evaluation. I would say that if there's one single thing everyone should do to become a power user it is to become comfortable with regular expressions. Many tasks that might take hours by hand become no more than a couple of minutes work with Vim, sed or Perl and a suitable regular expression. Many people are deterred by the jumble of punctuation that makes regular expressions look like line noise, but they're well worth learning. The only disadvantage of regular expressions is that once you've learned to use them you tend to look scathingly at anything that doesn't provide them as a core feature. -- Matthew Winn
Re: Vim Logo Use
Taylor Venable wrote: I can't find anything about it on the Vim website, so I was wondering what the status of the Vim logo is. Does someone own the copyright to it? Is it in the public domain? Would it be alright to create, say, a wallpaper with the Vim logo in it and release the wallpaper under a CC-BY-SA license? Thanks for clarification! The Vim logo was made by a few people, at least including Vince Negri and me. It's hard to say who owns the copyright officially, but I can claim to make decisions about it, since I decided to use it. In general you are free to use the Vim logo for promotion of Vim. No need to get written permission. However, if I notice misuse of the Vim logo I might get furious and poke someone with soft cushions. Have at you! I don't think you need a license for a wallpaper, especially since it will be hard to match the license of the Vim logo. -- hundred-and-one symptoms of being an internet addict: 47. You are so familiar with the WWW that you find the search engines useless. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: mail plugin and hexdump file cause endless loop in vim 7
Andrei Voropaev wrote: I've hit one interesting problem. When I've tried to send in an email large hexdump (around 50K) the vim entered endless loop with 100% CPU usage. I could terminate this loop by hitting Ctrl-C, but as soon as I've tried to move to the long line the same thing happened again. Since I could manipulated this file with vim without mail ftplugin, I came to conclusion that the problem has something to do with that plugin. The file in question is located at http://vandal.sdf-eu.org/hexdump.txt To reproduce the problem I did the following steps bash$ vim mutt-vandal-1001-25710-908 :new hexdump.txt 2yy :q p At this point vim freezes and top reports that it uses 100% CPU. Just in case. I use ~/.vim/ftplugin/mail.vim with set fo-=l Can anyone else try and see if the same thing happens? It's the syntax highlighting. Do :syn clear and the problem goes away. There must be some item in the mail syntax highlighting that can't handle long lines. Perhaps you can have a look at $VIMRUNTIME/syntax/mail.vim. Delete some lines to check which one causes trouble. The planned improvements to the regexp code (part of the Google summer of code) should also help. But it will takes several months before we get something. -- hundred-and-one symptoms of being an internet addict: 49. You never have to deal with busy signals when calling your ISP...because you never log off. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Favorite little-known feature
On Fri, May 04, 2007 at 09:20:51PM -0500, Clinton Curry wrote: What is your favorite little-known Vim feature? Selecting a block (Ctrl-V), then pressing I (shift-i) and entering text which then gets inserted into all rows of the block at the same column. This is one of the features I love when editing DNS zone files. Although Ctrl-A for incrementing the serial number of a zone file is a good thing, too. :) Christoph
autocomplete on the command line from words in buffers
Hello All, I did ask this question on comp.editors and didn't get an answer that was satisfactory. I want to develop a plugin just using vim scripts for the verilog language. In the plugin I have functions that require arguments that are words used in the current open buffers. On the command line, I want to autocomplete these words that are arguments to functions. For example: :call function1(last_Tab,first_Tab) In open buffers, the words called last_buffer_value and first_buffer_value are used. So when I hit Tab I want that word to be completed so the result would be :call function1(last_buffer_value,first_buffer_value) Is there a way to do this? Thanks in advance, Dan Fabrizio
errorformat and -version-info
Hello, I have troubles with the default compiler error format matching libtool's -version-info option that appears in make output and takes three colon-separated numbers as its argument, e.g. -version-info 1:2:3 When vim sees this it takes it for an error location and opens a file with a very silly name as the `source file' -- try loading the attached file as errorfile (note that while the splitting of long errorfile lines does not improve the situation, it is not the primary problem). I tried to fix the error format with things like :set errorformat+=%-G%.%#-version-info without any effect. Even just :set errorformat=%-G%.%#-version-info,%f:%l:%m does not ignore lines contaning `-version-info'. I probably misundertood something in the error format syntax. Can anyone help me? TIA, Yeti -- http://gwyddion.net/ errorfile if /bin/bash ../libtool --tag=CC --mode=compile /home/yeti/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -DG_LOG_DOMAIN=\GwyDraw\ -I/home/yeti/opt/gwyddion/include -Wall -W -Wshadow -Wpointer-arith -Wno-sign-compare -Wundef -Werror-implicit-function-declaration -Wno-system-headers -Wno-pointer-sign -Wno-format-zero-length -Wdeclaration-after-statement -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/atk-1.0 -fno-trapping-math -fno-math-errno -fno-strict-aliasing -ggdb -O2 -MT gwypixfield.lo -MD -MP -MF .deps/gwypixfield.Tpo -c -o gwypixfield.lo gwypixfield.c; \ then mv -f .deps/gwypixfield.Tpo .deps/gwypixfield.Plo; else rm -f .deps/gwypixfield.Tpo; exit 1; fi /home/yeti/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -DG_LOG_DOMAIN=\GwyDraw\ -I/home/yeti/opt/gwyddion/include -Wall -W -Wshadow -Wpointer-arith -Wno-sign-compare -Wundef -Werror-implicit-function-declaration -Wno-system-headers -Wno-pointer-sign -Wno-format-zero-length -Wdeclaration-after-statement -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/atk-1.0 -fno-trapping-math -fno-math-errno -fno-strict-aliasing -ggdb -O2 -MT gwypixfield.lo -MD -MP -MF .deps/gwypixfield.Tpo -c gwypixfield.c -fPIC -DPIC -o .libs/gwypixfield.o /bin/bash ../libtool --tag=CC --mode=link /home/yeti/bin/gcc -Wall -W -Wshadow -Wpointer-arith -Wno-sign-compare -Wundef -Werror-implicit-function-declaration -Wno-system-headers -Wno-pointer-sign -Wno-format-zero-length -Wdeclaration-after-statement -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtkglext-1.0 -I/usr/lib/gtkglext-1.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/atk-1.0 -fno-trapping-math -fno-math-errno -fno-strict-aliasing -ggdb -O2 -L/home/yeti/opt/gwyddion/lib -o libgwydraw2.la -rpath /home/yeti/opt/gwyddion/lib -lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lfontconfig -lXext -lXrender -lXinerama -lXi -lXrandr -lXcursor -lXfixes -lpango-1.0 -lcairo -lX11 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lgobject-2.0 -lglib-2.0 -version-info 0:1:0 gwydraw.lo gwyglmaterial.lo gwygradient.lo gwypixfield.lo gwyrgba.lo gwyselection.lo rm -fr .libs/libgwydraw2.la .libs/libgwydraw2.lai .libs/libgwydraw2.so .libs/libgwydraw2.so.0 .libs/libgwydraw2.so.0.0.1 /home/yeti/bin/gcc -shared .libs/gwydraw.o .libs/gwyglmaterial.o .libs/gwygradient.o .libs/gwypixfield.o .libs/gwyrgba.o .libs/gwyselection.o -L/home/yeti/opt/gwyddion/lib /usr/lib/libpangoft2-1.0.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libpangocairo-1.0.so -lfontconfig -lXext -lXrender -lXinerama -lXi -lXrandr -lXcursor -lXfixes /usr/lib/libpango-1.0.so /usr/lib/libcairo.so -lX11 /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libgobject-2.0.so /usr/lib/libglib-2.0.so -Wl,-soname -Wl,libgwydraw2.so.0 -o .libs/libgwydraw2.so.0.0.1 (cd .libs rm -f libgwydraw2.so.0 ln -s libgwydraw2.so.0.0.1 libgwydraw2.so.0) (cd .libs rm -f libgwydraw2.so ln -s libgwydraw2.so.0.0.1 libgwydraw2.so) creating libgwydraw2.la (cd .libs rm -f libgwydraw2.la ln -s ../libgwydraw2.la libgwydraw2.la)
Re: mail plugin and hexdump file cause endless loop in vim 7
On Sat, May 05, 2007 at 12:27:36PM +0200, Bram Moolenaar wrote: It's the syntax highlighting. Do :syn clear and the problem goes away. Ok, thank you. -- Minds, like parachutes, function best when open
Vim version 7.1a BETA has been released
Announcing: Vim (Vi IMproved) version 7.1a BETA This is a BETA release of Vim 7.1. It consists of Vim 7.0 plus all patches and updated runtime files. I expect this to be stable, since the patches have been used by many people already. This BETA is mainly to check that the files has been setup properly. It's been almost a year since the last one! Please report every problem you find! It will only be a few days until the 7.1 release, so please take a little time right now to check it out. Once you have installed Vim 7.1a BETA you can find details about the changes since Vim 7.0 with :help version-7.1. Testing --- This is a BETA test version. Please give it a good test and report anything that isn't right. That includes a crash but also a typo in the documentation. I will not make an Amiga or OS/2 binary for Vim 7.1a. A Mac version is hopefully available soon on http://macvim.org/ Where to get it --- All files can be found below this directory: ftp://ftp.vim.org/pub/vim/unstable/ Information about which files to download for what system (don't use the links, they are still for Vim 7.0): http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1a is also available from CVS (when it works again) and with Aap: http://www.vim.org/develop.php An overview of the files: UNIX: unix/vim-7.1a.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1a-extra.tar.gz extra files extra/vim-7.1a-lang.tar.gz multi-language files doc/vim71ahtml.zip help files converted to HTML MS-WINDOWS: pc/gvim71a.exe self-installing, includes all runtime files pc/vim71art.zip runtime files pc/vim71alang.zip files for translated messages and menus pc/gvim71a.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71aole.zip GUI binary with OLE support pc/gvim71a_s.zipGUI binary for Windows 3.1 (untested) pc/vim71ad16.zip16 bit console version for MS-DOS pc/vim71ad32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71aw32.zipconsole version for Windows NT/2000/XP pc/vim71asrc.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1a.diff.gz sources + runtime files extra/vim-7.0-7.1a-extra.diff.gz extra files extra/vim-7.0-7.1a-lang.diff.gzmulti-language files 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/maillist.php#vim If you want to help Vim development or get the latest patches, subscribe to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev Subject specific lists: Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte Macintosh issues: http://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Send them to [EMAIL PROTECTED]. 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 reproducible 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. 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! -- hundred-and-one symptoms of being an internet addict: 53. To find out what time it is, you send yourself an e-mail and check the Date: field. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Favorite little-known feature
Clinton Curry wrote: Every once in a while, I discover (either through help files or this list) a relatively little-known feature of vim which really enhances my computing experience. The most recent occurrence of this (thanks to A.J.Mechelynck) is the netrw feature (:help netrw) which allows one to edit a file over a network connection in a local copy of vim. Wonderful! What is your favorite little-known Vim feature? I live under the illusion maybe, the impression certainly, that if I know some Vim feature, there must be a far from negligible number of users who know it too. Maybe because, like Socrates, the more I learn and the better I see how ignorant I am. This said, IMHO the single most useful feature of Vim is its help system, because of its exhaustivity (I certainly wouldn't say that it is little-known; but maybe its importance is underestimated); and therefore the most useful commands are those by means of which that help system can be put to better use: :help, helptag completion, and :helpgrep. Best regards, Tony. -- Grandpa Charnock's Law: You never really learn to swear until you learn to drive.
Re: how to get gvim to open a file over ssh?
Am Freitag 04 Mai 2007 schrieb A.J.Mechelynck: IIUC, in this case every transfer requires inputting a username and password -- at least if you cannot configure the server and client yourself, see I never type a password wenn using netrw. See: http://en.wikipedia.org/wiki/Ssh-agent Wikipedia is - of course - only a description. You need to follow the further links for setup informations. Martin -- Martin Krischik mailto://[EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Vim 7 only including the first matched syntax file
I'm having trouble getting Vim to load all syntax file matches.
Specifically, I am attempting to use the mason.vim syntax, which
includes perl.vim, and I have an additional perl.vim installed in
~/.vim/syntax. I've also tested a more general case, without a ~/.vimrc
and an empty ~/.vim directory (save for the test files).
According to the documenation for syn-include, all matching files are
loaded:
When {file-name} is an absolute path (starts with /, c:, $VAR
or sfile) that file is sourced. When it is a relative path
(e.g., syntax/pod.vim) the file is searched for in 'runtimepath'.
All matching files are loaded. Using a relative path is
recommended, because it allows a user to replace the included file
with his own version, without replacing the file that does the :syn
include.
This appears to be true in version 6.3.82, which I have installed on one
system. However, the builds of version 7 I use will only load the
first matching file. I've veriified this with the latest version from
Subversion (revision 254).
Is this a known bug, an unknown bug, or something I'm doing wrongly?
Thanks.
--
Chris Grau
Re: Resp.: Help needed on pt_BR spell checking
2007/4/16, Bram Moolenaar [EMAIL PROTECTED]: Thanks. I updated the Aap script according to your shell script. Thank you! I also changed the .aff files to include the FOL/LOW/UPP lines. That works better when switching languages. I also added the MIDWORD line to make clear a quote can appear halfway a word. I didn't find the time to learn much spellchecking yet. If you say so, I must agree :) I don't understand why you need to remove words that contain a dot. English words with an embedded dot works just fine. Yes, you are right. Please include the . and - too in the midword list. I'd like to have ª, º and ° included when they are trailing characters, too. BTW, there is a problem with µ. If you start a sentence with µg, it will be highlighted as miscapitalized and Vim will suggest Mg instead. I can't do much with the .pdf file that replaces the README file. Please ask the maintainers to provide a plain text file with the Copyright notice. It should be fixed in a short time. Please verify the .spl files I produced are the same (or better :-) than yours. The spelldump output is the same. The newest pt_BR dictionary is: BR_DIR = http://www.deso-se.com.br/downloads/download.php?arquivo=pt_BR-2007-04-11 BR_FNAME = pt_BR-2007-04-11.zip There should be a new release soon. Thanks for maintaining the AAP receipe -- and Vim itself! Leonardo Fontenelle http://leonardof.org (l10n · free software · Brazil)
After recovering a file, filename.swp is left behind.
Is this a deliberate decision by the developers? If so what is the reason, as I don't need itafter recovery? Thanks, Brian
Re: After recovering a file, filename.swp is left behind.
Brian Gupta wrote: Is this a deliberate decision by the developers? If so what is the reason, as I don't need itafter recovery? Thanks, Brian See the last two paragraphs below :help :recover: quote Be sure that the recovery was successful before overwriting the original file or deleting the swap file. It is good practice to write the recovered file elsewhere and run 'diff' to find out if the changes you want are in the recovered file. Once you are sure the recovery is ok delete the swap file. Otherwise, you will continue to get warning messages that the .swp file already exists. /quote Best regards, Tony. -- Earn cash in your spare time -- blackmail your friends
