How can I define a bash alias as a sequence of multiple commands? [duplicate]

This question already has answers here: Multiple commands in an alias for bash (10 answers) Closed 3 years ago.

I know how to configure aliases in bash, but is there a way to configure an alias for a sequence of commands?

I.e say I want one command to change to a particular directory, then run another command.

In开发者_运维知识库 addition, is there a way to setup a command that runs "sudo mycommand", then enters the password? In the MS-DOS days I'd be looking for a .bat file but I'm unsure of the linux (or in this case Mac OSX) equivalent.

---

For chaining a sequence of commands, try this:

alias x='command1;command2;command3;'

Or you can do this:

alias x='command1 && command2 && command3'

The && makes it only execute subsequent commands if the previous returns successful.

Also for entering passwords interactively, or interfacing with other programs like that, check out expect. (http://expect.nist.gov/)

---

You mention BAT files so perhaps what you want is to write a shell script. If so then just enter the commands you want line-by-line into a file like so:

command1
command2

and ask bash to execute the file:

bash myscript.sh

If you want to be able to invoke the script directly without typing "bash" then add the following line as the first line of the file:

#! /bin/bash
command1
command2

Then mark the file as executable:

chmod 755 myscript.sh

Now you can run it just like any other executable:

./myscript.sh

Note that unix doesn't really care about file extensions. You can simply name the file "myscript" without the ".sh" extension if you like. It's that special first line that is important. For example, if you want to write your script in the Perl programming language instead of bash the first line would be:

#! /usr/bin/perl

That first line tells your shell what interpreter to invoke to execute your script.

Also, if you now copy your script into one of the directories listed in the $PATH environment variable then you can call it from anywhere by simply typing its file name:

myscript.sh

Even tab-completion works. Which is why I usually include a ~/bin directory in my $PATH so that I can easily install personal scripts. And best of all, once you have a bunch of personal scripts that you are used to having you can easily port them to any new unix machine by copying your personal ~/bin directory.

---

it's probably easier to define functions for these types of things than aliases, keeps things more readable if you want to do more than a command or two:

In your .bashrc

perform_my_command() {
    pushd /some_dir
    my_command "$@"
    popd
}

Then on the command line you can simply do:

perform_my_command my_parameter my_other_parameter "my quoted parameter"

You could do anything you like in a function, call other functions, etc.

You may want to have a look at the Advanced Bash Scripting Guide for in depth knowledge.

---

For the alias you can use this:

alias sequence='command1 -args; command2 -args;'

or if the second command must be executed only if the first one succeeds use:

alias sequence='command1 -args && command2 -args'

---

Your best bet is probably a shell function instead of an alias if the logic becomes more complex or if you need to add parameters (though bash supports aliases parameters).

This function can be defined in your .profile or .bashrc. The subshell is to avoid changing your working directory.

function myfunc {
   ( cd /tmp; command )
}

then from your command prompt

$ myfunc

For your second question you can just add your command to /etc/sudoers (if you are completely sure of what you are doing)

myuser           ALL = NOPASSWD: \
                    /bin/mycommand 

---

Apropos multiple commands in a single alias, you can use one of the logical operators to combine them. Here's one to switch to a directory and do an ls on it

      alias x="cd /tmp && ls -al"

Another option is to use a shell function. These are sh/zsh/bash commands. I don't know enough of other shells to be sure if they work.

As for the sudo thing, if you want that (although I don't think it's a good idea), the right way to go is to alter the /etc/sudoers file to get what you want.

---

You can embed the function declaration followed by the function in the alias itself, like so:

alias my_alias='f() { do_stuff_with "$@" (arguments)" ...; }; f'

The benefit of this approach over just declaring the function by itself is that you can have a peace of mind that your function is not going to be overriden by some other script you're sourcing (or using .), which might use its own helper under the same name.

E.g., Suppose you have a script init-my-workspace.sh that you're calling like . init-my-workspace.sh or source init-my-workspace.sh whose purpose is to set or export a bunch of environment variables (e.g., JAVA_HOME, PYTHON_PATH etc.). If you happen to have a function my_alias inside there, as well, then you're out of luck as the latest function declaration withing the same shell instance wins.

Conversely, aliases have separate namespace and even in case of name clash, they are looked up first. Therefore, for customization relevant to interactive usage, you should only ever use aliases.

Finally, note that the practice of putting all the aliases in the same place (e.g., ~/.bash_aliases) enables you to easily spot any name clashes.

---

you can also write a shell function; example for " cd " and "ls " combo here