From: Stuart Winter on
> Reqest to Slackware installation media developers:
>
> Can we (extra pretty) PLEASE have Nano on the install disks?
>
> Midnight Commander would be nice too, and there is plenty of room on the
> DVD for these distinctly useful tools.

I assume that you mean including them within the installer
environment -within the RAM disk.

The RAM disk is supposed to be kept small, originally because
the kernels (as I recall) wouldn't boot a RAM disk over
a certain size on x86, and I believe SPARC had a similar
size limit on the RAM disk.

Whilst the installer can be used as a pretty good rescue environment,
its primary function is to get the OS installed -- neither nano nor
mc are necessary to do that. We've added in other tools, either
as separate utilities or new features in busybox, but these are
for networking or encryption.

If you were rescuing a system which had nano on it, you could
chroot into the mount and run nano and mc there -- assuming
the OS was in a useable state.

--
Stuart Winter
www.slackware.com/~mozes
Slackware for ARM: www.armedslack.org
From: Lew Pitcher on
Sylvain Robitaille <syl(a)alcor.concordia.ca> trolled:

Sylvain Robitaille is French Canadien.

And the game was fixed. Everyone knows it.

LewPitcher(a)LewPitcher.ca
--
Official Website -->> http://lewpitcher.ca/
Something to look at: -->> http://www.emusclemag.com/
Lonely in Brampton? -->> http://gaypros.meetup.com/cities/ca/on/brampton/
Peel HIV/AIDS Network -->> http://www.phan.ca/home.html
From: Jim Diamond on
On 2009-11-30 at 02:42 AST, Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote:
> Jim Diamond <Jim.Diamond(a)nospam.AcadiaU.ca> wrote:
>> I use both myself. Vi for quick edits, emacs for serious work. Don't
>> ask me why :-)
>
> I think I understand why. Emacs with all its features might be a little to
> "bloated" to start for only a quick edit.
Well, given that I have an emacs server always running, that's not
it. Maybe I don't like the "context switch" of emacs opening a new
window, whereas I use vi in the terminal window.

> Sometimes for quick appends I don't start any editor at all, I then
> only use echo and >>.
That's too slow for more than one line: use "cat >>" :-)

Cheers.
Jim
From: Theodore Heise on
On Mon, 30 Nov 2009 06:04:04 +0000 (UTC),
Sylvain Robitaille <syl(a)alcor.concordia.ca> wrote:
> On Sun, 29 Nov 2009 10:31:44 -0500, Theodore Heise wrote:
>
>> The command ^J should do this, but you will need to call pico
>> with the quote string specified (i.e., pico -Q "> "). ...
>
> I just tested with the sample text I supplied, and it seems to
> reformat each individual line, rather than the block of text, so
> it's certainly not the same functionality as what I'd learned in
> vim.

Yes, I thought I explained that limitation. Pico will reformat a
whole block of text preceded by any number of the specified quote
character and single spaces. If there are multiple adjacent
spaces, it treats this as a new block. For probably better than
90% of the posts I reply to, pico reformats blocks of text just
fine. For the few that have multiple adjacent spaces, the added
editing is pretty trivial (I don't usually quote a lot).

--
Theodore (Ted) Heise <theo(a)heise.nu> Bloomington, IN, USA
From: Sylvain Robitaille on
On Mon, 30 Nov 2009 23:19:38 -0500, Theodore Heise wrote:

> ... Pico will reformat a whole block of text preceded by any number
> of the specified quote character and single spaces. If there are
> multiple adjacent spaces, it treats this as a new block. For probably
> better than 90% of the posts I reply to, pico reformats blocks of text
> just fine. ...

If you let yourself get used to how this works in vim, I assure you you
won't go back to pico ...

--
----------------------------------------------------------------------
Sylvain Robitaille syl(a)encs.concordia.ca

Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------