While I'm mostly a fan of cygwin, it's very slow compared to native ports of tools. It makes nice glue, but whenever possible, look for a native port for tools like xemacs, ImageMagick, perl, etc. You can then put their paths early so that you pick them up first (or put links to them in ~/bin or the like). ImageMagick is a great example of this. I couldn't believe how much slower convert was than doing the work in PhotoShop (even including loading up Photoshop and all the images). Then I dumped the cygwin version and ran a native port (under cygwin's bash) and all was well again.
Of course, getting all the tools I need to work on windows finally got to be too much trouble, and I've gone back to my two-machine solution. Image capture/cleanup in Windows with PhotoShop Elements (which continues to be better than gimp for this kind of work; no offense), than mass convert-ization and album-ization on linux running samba. Rob On Tue, Feb 19, 2002 at 09:39:55AM -0500, John Turner wrote: > Cygwin is a must have for every Linux user forced to use > a Windows machine. I was even able to get sshd working > and we were able to get a remote bash shell on our NT/Win2K > servers. > > John > > On Tue, Feb 19, 2002 at 08:28:44AM -0500, Chris Merrill wrote: > > Benjamin Reed wrote: > > > > > Yup... PuTTY makes Windows usable... by letting you SSH to a real > > > OS. <g> > > > > > > I'm becoming fond of Cygwin. But it's considerably more than > > an SSH/Telnet client. An entire linux shell (bash?) - now that > > I've installed enough extensions (like CVS) I can run our > > Linux build process on my W2k box. Of course, the best part > > is having a decent console for those tasks best accomplished > > with keyboard.
