Date: Thu, 16 Jul 1998 08:09:59 +0200 From: Johann Visagie <wjv@cityip.co.za> To: "Kevin G. Eliuk" <kevin_eliuk@sunshine.net> Cc: Chris Browning <brownicm@netunlimited.net>, freebsd-questions@FreeBSD.ORG Subject: Re: Doskey Message-ID: <19980716080959.A19152@cityip.co.za> In-Reply-To: <Pine.BSF.3.96.980715222344.432D-100000@vanessa.eliuk.org>; from Kevin G. Eliuk on Wed, Jul 15, 1998 at 10:28:26PM -0700 References: <19980715204302.A17838@cityip.co.za> <Pine.BSF.3.96.980715222344.432D-100000@vanessa.eliuk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 15 Jul 1998 at 22:28 SAT, Kevin G. Eliuk wrote: > > I am surprised that noone has mentioned uncommenting this in ~/.profile > in 2.2.5 and earlier and ~/.shrc in 2.2.6. > > # Uncomment next line to enable the builtin emacs(1) command line editor > # in sh(1), e.g. C-a -> beginning-of-line. > set -o emacs > > and it enables the same feature as `Doskey' as well as others. Hey, I admit I didn't know that was available in sh. bash uses emacs line editing by default. Of course, what is _really_ funky is to "set -o vi", though I admit that even I can't stand that for long periods of time, inveterate vi user that I am. ;-) -- V Johann Visagie | Email: wjv@CityIP.co.za | Tel: +27 21 419-7878 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980716080959.A19152>