Re: VIM doesn't need new features?!?!

[Charles E Campbell Jr]

Peter Michaux wrote:


 And now I see that VIM doesn't need more features...

http://www.vim.org/soc/ideas.php


May I suggest taking a look at:

 http://vim.sourceforge.net/sponsor/vote_results.php

Regards,
Chip Campbell

RE: VIM doesn't need new features?!?!

[Halim, Salman]

I really didn't think Peter said anything that was a flame.  Perhaps he
didn't read the whole thing, but I, too, initially walked away with the
same conclusion was he did, and I *have* been using Vim for a long time.
(I just know better because I've been here longer.)

Suresh, on the other hand, was pretty much out of line and actually took
it to the level of personal attacks.  Makes me wonder if he's really
Sven Guckes in disguise.

Salman.

 -Original Message-
 From: Milan Vancura [mailto:[EMAIL PROTECTED] 
 Sent: Monday, April 16, 2007 3:27 AM
 To: Vim development list
 Subject: Re: VIM doesn't need new features?!?!
 
The preceding shows you have trouble reading -- that page has a  
   link to a voting page, which page lists certain core features  
   that could be added to vim.  If your investigation into 
 plugins  was 
   as casual as your reading of the above link, then your 
 efforts  at 
   finding and evaluating existing plugins in relation to 
 your  notion 
   of a project are likely to have been botched!
  
  Vim has many, many features. We don't really need more
 
 Peter, don't start flames, please. vim-dev list is a very 
 valuable list exactly for the reason that people usualy don't 
 try flaming here.
 
 It's easy to take one sentence without any context and become 
 upset. Read more (as Suresh Govindachar already suggested) 
 and your life will be nicer again.
 Please start with Suresh Govindachar's e-mail, the answer for 
 you is already there. The sentence you started a flame with 
 means that it seems we can add new features by some script 
 languages (most usualy the internal vim script) and don't 
 need to add every bell and whistle in the core vim code.
 
 And it's true for your problem too: core vim features are 
 strong enough to allow project handling - but the exact 
 implementation is up to your choice.
 There are several plugins ready at vim.org which you can use 
 or modify. 
 
 So again: please start reading at vim.org again with this 
 information in mind.
 And stop the flame. If you have a concrete question, ask here 
 or at vim-users.
 
 Thank you and have a nice day,
 
 Milan Vancura
 --
 Milan Vancura, Prague, Czech Republic, Europe
 

Re: vim patch for cygwin

[Luca Masini]

Bram Moolenaar wrote:

 The mch_FullName() in os_unix.c already takes care of symlinks.  Why
 would this extra code for Cygwin be needed?

 If something needs to be patched it's probably best done in 
mch_FullName().



In cygwin /etc/hosts is a symbolic link to 
C:\WINDOWS\system32\drivers\etc\hosts

and if expanded in that way is not recognized as a full path because
does not start with / or with ~.

The small patch change it in posix format
 /cygdrive/c/WINDOWS/system32/drivers/etc/hosts
so it is recognized as a full path and the .swp file
is created (in the other case there is the
message *E303* Unable to open swap file)

Maybe the mch_FullName() is a better place to put the
cygwin_conv_to_posix_path().
I have put it there because there is also
slash_adjust() for other platform.

Luca.