From: Eric Olinger <EvvL@RustedHalo.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] install CD bloat
Date: Wed, 20 Aug 2003 09:31:31 -0700 [thread overview]
Message-ID: <20030820093131.00001665.EvvL@RustedHalo.net> (raw)
In-Reply-To: <1061394716.414.42.camel@vertigo>
On 20 Aug 2003 11:51:56 -0400
Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> vim is only available outside of chroot. It is not in the stages, and
> isn't available while in chroot. Personally, I HATE nano, but I think
> if we're going to have an editor on the CD by default, we should pick
> one and stick with it rather than trying to meet the needs of every
> user's desire. After all, what's next? "I hate nano and vim, someone
> put emacs on the Live CD."
If were really talking about saving space on the livecd we could always replace
vim with nVi. It has all the basic vi features in a lot smaller package. Plus in
that extra space put a small emacs work-alike like qemacs. I don't use emacs
but I always assumed that since we had Vi on the cd that Emacs was on the
cd as well. It'd be good to have at least the the two most common editors on
the cd or at least work-alikes.
--
Eric Olinger (http://evvl.rustedhalo.net/pgp_key.txt)
The cure for 1984 is 1776.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-20 16:31 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 19:42 [gentoo-dev] install CD bloat Kurt Lieber
2003-08-18 21:17 ` Dhruba Bandopadhyay
2003-08-18 23:03 ` Stuart Herbert
2003-08-19 0:06 ` Bob Johnson
2003-08-19 1:33 ` Luke-Jr
2003-08-19 6:47 ` Sven Vermeulen
2003-08-19 6:54 ` Jon Portnoy
2003-08-19 6:59 ` Sven Vermeulen
2003-08-19 7:10 ` Jon Portnoy
2003-08-21 5:00 ` Stewart Honsberger
2003-08-21 6:16 ` C. Brewer
2003-08-20 1:10 ` Luke-Jr
2003-08-20 7:31 ` Sven Vermeulen
2003-08-20 13:09 ` Chris Gianelloni
2003-08-20 12:39 ` Chris Gianelloni
2003-08-20 13:18 ` Michael Cummings
2003-08-20 13:18 ` Douglas Russell
2003-08-20 14:05 ` Tobias Sager
2003-08-20 15:27 ` Aron Griffis
2003-08-20 15:56 ` Svyatogor
2003-08-20 15:51 ` Chris Gianelloni
2003-08-20 16:27 ` matt c
2003-08-20 17:09 ` Douglas Russell
2003-08-20 18:36 ` Paul de Vrieze
2003-08-20 22:51 ` Stuart Herbert
2003-08-20 16:31 ` Eric Olinger [this message]
2003-08-20 17:05 ` Matt Rickard
2003-08-21 5:13 ` Stewart Honsberger
2003-08-21 5:42 ` Jon Portnoy
2003-08-21 5:59 ` Stewart Honsberger
2003-08-21 6:08 ` Jon Portnoy
2003-08-21 6:25 ` Stewart Honsberger
2003-08-21 6:51 ` Ralph F. De Witt
[not found] ` <3F4464DC.1010904@snerk.org>
2003-08-21 6:30 ` Jon Portnoy
2003-08-21 16:58 ` [gentoo-dev] OT: Re: Nano. WAS: " Stroller
2003-08-21 17:41 ` Mike Frysinger
2003-08-21 9:34 ` [gentoo-dev] " Chris Gianelloni
2003-08-21 9:54 ` Douglas Russell
2003-08-21 17:55 ` Jon Portnoy
2003-08-21 9:52 ` Toby Dickenson
2003-08-20 18:43 ` Paul de Vrieze
2003-08-20 22:42 ` Stuart Herbert
2003-08-20 23:34 ` Tavis Ormandy
2003-08-21 1:16 ` Chris Gianelloni
2003-08-21 2:06 ` Luke-Jr
2003-08-21 10:29 ` Paul de Vrieze
2003-08-23 14:43 ` Stuart Herbert
2003-08-20 15:22 ` Aron Griffis
2003-08-20 12:43 ` Kurt Lieber
2003-08-20 14:09 ` Luke-Jr
2003-08-20 18:40 ` Paul de Vrieze
2003-08-20 20:01 ` Daniel Armyr
2003-08-20 23:05 ` William Kenworthy
2003-08-19 11:21 ` Chris Gianelloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030820093131.00001665.EvvL@RustedHalo.net \
--to=evvl@rustedhalo.net \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox