setting options in bash

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: GregGreg.Furmanek@hit.cendant.com
Date:  
Subject: setting options in bash
Ok.

I am using Mandrake, so you can add this distro to your list
of distros with behavior simular to RH.

The Wolf


-----Original Message-----
From: Kevin Buettner [mailto:kev@primenet.com]
Sent: Wednesday, May 03, 2000 6:23 PM
To:
Subject: Re: setting options in bash


On May 1, 7:51am, Gorman, John wrote:

> Also set it in your .bash_profile


I haven't looked at the precise reasons why, but for some reason,
the line

    INPUTRC=/etc/inputrc


in /etc/profile prevents "set -o vi" from working when placed in
either .bashrc or .bash_profile.

Not all distributions do this; Red Hat does, but TurboLinux does
not. (Those are the only ones I have installed at the moment.)

Putting "set editing-mode vi" in your ~/.inputrc file is really a
better solution than "set -o vi" (in either .bash_profile or .bashrc)
because then vi command line editing will work in other tools which
use the readline library. E.g, if you use the command line version of
gdb, you'll find that the history mechanism and line editing
mechanisms will be set to vi bindings just as they are in bash (when
you use this setting).

I've just noticed that python seems to use the readline library.
Perl can be enabled to use readline as well if you install the
Term::ReadLine and Term::ReadKey modules.

Kevin

--
Kevin Buettner
,

_______________________________________________
Plug-discuss mailing list -
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss