Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm list-help: list-post: Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-apps AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Mon, 3 Jul 2000 12:54:22 -0400 To: cygwin-apps AT sourceware DOT cygnus DOT com Subject: Re: VIM 5.7 package available for testing Message-ID: <20000703125422.A27488@cygnus.com> Mail-Followup-To: cygwin-apps AT sourceware DOT cygnus DOT com References: <396055A7 DOT 40B903EA AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <396055A7.40B903EA@cygnus.com>; from vinschen@cygnus.com on Mon, Jul 03, 2000 at 10:58:15AM +0200 On Mon, Jul 03, 2000 at 10:58:15AM +0200, Corinna Vinschen wrote: >Michael Ring wrote: >> /bin/vi should be a real executeable, not a symlink because it is in >> /bin and I am trying to have things as FHS 2.X compatible as possible. >> >> So I would like to make /usr/bin/vim a link to /bin/vi.exe (Strange, I >> know; but the reason for that is the RPM-Packaging with /bin/vi >> beeing a basic dependency and enhanced vim only beeing an addon.) > >Personally I would prefer that `vim' is the executable because it >_is_ vim. `vi' is only the convenience thingy for those of us (like >me) who are used to use vi for years. If you make this a link, please make it a hard link. Otherwise it won't work outside of a cygwin environment. cgf