Commands using export

On systems where your home directory is shared across different machines, your bash history will be global, rather than being a separate history per machine. This setting in your .bashrc file will ensure that each machine has its own history file.

usage: dng BRE [selection]

default selection is the last match

DNS is ok, but although domainnames may be easier to remember than IP numbers, it still requires typing them out. This can be error-prone. Even more so than typing IPv4 numbers, depending on the domainname, its length and complexity.

combination of several of the above

Adds a function that runs every time the prompt is rendered. The function grabs the CWD from PWD and issues a command to tmux to change the current window

when working with many machines in a computer lab need to know the IP addr is very large, this is a simplistic solution to make things easier

I was surprised to find that with RedHat bash, I could not find any comment lines (begining with #) in my bash shell history. Surprised because in Mageia Linux this works. It turns out that RedHat's bash will keep comment lines if in my .bashrc, I define:

export HISTIGNORE=' cd "`*: PROMPT_COMMAND=?*?'

Why have comment lines in shell history? It's a handy and convenient way to make proto-commands (to be completed later) and for storing brief text data that is searchable in shell history.

This will affect all invocations of grep, even when it is called from inside a script.

Is there somebody that uses Windows a lot that keeps messing up your Linux machine? Press Ctrl+Alt+F1-F6 and run this command after logging into a text shell!

Thanks to the authors of:

and the author of:

and others, we can have a fast Linux or android.

IMPORTANT if you find a priority order problem in PATH you can push a path directory to the front without duplication as follows:

then ...

Check duplication with:

Finally do a very neat line by line list of $PATH:

The speed up is very noticeable for android, and builds on Linux Ubantu are much faster with make and scripts.

I will update the command on request. Timothy from SONY

(1) don't run twice, or the same folder will occur in $PATH.

(2) otherwise you need to start a new terminal

a pretty simple script when running java programs from command line

This will temporarily add the current directory to your $PATH. Allowing you to execute from that directory for the duration of the session.

Useful in root's .profile - will auto-logout after TMOUT seconds of inactivity.

Close after `seconds` inactive.

export TMOUT=seconds

(unefunge)

Adds the time in 12hr AM/PM format to the beginning of a prompt. Change \@ to \t for 24-hour time or \T for 12hr without AM/PM.

To keep the time the next time you open a terminal, edit ~/.bashrc and stick the command at the bottom.

pushd and popd are your friends, but sometimes they're just incompatible with the way one works...

Two shell functions:

bm bookmarkname - "bookmarks" the current directory, just 'cd $BMbookmarkname' to return to it.

forget bookmarkname - unsets the 'bookmarkname' variable. It isn't mandatory, they cease to exist when the session ends.

If the return code from the last command was greater than zero, colour part of your prompt red. The commands give a prompt like this:

[user current_directory]$

After an error, the "[user" part is automatically coloured red.

Tested using bash on xterm and terminal. Place in your .bashrc or .bash_profile.

This will cause bash to fix a garbled terminal before the prompt is printed. For example, if you cat a file with nonprintable character sequences, the terminal sometimes ends up in a mode where it only prints line drawing characters. This sequence will return the terminal to the standard character set after every command.

I used to do a lot of path manipulation to set up my development environment (PATH, LD_LIBRARY_PATH, etc), and one part of my environment wasn't always aware of what the rest of the environment needed in the path. Thus resetting the entire PATH variable wasn't an option; modifying it made sense.

The original version of the functions used sed, which turned out to be really slow when called many times from my bashrc, and it could take up to 10 seconds to login. Switching to parameter substitution sped things up significantly.

The commands here don't clean up the path when they are done (so e.g. the path gets cluttered with colons). But the code is easy to read for a one-liner.

The full function looks like this:

I tried using regexes to make this into a cleaner one-liner, but remove_path ended up being cryptic and not working as well:

you should have the "most" package installed. I like it because it is colorful and easier to read. alternatively you can use "less" instead of "most".

you can also add this to your ~/.bashrc to make it permanent.