Comments on: Enhanced Bash

By: Enhanced Bash : Linux T&T

Enhanced Bash : Linux T&T — Fri, 07 Aug 2009 11:04:56 +0000

[...] Enhanced Bash | AmirWatad.com [...]

By: Amir Watad

Amir Watad — Sat, 07 Feb 2009 20:49:25 +0000

Hey nbensa!
Thank you for this useful information.
I didn’t got the thing with not recording commands with passwords, what makes the HISTORYIGNORE to ignore passwords?

Thank you again

By: nbensa

nbensa — Sat, 07 Feb 2009 18:27:06 +0000

I forgot to say you can add a timestamp too:

In bashrc:

export HISTTIMEFORMAT=”%F %T ”

And for those who don’t want to lose default inputrc settings, you can add include to your .inputrc:

$include /etc/inputrc
your-custom-settings-here

Regards

By: nbensa

nbensa — Sat, 07 Feb 2009 18:15:24 +0000

While you’re at it, add to inputrc:

set completion-ignore-case on

This way you can to:

cd deskt[TAB]

and you’ll get “cd Desktop/”

To bashrc add:

shopt -s cdspell

Now try:

cd /vr

For history you can add to bashrc:

export HISTORYIGNORE=”&:ls:[bf]g:exit:[ \t]*”

and history will ignore “ls”, bg, fg, exit, commands as well as commands starting with a space or tab. The last one is pretty handy if you want to not record history for commands containing passwords. For example:

sudo mount -t smbfs -o username=user,password=s3krEtPa55 //server/share /mount/point

Regards

By: Enhanced Bash | Nica's Blog

Enhanced Bash | Nica's Blog — Tue, 03 Feb 2009 03:32:39 +0000

[...] (以上程式碼取自：http://www.amirwatad.com/blog/archives/2009/01/30/enhanced-bash/) [...]

By: Amir Watad

Amir Watad — Mon, 02 Feb 2009 13:08:23 +0000

Thank you Bret.
By the way, there is no such thing “sourcing .inputrc”, you shouldn’t source it since it’s not a bash-script. I believe this is the reason of most of the command-not-found errors people faced.

By: Brett

Brett — Mon, 02 Feb 2009 07:51:35 +0000

To everyone getting a “command not found” error when sourcing the .bashrc or .inputrc, this most likely a copy and paste error.
Make sure the single quote “‘” (which bash will interpret as the start of a string) is not getting converted to a backtick “`” (which bash will interpret as “execute inline”, causing the commond not found error).
Also if your home dir does not have a .inputrc in it just create the file, relogin and bash will load those settings for you.
Thanks Amir, great tips

By: Amir Watad

Amir Watad — Mon, 02 Feb 2009 01:16:46 +0000

Hi Bjarke,
Thank you for your comment.
Indeed, there is the /etc/inputrc file, and it’s similar to ~/.inputrc, except that it’s a system wide file (i.e. affects all users, and this is why you need root privileges to edit it).
~/.inputrc is a per user file, and I prefer to edit it and not the system wide file (except if you have a reason to make changes for all users).

Sometimes ~/.inputrc is not found by default, and you need to create it.

Please notice that ~/.inputrc and /etc/inputrc are NOT bash scripts, so please don’t try to source them (i.e. by typing source .inputrc or . .inputrc etc..), you’ll get errors from the simple reason that you’re trying to run a non-script file.

Thanks again for your comments

By: Bjarke Bruun

Bjarke Bruun — Mon, 02 Feb 2009 00:58:29 +0000

The inputrc file is a global file located in /etc aka /etc/intpurc – you need to be root to edit it. It is also where you can disable the annoying bell sound by uncommenting the

set bell-style none

By: Christian

Christian — Sun, 01 Feb 2009 14:40:23 +0000

E-mail sent.