l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2001 Dec 30 17:02

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
RE: Re: [vox-tech] I don't have an .inputrc
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Re: [vox-tech] I don't have an .inputrc

  • Subject: RE: Re: [vox-tech] I don't have an .inputrc
  • From: "Deja User" <unix_MAPSadmin@my-deja.com>
  • Date: Wed, 07 Mar 2001 22:22:38 -0800

Sounds like .inputrc will be fairly important to me when I get more into 
Linux-specific projects. Thanks for the info., Micah. 

>Date: Wed, 7 Mar 2001 17:21:46 -0800
>From: Micah Cowan <micah@cowanbox.com>
>To: vox-tech@franz.mother.com
>Subject: Re: [vox-tech] I don't have an .inputrc
>Reply-To: vox-tech@franz.mother.com
>On Wed, Mar 07, 2001 at 04:48:29PM -0800, Deja User wrote:
>> When I create unix accounts using Korn shell, I modify a .profile
>> (in my home directory) and that's it. I think the way Linux/Bash is
>> configured seems unnecessarily complex. Now, someone can tell me
>> exactly how logical and simple it all is... ; ) BTW: I use ksh to
>> maintain compatibility with my work environment. I want to work more
>> with ksh scripting. Given my limited knowledge, I am assuming it
>> might be unwise to write ksh scripts in a bash environment, although
>> probably most of what I write will be sh compatible. Dunno... UA
>.inputrc isn't extra complexity - it's extra functionality.  There's
>certainly no need to use it whatsoever, but it allows you to customize
>anything which uses libreadline.
>BTW, .inputrc has absolutely nothing to do with bash (directly).  It
>has to do with libreadline, which is /used/ by bash.  It's also used
>by Perl and gdb and other things; and the changes you make in your
>.inputrc affect all those things as well.
>ksh seems to be a great shell (here I'm not talking about the one
>usually shipped with Linux, but the newest version, ksh93 I
>think...).  But bash has most of the functionality it has, and is free
>software, whereas ksh is not.  This is why I prefer bash.
>Bash also has many truly terrific features which are rarely used;
>including the abilitiy to write your own "builtin" commands and plug
>them in to a currently running session.

--== Sent via Deja.com ==--

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.