Search Results

You might try: grp() { local grep_pattern=$1 shift # remaining args are the command: "$@" | grep "$grep_pattern" | less } And invoke it like: grp nvidia pac -Q

You should only attempt to unalias if it is actually an alias: Change unalias ls to [[ $(type -t ls) == "alias" ]] && unalias ls …

There's no problem declaring a function containing unknown commands. It's not until you try to execute it that trouble occurs. $ unknown() { foo; bar; baz; } $ unknown bash: foo: command not found ba …

As @AndreasWiese comments, you can't do this with an alias. Aliases tack on arguments space-separated, so you can't join them (in a simple way) to the aliased command. …

You can use a shell function: top() { if ! type htop &>/dev/null; then sudo apt-get install htop fi htop }

If you need environment variables, you can use the env command: alias staging_server='env \ MY_ENV1="http://example.com" \ MY_ENV2="http://example2.com" \ MY_ENV3="http://example3.com" \ MY_ENV4 …

$ See 9.3 History Expansion in the manual Using this in an alias: the linked manual section says History expansion is performed immediately after a complete line is read, before the shell breaks it … Alias expansion is performed by this step (see Aliases). Given the above statements, I don't know if it's even possible to have history expansion occur in an alias. …

You could create a function and write your command "backwards" apachelog() { "$@" /var/log/apache2/error_log } apachelog tail -50

In addition to Chris's good advice to use a function, Don't parse ls Use stat to get statistics about files: lsfc() { ls -lq -- "$@" printf 'File count: %d\n' "$(stat -c '%F' "$@" | grep -cF ' …

the ~/.bash_profile is only processed for a login shell. Aliases are only available in an interactive bash session. So, referencing Invoking Bash: !bash -lic sample

In Tcl I'd write proc psgrep {pattern} { return [join [lsearch -regexp -inline -all [split [exec ps -A] \n] $pattern] \n] } set output [psgrep {a|b}]

Aliases are almost always better written as functions. The tricky part here is you chain every command together with && to abort early -- I use set -e in a subshell here for the same effect. runhole( …

As requested: This is one reason why functions are better than aliases: you can avoid quoting hell. ttn() { tail -10000 /var/log/nginx/access.log | awk '{print $1}' | sort | uniq -c | sort -nr | head …

The "bab" that gets executed after $(echo bab) will not be handled as an alias. Try using a function instead: unalias bab bab() { python "$@"; } $(echo bab) # launches a python shell …

dockerid() { docker ps -a \ | grep -o -E '^[a-z0-9]{12}' \ | awk '{printf "%s ",$0} END {print ""}' } Although the alias quoting hell goes away by replacing awk with paste alias dockerid=" …