RE: problem with win32 vim 7.1a.001
> > Any ideas? > > Maybe you can rename all your directories named Vim70 to Vim71a. Yep - that was it. C:\Vim\vim70 was renamed to C:\Vim\vim71a and all is well. Thanks! (and also thanks to Tony for the troubleshooting hints)
Re: Vim version 7.1a BETA has been released
On 2007-05-06, Gary Johnson <[EMAIL PROTECTED]> wrote: > On 2007-05-05, "A.J.Mechelynck" <[EMAIL PROTECTED]> wrote: > > Compiles as a breeze :-). > > Yes indeed. I've compiled it so far on SunOS 5.8 and HP-UX 10.20. > I may try Cygwin if I'm feeling adventurous enough. I've never done > that except from Cygwin sources. Well, that was really easy. I built just the console version for Cygwin and it seems to work fine in PuTTY over an ssh connection. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
Re: problem with win32 vim 7.1a.001
Michael Wookey wrote: Hello vim list, I've just synced up to 7.1a.001 (svn #263) and built on Win32 (MSVC). Everything builds fine and I replace my previous gvim.exe and vim.exe with the newly built versions. I also sync my runtime from ftp.nluug.nl. My vim installation is in: C:\Vim\vim70 My config is in: C:\Vim\_vimrc Additional plugins are in: C:\Vim\vimfiles\... This has always worked fine as this is the structure set up by the vim win32 installer. I now find that launching gvim/vim doesn't find my _vimrc or my vimfiles runtime. I can get it to load my _vimrc by moving it to: C:\Vim\Vim70\_vimrc However my runtime isn't picked up as :scriptnames doesn't list any plugins loaded. Is it just me or has something broken win32 vim? My previous sync was svn#254 (Vim 7.0.236) with a runtime sync from the same time and everything was fine. Any ideas? Make sure that VIMRUNTIME is _not_ defined in your environment (in XP or later: Control Panel => System => Adevanced => Environment variables; there are two sets, one for "all users" and one specific to your login name). VIM may be either undefined or set at C:\Vim; NOT at C:\Vim\Vim70 unless your distribution is in C:\Vim\Vim70\Vim70 (7.0) and/or C:\Vim\vim70\Vim71a (7.1), both of which are quite "atypical" to say the least. Your (user) _vimrc can be either in $HOME (wherever Vim sets it) or, on a single-user system only, in $VIM. The problem with the latter is that it's the same for all users (all login names). At Vim startup, if VIM and VIMRUNTIME are both undefined, and (g)vim was loaded from C:\Vim\vim71a\, that directory will become $VIMRUNTIME and its parent will become $VIM. Vim will then look for runtime files there and in its subfolders. Warnings: 1. I don't think you can use the same server to rsync your 7.1 runtimes as your 7.0: it would pick the 7.0 files, including help files with 'For Vim 7.0" in their first line. AFAICT, the 7.1 runtimes consist of those distributed for 7.1a.000 plus one modification in the latest patch. Couldn't find anything else at ftp.vim.org. 2. The parent of the src/ and runtime/ (and a few other) directories from yource source 7.1 distro should be named vim71a (which is where the archives unpack to) to avoid conflict with the 7.0 source. The first 7.0 compile MUST be from scratch, then you may compile only the changes but only if your featureset stays the same (e.g. big, +gui +ole +perl/dyn +python/dyn -ruby -tcl -mzscheme +multibyte_ime/dyn etc...). To force a full rebuild, use "make -f clean" or "make -f distclean" prior to rebuilding. 3. For more details, see http://users.skynet.be/antoine.mechelynck/vim/compile.htm but replace "vim70" (wherever it appears) by "vim71a". Best regards, Tony. -- If you think education is expensive, try ignorance. -- Derek Bok, president of Harvard
Re: Vim version 7.1a BETA has been released
On 2007-05-06, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > Gary Johnson wrote: > > > I noticed that filetype.vim does not include the patch that I > > submitted to this list 2006-07-25 to fix the recognition of mutt > > temporary files on SunOS. Is there something else I can do to have > > this patch accepted? > > It was still in the todo list. There are many items I still didn't have > time for, unfortunately. I assume you have properly tested this change. > I'll include this one now. Thank you. I was concerned that it hadn't made it onto the list. I didn't realize you had such a backlog of changes. I've been using it in my $VIMRUNTIME/filetype.vim since July without any problems or errors that I know of. Best regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
problem with win32 vim 7.1a.001
Hello vim list, I've just synced up to 7.1a.001 (svn #263) and built on Win32 (MSVC). Everything builds fine and I replace my previous gvim.exe and vim.exe with the newly built versions. I also sync my runtime from ftp.nluug.nl. My vim installation is in: C:\Vim\vim70 My config is in: C:\Vim\_vimrc Additional plugins are in: C:\Vim\vimfiles\... This has always worked fine as this is the structure set up by the vim win32 installer. I now find that launching gvim/vim doesn't find my _vimrc or my vimfiles runtime. I can get it to load my _vimrc by moving it to: C:\Vim\Vim70\_vimrc However my runtime isn't picked up as :scriptnames doesn't list any plugins loaded. Is it just me or has something broken win32 vim? My previous sync was svn#254 (Vim 7.0.236) with a runtime sync from the same time and everything was fine. Any ideas?
[PATCH] minor doc patch
Hi Bram, Find attached a patch that properly brackets the use of "Enter" in the docs. cheers vimdoc-enter-brackets.patch Description: vimdoc-enter-brackets.patch
Re: Vim version 7.1a BETA -- svn ?
On 5/6/07, Yakov Lerner <[EMAIL PROTECTED]> wrote: On 5/6/07, Martin Krischik <[EMAIL PROTECTED]> wrote: > Am Sonntag 06 Mai 2007 schrieb Yakov Lerner: > > > On 2007-05-05, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > Announcing: Vim (Vi IMproved) version 7.1a BETA > > > > I tried to build vim7.1 from svn. But all I get from usual > > svn location (https://svn.sourceforge.net/svnroot/vim/vim7), is > > vim 7.0.236. Will vim7.1 be served at this localtion eventually ? > > That is probalby because the svn server is a mess. I have to disagree. The svn maintainer does valuable service to the community. The svn service is really stable, unlike the cvs server. I'd like to really thank the svn updater for keeping the svn updated. The reason why updates did not make it to svn was that cvs server was down, as Bram explained above. I don't think so. I guess the reason why updates did not make it to svn was that the svn committer was out for holiday. Because the svn committing work has nothing to do with the cvs service. It only depends on the ftp service: the committer checks out the patches from the ftp, not from cvs. Yakov
Re: Vim version 7.1a BETA -- svn ?
On 5/7/07, A.J.Mechelynck <[EMAIL PROTECTED]> wrote: François Pinard wrote: > [Martin Krischik] >>> [Martin Krischik] > >>> > That is probalby because the svn server is a mess. > [probably] > >> Only the vim svn archive has no space for tags, braches or releases. > [branches] > > It is not a mess, merely being different. If there is ever a _real_ > need for another organisation of the Subversion repository for Vim, we > can be fairly confident that it will be addressed. > > But now, the Subversion repository mirrors a non-Subversion one, this is > for users convenience, and that's very nice already. Bram currently > does not use Subversion for Vim development, so there is no point > pretending that he does. If Bram was using Subversion, he might feel > like changing things. But even then, the needs would mainly be Bram's! > >> But you can do valuable service and still do it wrong [...] > > Once again, being different does not imply being wrong. We should not > be overly dogmatic in such matters. If the download recipes are clear > and work as expected, the repository fills its role. > Anyway, if the code mirrored on that svn server belongs only to the 7.0 (release) code tree, there are no branches, since every patchlevel comes linearly on top on the one before, and there is one set of files applicable to all platforms and featuresets. _If_ there comes a 7.0.244, _and_ it branches out from 7.0.243 away from 7.1a.000 and 7.1a.001, _and_ both 7.0 and 7.1a are further mirrored on svn, _then_ there will maybe be a reason to define a branch point. But not before. Bram won't make such branches. He always commit patches linearly. If he one day can finally realize that how valuable the branches are, we'll create the tags and branches directories in the svn directory right away. It only costs a few commands. :-) Best regards, Tony. -- Speer's 1st Law of Proofreading: The visibility of an error is inversely proportional to the number of times you have looked at it.
Re: Vim version 7.1a BETA -- svn ?
On 5/7/07, François Pinard <[EMAIL PROTECTED]> wrote: [Martin Krischik] >> [Martin Krischik] >> > That is probalby because the svn server is a mess. [probably] >Only the vim svn archive has no space for tags, braches or releases. [branches] It is not a mess, merely being different. If there is ever a _real_ need for another organisation of the Subversion repository for Vim, we can be fairly confident that it will be addressed. But now, the Subversion repository mirrors a non-Subversion one, this is for users convenience, and that's very nice already. Bram currently does not use Subversion for Vim development, so there is no point pretending that he does. If Bram was using Subversion, he might feel like changing things. But even then, the needs would mainly be Bram's! Well, currently the svn repository has no "tags", "branches" and "trunk", unlike most of the other svn repositories. But that's not because it's a mirror of a non-svn repository - cvs can also uses tags and branches. The main reason is, Bram doesn't use cvs for development, either. He maintains another repository internally. So both cvs and svn are doing the same thing as an ftp server. >But you can do valuable service and still do it wrong [...] Once again, being different does not imply being wrong. We should not be overly dogmatic in such matters. If the download recipes are clear and work as expected, the repository fills its role. Yes. If once needed, we can create the needed "trunk", "branches", "tags" directories very simply with just a few commands. So just don't panic. -- François Pinard http://pinard.progiciels-bpi.ca
Re: patch 7.1a.001
Sent this direct to Bram by accident instead of to the dev list... Hey All, > Patch 7.1a.001 I managed to compile 7.1a from cvs yesterday. I went and did a cvs up to grab this patch and I am now getting this error: gui_w32.c:236: error: redefinition of `struct tagNMTTDISPINFOA' gui_w32.c:246: error: redefinition of `struct tagNMTTDISPINFOW' mingw32-make: *** [gobj/gui_w32.o] Error 1 I'm guessing it's not a result of this patch, since this patch did not affect gui_w32.c. Perhaps there was something changed in CVS (I notice the update grabbed a whole bunch of files)? Chris -- Chris Sutcliffe http://ir0nh34d.googlepages.com http://ir0nh34d.blogspot.com http://emergedesktop.org
Re: Vim version 7.1a BETA -- svn ?
François Pinard wrote: [Martin Krischik] [Martin Krischik] > That is probalby because the svn server is a mess. [probably] Only the vim svn archive has no space for tags, braches or releases. [branches] It is not a mess, merely being different. If there is ever a _real_ need for another organisation of the Subversion repository for Vim, we can be fairly confident that it will be addressed. But now, the Subversion repository mirrors a non-Subversion one, this is for users convenience, and that's very nice already. Bram currently does not use Subversion for Vim development, so there is no point pretending that he does. If Bram was using Subversion, he might feel like changing things. But even then, the needs would mainly be Bram's! But you can do valuable service and still do it wrong [...] Once again, being different does not imply being wrong. We should not be overly dogmatic in such matters. If the download recipes are clear and work as expected, the repository fills its role. Anyway, if the code mirrored on that svn server belongs only to the 7.0 (release) code tree, there are no branches, since every patchlevel comes linearly on top on the one before, and there is one set of files applicable to all platforms and featuresets. _If_ there comes a 7.0.244, _and_ it branches out from 7.0.243 away from 7.1a.000 and 7.1a.001, _and_ both 7.0 and 7.1a are further mirrored on svn, _then_ there will maybe be a reason to define a branch point. But not before. Best regards, Tony. -- Speer's 1st Law of Proofreading: The visibility of an error is inversely proportional to the number of times you have looked at it.
Where to find 7.1a patchlevels & runtimes? (Was: patch 7.1a.001)
Bram Moolenaar wrote: Patch 7.1a.001 Problem:Crash when downloading a spell file. (Szabolcs Horvat) Solution: Avoid that did_set_spelllang() is used recursively when a new window is opened for the download. Also avoid wiping out the wrong buffer. Files: runtime/autoload/spellfile.vim, src/buffer.c, src/ex_cmds.c, src/spell.c [...] After a little hunting, I found this patch on the ftp server too (with README, MD5 and MD5SUMS): ftp://ftp.vim.org/pub/vim/unstable/patches/7.1a/ Note: I prefer not to feed the email itself to the patch program, because: - my ISP's routers sometimes autoconvert the contents between 8-bit and quoted-printable; and the latter make the patch program choke; - if I see several patches published while I was away or asleep, by FTP I can get them all to where "patch" will find them. - the patch directory on FTP includes a table of contents, README I notice this patch modifies one runtime file. This reminds me that runtime updates are not always reflected in patches. Do the files in ftp://ftp.vim.org/pub/vim/runtime/ (and the equivalent rsync repository, ftp.nluug.nl::Vim/runtime/ ) apply to 7.0 only, or to both 7.0 and 7.1? (The latest changes there are for a large number of spelling dictionaries.) On thinking back, I would suspect they /aren't/ the same, since the first line of each helpfile mentions either 7.0 or 7.1a -- so at least the contents of the doc/ subfolders are different. So -- will runtime upgrades for 7.1 beta be always reflected in patches, or else will there be a runtime server -- and where? (ftp://pub/vim/unstable/runtime/ contains only one item yet: a softlink to the main "spell" subfolder.) Hm... I see a "snapshot zip", http://ftp.vim.org/pub/vim/unstable/snapshot/vim-7.1a.zip ,but it's more than 24h older than the patch, while it's only about 2h "younger" than the 7.0.000 tar.gz and tar.bz2 archives so I guess it's 7.1a.000 in one big economy package... Best regards, Tony. -- If you don't have a nasty obituary you probably didn't matter. -- Freeman Dyson
patch 7.1a.001
Patch 7.1a.001
Problem:Crash when downloading a spell file. (Szabolcs Horvat)
Solution: Avoid that did_set_spelllang() is used recursively when a new
window is opened for the download.
Also avoid wiping out the wrong buffer.
Files: runtime/autoload/spellfile.vim, src/buffer.c, src/ex_cmds.c,
src/spell.c
*** ../vim-7.1a.000/runtime/autoload/spellfile.vim Tue Aug 29 22:31:34 2006
--- runtime/autoload/spellfile.vim Sun May 6 23:52:05 2007
***
*** 1,6
" Vim script to download a missing spell file
" Maintainer: Bram Moolenaar <[EMAIL PROTECTED]>
! " Last Change:2006 Aug 29
if !exists('g:spellfile_URL')
let g:spellfile_URL = 'ftp://ftp.vim.org/pub/vim/runtime/spell'
--- 1,6
" Vim script to download a missing spell file
" Maintainer: Bram Moolenaar <[EMAIL PROTECTED]>
! " Last Change:2007 May 06
if !exists('g:spellfile_URL')
let g:spellfile_URL = 'ftp://ftp.vim.org/pub/vim/runtime/spell'
***
*** 58,76
let fname = a:lang . '.' . enc . '.spl'
" Split the window, read the file into a new buffer.
new
setlocal bin
echo 'Downloading ' . fname . '...'
call spellfile#Nread(fname)
if getline(2) !~ 'VIMspell'
" Didn't work, perhaps there is an ASCII one.
! g/^/d
let fname = a:lang . '.ascii.spl'
echo 'Could not find it, trying ' . fname . '...'
call spellfile#Nread(fname)
if getline(2) !~ 'VIMspell'
echo 'Sorry, downloading failed'
! bwipe!
return
endif
endif
--- 58,97
let fname = a:lang . '.' . enc . '.spl'
" Split the window, read the file into a new buffer.
+ " Remember the buffer number, we check it below.
new
+ let newbufnr = winbufnr(0)
setlocal bin
echo 'Downloading ' . fname . '...'
call spellfile#Nread(fname)
if getline(2) !~ 'VIMspell'
" Didn't work, perhaps there is an ASCII one.
! " Careful: Nread() may have opened a new window for the error message,
! " we need to go back to our own buffer and window.
! if newbufnr != winbufnr(0)
! let winnr = bufwinnr(newbufnr)
! if winnr == -1
! " Our buffer has vanished!? Open a new window.
! echomsg "download buffer disappeared, opening a new one"
! new
! setlocal bin
! else
! exe winnr . "wincmd w"
! endif
! endif
! if newbufnr == winbufnr(0)
! " We are back the old buffer, remove any (half-finished) download.
! g/^/d
! else
! let newbufnr = winbufnr(0)
! endif
!
let fname = a:lang . '.ascii.spl'
echo 'Could not find it, trying ' . fname . '...'
call spellfile#Nread(fname)
if getline(2) !~ 'VIMspell'
echo 'Sorry, downloading failed'
! exe newbufnr . "bwipe!"
return
endif
endif
***
*** 96,112
let fname = substitute(fname, '\.spl$', '.sug', '')
echo 'Downloading ' . fname . '...'
call spellfile#Nread(fname)
! if getline(2) !~ 'VIMsug'
! echo 'Sorry, downloading failed'
! else
1d
exe "write " . escape(dirlist[dirchoice], ' ') . '/' . fname
endif
- set nomod
endif
endif
! bwipe
endif
endfunc
--- 117,145
let fname = substitute(fname, '\.spl$', '.sug', '')
echo 'Downloading ' . fname . '...'
call spellfile#Nread(fname)
! if getline(2) =~ 'VIMsug'
1d
exe "write " . escape(dirlist[dirchoice], ' ') . '/' . fname
+ set nomod
+ else
+ echo 'Sorry, downloading failed'
+ " Go back to our own buffer/window, Nread() may have taken us to
+ " another window.
+ if newbufnr != winbufnr(0)
+ let winnr = bufwinnr(newbufnr)
+ if winnr != -1
+ exe winnr . "wincmd w"
+ endif
+ endif
+ if newbufnr == winbufnr(0)
+ set nomod
+ endif
endif
endif
endif
! " Wipe out the buffer we used.
! exe newbufnr . "bwipe"
endif
endfunc
*** ../vim-7.1a.000/src/buffer.cThu Mar 15 22:53:25 2007
--- src/buffer.cSun May 6 15:44:08 2007
***
*** 1426,1431
--- 1426,1438
if (curbuf->b_kmap_state & KEYMAP_INIT)
keymap_init();
#endif
+ #ifdef FEAT_SPELL
+ /* May need to set the spell language. Can only do this after the buffer
+ * has been properly setup. */
+ if (!curbuf->b_help && curwin->w_p_spell && *curbuf->b_p_spl != NUL)
+ did_set_spelllang(curbuf);
+ #endif
+
redraw_later(NOT_VALID);
}
***
*** 2414,2424
/* Set 'foldlevel' to 'foldlevelstart' if it's not negative. */
if (p_fdls >= 0)
curwin->w_p_fdl = p_fdls;
- #endif
-
- #ifdef FEAT_
Re: Vim version 7.1a BETA -- svn ?
[Martin Krischik] [Martin Krischik] > That is probalby because the svn server is a mess. [probably] Only the vim svn archive has no space for tags, braches or releases. [branches] It is not a mess, merely being different. If there is ever a _real_ need for another organisation of the Subversion repository for Vim, we can be fairly confident that it will be addressed. But now, the Subversion repository mirrors a non-Subversion one, this is for users convenience, and that's very nice already. Bram currently does not use Subversion for Vim development, so there is no point pretending that he does. If Bram was using Subversion, he might feel like changing things. But even then, the needs would mainly be Bram's! But you can do valuable service and still do it wrong [...] Once again, being different does not imply being wrong. We should not be overly dogmatic in such matters. If the download recipes are clear and work as expected, the repository fills its role. -- François Pinard http://pinard.progiciels-bpi.ca
Re: Vim version 7.1a BETA -- svn ?
Am Sonntag 06 Mai 2007 schrieb Yakov Lerner: > On 5/6/07, Martin Krischik <[EMAIL PROTECTED]> wrote: > > Am Sonntag 06 Mai 2007 schrieb Yakov Lerner: > > > On 2007-05-05, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > > Announcing: Vim (Vi IMproved) version 7.1a BETA > > > > > > I tried to build vim7.1 from svn. But all I get from usual > > > svn location (https://svn.sourceforge.net/svnroot/vim/vim7), is > > > vim 7.0.236. Will vim7.1 be served at this localtion eventually ? > > > > That is probalby because the svn server is a mess. > > I have to disagree. The svn maintainer does valuable service > to the community. The svn service is really stable, unlike the cvs server. > I'd like to really thank the svn updater for keeping the svn updated. Of course the svn maintainer do valuable service. But you can do valuable service and still do it wrong (in which case you can de more with less effort). Compare the following svn archives - most of which I picked from the Sourforge homepage (top ten, most active etc. pp): http://open-image.svn.sourceforge.net/viewvc/open-image/ http://gnuada.svn.sourceforge.net/viewvc/gnuada/ http://uiq3.svn.sourceforge.net/viewvc/uiq3/ http://adempiere.svn.sourceforge.net/viewvc/adempiere/ http://phpmyadmin.svn.sourceforge.net/viewvc/phpmyadmin/ http://pidgin.svn.sourceforge.net/viewvc/pidgin/ http://zk1.svn.sourceforge.net/viewvc/zk1/ http://vim.svn.sourceforge.net/viewvc/vim/ All but two have at least /trunk /branch /tag - some more. One is more simplistic and has got only /trunk /releases. Only the vim svn archive has no space for tags, braches or releases. Martin -- Martin Krischik mailto://[EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Re: VimWiki - again - but with a brand new option
Hi all Independent of the implementation used, I suggest to develop good guidelines. The Wiki should be really valuable and not redundant to vim-tips or mailing-lists. I think it's also important to have some people feeling responsible for it so if someone doesn't follow the rules, they will tidy it up quickly. my 2 cents, Sebastian. PS: I would clearly prefer wikia.org over sf.net (I would not build up upon any beta ...)
Re: VimWiki - again - but with a brand new option
Actually, when we first started talking about all of this, I tried to register a vim wiki site on WIkia (http://www.wikia.com). I didn't get any response for a while, but about a week ago, they finally let me know that we could in fact have our own wiki on that site. Here's the address: * http://www.wikia.com/wiki/Vim It has a lot of the advantages that you get with a Sourceforge wiki as far as I can tell, and they have some real cutting-edge spam-fighting modules. So yes, Sourceforge is a better option than it used to be, but my understanding was that some people on the list were unhappy with Soureforge's availability. I'm not saying that Wikia will be better in that respect, but at least it's not Sourceforge. What do you guys think? On Sunday 06 May 2007 08:32, Martin Krischik wrote: > Hello Vim Developers, > Hello Vim Users, > > some time ago there was a huge discussion about a Vim-Wiki. In the end > WikiBooks has the highest support. Still some whished for a Vim-only-Wiki > instead of beeing part of a larger project. > > For this a new option is not open: SourceForge ended the beta for there > wiki support. We can now have a Vim-only-Wiki with just one mouse click. In > fact we could have several because there are several Vim projects on > SourceForge. > > It would be just for us, has a propper user maintainance, (desaster) backup > by SourceForge themself and it can be personalised by CSS. > > All it takes to start is a project admin to activate the wiki. > > Martin > > [1] http://en.wikibooks.org/wiki/Learning_the_vi_editor/Vim
Re: Vim version 7.1a BETA -- svn ?
On 5/6/07, Martin Krischik <[EMAIL PROTECTED]> wrote: Am Sonntag 06 Mai 2007 schrieb Yakov Lerner: > On 2007-05-05, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Announcing: Vim (Vi IMproved) version 7.1a BETA > > I tried to build vim7.1 from svn. But all I get from usual > svn location (https://svn.sourceforge.net/svnroot/vim/vim7), is > vim 7.0.236. Will vim7.1 be served at this localtion eventually ? That is probalby because the svn server is a mess. I have to disagree. The svn maintainer does valuable service to the community. The svn service is really stable, unlike the cvs server. I'd like to really thank the svn updater for keeping the svn updated. The reason why updates did not make it to svn was that cvs server was down, as Bram explained above. Yakov
VimWiki - again - but with a brand new option
Hello Vim Developers, Hello Vim Users, some time ago there was a huge discussion about a Vim-Wiki. In the end WikiBooks has the highest support. Still some whished for a Vim-only-Wiki instead of beeing part of a larger project. For this a new option is not open: SourceForge ended the beta for there wiki support. We can now have a Vim-only-Wiki with just one mouse click. In fact we could have several because there are several Vim projects on SourceForge. It would be just for us, has a propper user maintainance, (desaster) backup by SourceForge themself and it can be personalised by CSS. All it takes to start is a project admin to activate the wiki. Martin [1] http://en.wikibooks.org/wiki/Learning_the_vi_editor/Vim -- Martin Krischik mailto://[EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Re: Vim version 7.1a BETA -- svn ?
Am Sonntag 06 Mai 2007 schrieb Yakov Lerner: > On 2007-05-05, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Announcing: Vim (Vi IMproved) version 7.1a BETA > > I tried to build vim7.1 from svn. But all I get from usual > svn location (https://svn.sourceforge.net/svnroot/vim/vim7), is > vim 7.0.236. Will vim7.1 be served at this localtion eventually ? That is probalby because the svn server is a mess. The maintainser forgot to greate the /trunk /branch /tag directories. You can choose different names. You can add additional directories (I often have a /pmwiki directory as well) but in order to work propperly with Subversion you need the idea behind. Now, good news is: Subversion superior maintaince tools allows to fix the mess (something almost impossible with cvs) and would even volonteer to help out here. Martin -- Martin Krischik mailto://[EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part.
Re: Patch: virtcol([123,'$'])
On 6-May-2007 14:11, Bram Moolenaar wrote: Michael Schaap wrote: 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? :-) It's in the todo list. I simply don't enough have time to work away all todo items. Otherwise the release would have to wait another year... No problem. :-) Thanks for the heads-up, - Michael
Re: Vim version 7.1a BETA has been released
Michael Henry wrote:
Gary Johnson wrote:
On 2007-05-05, "A.J.Mechelynck" <[EMAIL PROTECTED]> wrote:
(Warning: In the "ln" command as used here, the target name comes
before the link name. I find this counter-intuitive.)
It's not just me then. I have to think carefully about that every
time I use ln.
I used to find this hard to remember until I realized that 'ln' and 'cp'
are very similar. The 'cp' command copies one or more sources to a
destination; the 'ln' command links one or more sources to a destination
as well. I tend to think of 'ln -s' as "copy using symlinks". The
order and meaning of the arguments is the same between the commands,
which I now find consistent and intuitive.
Michael Henry
The problem is, "cp -v file1 file2" outputs
`file1' -> `file2'
("the data has been copied from file1 to file2") but "ln -sv file1 file2"
outputs
file2 -> file1
("file2 is now a link pointing to file1"). I still have to call up the help or
the manual every time I invoke it.
Best regards,
Tony.
--
Celebrate Hannibal Day this year. Take an elephant to lunch.
Re: Vim version 7.1a BETA has been released
Gary Johnson wrote: On 2007-05-05, "A.J.Mechelynck" <[EMAIL PROTECTED]> wrote: (Warning: In the "ln" command as used here, the target name comes before the link name. I find this counter-intuitive.) It's not just me then. I have to think carefully about that every time I use ln. I used to find this hard to remember until I realized that 'ln' and 'cp' are very similar. The 'cp' command copies one or more sources to a destination; the 'ln' command links one or more sources to a destination as well. I tend to think of 'ln -s' as "copy using symlinks". The order and meaning of the arguments is the same between the commands, which I now find consistent and intuitive. Michael Henry
Re: Patch: virtcol([123,'$'])
Michael Schaap wrote: > 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? :-) It's in the todo list. I simply don't enough have time to work away all todo items. Otherwise the release would have to wait another year... -- hundred-and-one symptoms of being an internet addict: 63. You start using smileys in your snail mail. /// 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: Vim version 7.1a BETA -- svn ?
Yakov Lerner wrote: > On 2007-05-05, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Announcing: Vim (Vi IMproved) version 7.1a BETA > > I tried to build vim7.1 from svn. But all I get from usual > svn location (https://svn.sourceforge.net/svnroot/vim/vim7), is > vim 7.0.236. Will vim7.1 be served at this localtion eventually ? I had some trouble with the CVS server yesterday. Still working on it. The SVN server always lags behind a bit. I don't update it myself (one less thing to worry about). -- Time is money. Especially if you make clocks. /// 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: Vim version 7.1a BETA has been released
Gary Johnson wrote: > I noticed that filetype.vim does not include the patch that I > submitted to this list 2006-07-25 to fix the recognition of mutt > temporary files on SunOS. Is there something else I can do to have > this patch accepted? It was still in the todo list. There are many items I still didn't have time for, unfortunately. I assume you have properly tested this change. I'll include this one now. -- Q: Should I clean my house or work on Vim? A: Whatever contains more bugs. /// 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: Vim version 7.1a BETA -- svn ?
Yakov Lerner wrote: On 2007-05-05, Bram Moolenaar <[EMAIL PROTECTED]> wrote: Announcing: Vim (Vi IMproved) version 7.1a BETA I tried to build vim7.1 from svn. But all I get from usual svn location (https://svn.sourceforge.net/svnroot/vim/vim7), is vim 7.0.236. Will vim7.1 be served at this localtion eventually ? Thanks Yakov Well, it should first have time to cycle (isn't 7.0 at patchlevel 243 or thereabouts?); and then maybe it's waiting for 7.1a.001? In the meantime you can get the archives from the ftp server, no patches have been issued against 7.1a yet. Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 216. Your pet rock leaves home.
Vim version 7.1a BETA -- svn ?
On 2007-05-05, Bram Moolenaar <[EMAIL PROTECTED]> wrote: Announcing: Vim (Vi IMproved) version 7.1a BETA I tried to build vim7.1 from svn. But all I get from usual svn location (https://svn.sourceforge.net/svnroot/vim/vim7), is vim 7.0.236. Will vim7.1 be served at this localtion eventually ? Thanks Yakov
Re: Vim version 7.1a BETA has been released
On 2007-05-05, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > 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. I noticed that filetype.vim does not include the patch that I submitted to this list 2006-07-25 to fix the recognition of mutt temporary files on SunOS. Is there something else I can do to have this patch accepted? Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
Re: Vim version 7.1a BETA has been released
Gary Johnson wrote: On 2007-05-05, "A.J.Mechelynck" <[EMAIL PROTECTED]> wrote: Bram Moolenaar wrote: 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". [...] Compiles as a breeze :-). Yes indeed. I've compiled it so far on SunOS 5.8 and HP-UX 10.20. I may try Cygwin if I'm feeling adventurous enough. I've never done that except from Cygwin sources. The binary is now in /usr/local/vim (but we still have /usr/local/vim70 as a backup); the runtime files go in /usr/local/vim/vim71a and below, where the binary will find them with no problem (and the 7.0 runtime files in /usr/local/vim/vim70 [or wherever] aren't touched). I think some directories were omitted from the paths in that paragraph and that it should read: The binary is now in /usr/local/bin/vim (but we still have /usr/local/bin/vim70 as a backup); the runtime files go in /usr/local/share/vim/vim71a and below, where the binary will find them with no problem (and the 7.0 runtime files in /usr/local/share/vim/vim70 [or wherever] aren't touched). er, yes. I should have reread it once more. (Warning: In the "ln" command as used here, the target name comes before the link name. I find this counter-intuitive.) It's not just me then. I have to think carefully about that every time I use ln. Regards, Gary Yes. When linking to the same name in a different directory, I find it easier to omit the link name altogether, as shown for matchit.txt Best regards, Tony. -- "He was a modest, good-humored boy. It was Oxford that made him insufferable."
Re: Vim version 7.1a BETA has been released
On 2007-05-05, "A.J.Mechelynck" <[EMAIL PROTECTED]> wrote: > Bram Moolenaar wrote: > > 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". > [...] > > Compiles as a breeze :-). Yes indeed. I've compiled it so far on SunOS 5.8 and HP-UX 10.20. I may try Cygwin if I'm feeling adventurous enough. I've never done that except from Cygwin sources. > The binary is now in /usr/local/vim (but we still have /usr/local/vim70 as a > backup); the runtime files go in /usr/local/vim/vim71a and below, where the > binary will find them with no problem (and the 7.0 runtime files in > /usr/local/vim/vim70 [or wherever] aren't touched). I think some directories were omitted from the paths in that paragraph and that it should read: The binary is now in /usr/local/bin/vim (but we still have /usr/local/bin/vim70 as a backup); the runtime files go in /usr/local/share/vim/vim71a and below, where the binary will find them with no problem (and the 7.0 runtime files in /usr/local/share/vim/vim70 [or wherever] aren't touched). > (Warning: In the "ln" command as used here, the target name comes before the > link name. I find this counter-intuitive.) It's not just me then. I have to think carefully about that every time I use ln. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
