Commands using export (101)
-
So this first obtains address of the DBUS session, as it's not available by default over SSH. Then it tells plasma-overlay to exit. `kquitapp` is pretty much an equivalent of the qdbus calls.
0( eval $(grep -z '^DBUS_SESSION_BUS_ADDRESS' /proc/$(pgrep -u $USER plasma-overlay)/environ); export DBUS_SESSION_BUS_ADDRESS; kquitapp plasma-overlay ) -
Yo run the `nohist` command and after that the commands won't get stored in the history file for the current session. This makes no permanent changes.
0nohist(){ export HISTFILE=/dev/null; } -
that's how I do it in ubuntu
0echo test $DISPLAY > /dev/null || export DISPLAY=:0.0; xset dpms force off;gnome-screensaver-command -l -
Need to change values of 'field 1'...'field 3' to column names. input_file.tsv is the tab file you want to conver output_file.json is the file that is created with the json output. Assumes your tsv has no headers.
0export FIELDS=field_1,field_2,field_3; cat input_file.tsv| ruby -rjson -ne 'puts ENV["FIELDS"].split(",").zip($_.strip.split("\t")).inject({}){|h,x| h[x[0]]=x[1];h}.to_json' > output_file.json -
Useful if you have multiple versions of Java installed. The 1.7 pkg for Mac doesn't tell you anything about where it's putting stuff. Show Sample Output
0export JAVA_HOME=$(/usr/libexec/java_home -v 1.7) -
e.g.
OLDDIALOGRC=$DIALOGRC; export DIALOGRC=/dev/stdin; echo -e "screen_color = (CYAN,RED,ON)" | dialog --infobox "\nfoo bar" 5 11; export DIALOGRC=$OLDDIALOGRCAlternative:OLDDIALOGRC=$DIALOGRC; export DIALOGRC=/dev/stdin; printf "<configuration>\n" | dialog <options>; export DIALOGRC=$OLDDIALOGRC0OLDDIALOGRC=$DIALOGRC; export DIALOGRC=/dev/stdin; echo -e "<configuration>" | dialog <options>; export DIALOGRC=$OLDDIALOGRC -
A simple PS1, ready to be used. Just paste in your ~/.bashrc Show Sample Output
0export PS1="[\[\e[1;32m\]\u\[\e[m\]\[\e[1;31m\]@\[\e[m\]\[\e[3;35m\]\H\[\e[m\] \[\e[1;30m\]| \[\e[m\]\[\e[1;34m\]\w\[\e[m\] \[\e[1;29m\]\t\[\e[m\]]\[\e[1;33m\]$\[\e[m\]" -
From a local node, retrieve the date from server A and set that time on server B. When ntpd is not an option and you need to get closest clock sync between two nodes Replace SRC_SRV with yout source server and DST_SRV with your destination server. You must have ssh access to both and sudo access to the the destination to set the date. Show Sample Output
0env TERM="$(ssh SRC_SRV "date"):TERM" ssh -t DST_SRV 'TS=${TERM%:*}; TERM=${TERM##*:}; export TS; date ; sudo date -s "$TS"; date' -
This command is named "rope" since it ties a rope in the directory you are in... so when you go to other directories you can type "rope" again and you will get back to tied directory... it helps a lot when you forget to execute a command in other directories, so you can go, do what you want, and return to the directory to complete what you now want to do. NOTE: add this command to the end of ".bashrc" file found in your home directory and the alias will be permanent
0alias rope='if [[ "$i" == "0" ]]; then cd $dir; i=1; else dir=$(pwd); export dir; i=0; fi' -
-1export PS1='\D{%a %D %T}> '
-
#ps aliases PSO='user,pid,ppid,%cpu,%mem,time,start,state,command' PSOA='user,pid,time,state,command' PSOL='user,pid,ppid,%cpu,%mem,nice,pri,etime,time,tt,state,ucomm' export PSO PSOA PSOL function _ps { /bin/ps $@ ; } alias ps='_ps ax -o $PSO' alias psa='_ps ax -o $PSOA' alias psl='_ps ax -o $PSOL' alias psm='_ps -U $USER -o $PSOA'
-1export PSOA='user,pid,time,state,command' ; function _ps { /bin/ps $@ ; } ; alias psa='_ps ax -o $PSOA' -
a pretty simple script when running java programs from command line Show Sample Output
-1CLASSPATH=.; export CLASSPATH=$CLASSPATH$(find "$PWD" -name '*.jar' -type f -printf ':%p\n' | sort -u | tr -d '\n'); echo $CLASSPATH -
(1) don't run twice, or the same folder will occur in $PATH. (2) otherwise you need to start a new terminal Show Sample Output
-1export PATH=$PATH$(find "$PWD" -name '.*' -prune -o -type f -a -perm /u+x -printf ':%h\n' | sort -u | tr -d '\n'); echo $PATH -
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!
-1export PS1="C:\\>"; clear -
-1export PS1="[\u@`curl icanhazip.com` \W]$ "
-
-1export IP="$(hostname -I | awk '{print $1}')"
-
-2export PS1='[\[\e[36;1m\]\u@\[\e[32;1m\]\h \[\e[31;1m\]\w]# \[\e[0m\]'
-
Not always does Xorg run on :0. For times like those, this script allows you to find out which it is.
-2export DISPLAY=$(tr '\000' '\n' < /proc/`pidof Xorg`/cmdline | egrep '^:[0-9]+') -
Like the given command, but combines _DISPLAY=":0.0"_ with _export DISPLAY_ to get _export DISPLAY=":0.0"_ and only imports if DISPLAY is set successfully.
-3export DISPLAY=":0.0" && import -window root screenshot.png -
This will temporarily add the current directory to your $PATH. Allowing you to execute from that directory for the duration of the session.
-3export PATH=$PATH:`pwd` -
changes the PS1 to something better than default. [username.hostname.last-2-digits-of-ip] (current directory) Show Sample Output
-4newhostname=$(hostname | awk -F. '{print $1 "." $2}'); ipaddress=$(nslookup `hostname` | grep -i address | awk -F" " '{print $2}' | awk -F. '{print $3 "." $4}' | grep -v 64.142);PS1="[`id -un`.$newhostname.$ipaddress]"' (${PWD}): '; export PS1 -
-4export IFS=$'\n';for dir in $( ls -l | grep ^d | cut -c 52-);do du -sh $dir; done
-
This command is great for dumping your history so that when you're working on a system that is under a shared account, you can keep others from reviewing your history file. I use this when I'm just visiting a system to diagnose a problem, or to make a quick fix.
-4export HISTFILE=/dev/null/ -
This will kill a specific process you don't know the PID of, when pidof and pgrep are not available, for example on OS X. var1 is created so that the whitespace can be trimmed before passing off to kill. Show Sample Output
-5export var1=`ps -A | grep '[u]nique' | cut -d '?' -f 1`; echo${var1/ /}; kill -9 $var1 -
only during session
-5export PATH=$PATH:/home/user/my_prog - ‹ First < 2 3 4 5 >
What's this?
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Check These Out
Stay in the loop…
- Follow the Tweets.
-
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10 - Subscribe to the feeds.
-
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
- » commands using export