Kituu

Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net

Score 70.0%

Description:

Fully configurable BASH environment ; You can copy it to all your users/root home folders (and to /etc/skel for all future ones) and it will automatically display "root" in the color you define. Bad root.

(Follow me on twitter https://twitter.com/xaccrocheur)

-Two-lines stable display
-Double-clickable full path (for copy & pasting)
-Simple and light load-meter
-Visual status of the latest command output
-Command history available across all new shells
-Cool aliases
-(Optional) "Greetings" mode

Many, if not all aspects, are configurable in the commented file ; It's also meant to be as secure as possible and avoids exporting crap in your env. Many surprises as well. I spent some time on this one. Bug reports *welcome*

Use this little script :
http://www.box.net/shared/6ncm8z214l
To help you find your colors

If you defined custom paths and aliases in your existing .bashrc, don't forget to source them in the new one. Always keep a backup.

You should check this page regularly for updates. Use the force, read the source ;)

NOTE: this .bashrc only works with UTF-8 capable terminal emulators.

Don't forget that http://www.catonmat.net/blog/bash-emacs-editing-mode-cheat-sheet/

Mandriva GNU/Linux rocks

Last changelog:

7 years ago

0.8.2
colored path if on remote machine
0.8.1
-Now hosted on github
-Fixed the "first connection" arithmetic bug
0.8.0
-Major rewrite ; I realized that some terms were not correctly handled. Also I wanted it to run on older, non-ansi systems, old bashes.

miawallace
7 years ago

It seems to finish the install, but then i type "bash" and it gives me this:
bash: /git-completion.bash: Permission denied
How to fix this please?

Report

Zeroangel
7 years ago

I kept getting this error when opening the terminal for the first time in a session:
bash: let: pwdmaxlen=/2: syntax error: operand expected (error token is "/2")

I managed to fix it by commenting out an original line in the bashrc and replacing it with one that was formatted differently:
# let pwdmaxlen=${COLUMNS}/2
(( pwdmaxlen = COLUMNS /2 ))

Report

xaccrocheur
7 years ago

Wow, thanks a bunch, dude.

Report

xaccrocheur
8 years ago

Hi SeaJey ;

Those lines duplicate what kituu already does :

The export HISTCONTROL=something deal with history handling. The way it's configured in kituu is :

-only remove duplicate commands.
-Export the history file to any new shell.

(hss allows searching in the history, it's an alias for history | grep)

If you're ok with that policy, then remove them. Same with the less stuff. What system are you using ?

Report

SeaJey
8 years ago

Excuse me for disturbance - I've found some duplicates after posting the comment.

But could you please share your screenshots with activated "stupid squirrel" or "cute plane"?

I've some misbehavior with those options.

Report

xaccrocheur
8 years ago

Au contraire Seajay, thank you for your feedback ; Although I spend time ensuring that the greetings options play nice w/ each other, on some systems, display glitches may occur, in this case put all greetings options to yes, and start removing some. I myself don't use the greetings, hence all the settings defaulting to "no" ; I put them back on to test them them over time

Report

SeaJey
8 years ago

I've inspected my own .bashrc before switching to Kituu and saw this sections:

# don't put duplicate lines in the history. See bash(1) for more options
export HISTCONTROL=ignoredups
# ... and ignore same sucessive entries.
export HISTCONTROL=ignoreboth

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(lesspipe)"

Could you comment about their usefulness?

Report