On Sat, Sep 15, 2007 at 04:20:41PM -0700, Gary Johnson wrote: > > On 2007-09-15, "Ed S. Peschko" <[EMAIL PROTECTED]> wrote: > > All (especially Bram ;)), > > > > I know it's been discussed before, but how easy would it be to make: > > > > 1. uniq (and other commonly used %! commands to sort input) native > > to vim. > > 2. vim take a list of files as an input (ie: vim -l filelist) > > > > My goal is to try to make native win32 as comfortable to work on as unix, > > and > > these two issues keep popping up - and I'm sure I can think of others. In > > the > > above case, I end up ftp'ing files over to unix to do stuff like this, and > > then > > re-ftp'ing over the files to the win32 machine to process. > > > > Any ideas to get around this would be greatly appreciated as well as maybe > > adding to the above list, but I don't see any easy workarounds. > > Please don't start new threads by replying to other posts. It makes > your message appear to be part of the thread to which you replied. > Just send an original message to the list address. > > Since uniq and other external programs already exist and since vim > supports the use of such external programs, there is no good reason > to include the functionality of those programs within vim. It would > be a huge waste of Bram's time. > > If you want Windows to be as comfortable to use as Unix, I suggest > that you install Cygwin (www.cygwin.com). It is great. The Cygwin > team seems to do a good job of keeping the vim package up to date > with patches, although it's also very easy to build vim on Cygwin if > you really want the latest patches. You can then do #1 as easily on > Windows as you can on Unix, and the solution to #2 becomes > > vim $(< filelist)
*sigh*.. yes, I've gone down the cygwin path before, and no, it is not a pleasant one when you are dealing with native windows programs (either compiling or using them) For example, if you want to use ActiveState perl, no cygwin paths work. Or if you want to compile using Visual Studio, Microsoft's compilers don't play well with gmake, etc. etc. etc. Hence, it's a worthwhile thing IMO to make vim win32 aware.. When in Rome.. As for the options in question, there is a precedent - sort is implemented in vim already. I can count on one hand the programs that I regularly use inside of the buffer, and 'uniq' is one.. 'sort' ing, and then 'uniq' ing to get a count of uniq files is a very common metaphor. > You can also use Cygwin tools with the native Windows gvim, but > it becomes a little tricky, depending on what you're trying to do. > You might find Luc Hermitte's pages on Cygwin and vim useful: > > http://hermitte.free.fr/ Like you said, it's a 'little tricky' - which is a euphemism for 'damn frustrating'. I've tried it and it's frustrating enough for me to put up with the annoyances of cmd. The fact that it is so frustrating is cause enough to declare the usage problems a bug that needs to be addressed. Ed --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
