Date: Thu, 25 Jun 2009 13:28:54 +0800 From: Erich Dollansky <erich@apsara.com.sg> To: freebsd-questions@freebsd.org Cc: Manish Jain <invalid.pointer@gmail.com>, bf1783@googlemail.com Subject: Re: The question of moving vi to /bin Message-ID: <200906251328.55846.erich@apsara.com.sg> In-Reply-To: <4A430505.2020909@gmail.com> References: <4A430505.2020909@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On 25 June 2009 pm 13:03:01 Manish Jain wrote: > > If you want to make a case for replacing ed(1), you're going > > to have to come up with some concrete reasons for doing so, > > not just make a (long and hyperbolic) statement that you > > don't like it. > > requirements of being interactive. That's one reason. Secondly, > how many times does an average commandline user even think of > using ed when he needs to edit a file, even in the extreme case > where there are no alternatives ? > isn't there ee in the base system? > Till the improvements are in place, we need the alternative of > having vi under /bin rather than /usr/bin. > I do not see any reason to have a monster like vi there. > Actually, it surprises me to what extent the core of the > FreeBSD community is enamoured with this idea of a > micro-minimalistic base, in which it is practically impossible > to do anything except run fsck. Matters don't stop there. > Seeing the limitations of this approach, the community churns > up wierd workarounds like /rescue/vi, when all that was needed > was shift vi from /usr. You talk about the need for compliance Only people who want to use vi do this. The rest is happy with ee. > But I guess my words are of no use when the people who matter > just won't listen. So I give any hopes in this regard. I hope that they do not listen. It would be even better to have an editor like joe in /bin than anything like vi. Erich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200906251328.55846.erich>