Difference between revisions of "Translations:Aliases in .bashrc/2/en"

Latest revision as of 16:14, 29 December 2022

Information about message (contribute)

This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.

Message definition (Aliases in .bashrc)

The syntax for creating a bash function is very easy. They can be declared in two different formats:
{{File|file=~/.bashrc|
content=<pre>...
function_name () {
[commands]
}
...</pre>}}
or
{{File|file=~/.bashrc|
content=<pre>...
function function_name {
[commands]
}
...</pre>}}
To pass any number of arguments to the bash function simply, put them right after the function’s name, separated by a space. The passed parameters are $1, $2, $3, etc., corresponding to the position of the parameter after the function’s name. The $0 variable is reserved for the function name.

The syntax for creating a bash function is very easy. They can be declared in two different formats:
{{File|file=~/.bashrc|
content=<pre>...
function_name () {
  [commands]
}
...</pre>}}
or
{{File|file=~/.bashrc|
content=<pre>...
function function_name {
  [commands]
}
...</pre>}}
To pass any number of arguments to the bash function simply, put them right after the function’s name, separated by a space. The passed parameters are $1, $2, $3, etc., corresponding to the position of the parameter after the function’s name. The $0 variable is reserved for the function name.

The syntax for creating a bash function is very easy. They can be declared in two different formats:

~/.bashrc

...
function_name () {
  [commands]
}
...

or

~/.bashrc

...
function function_name {
  [commands]
}
...

To pass any number of arguments to the bash function simply, put them right after the function’s name, separated by a space. The passed parameters are $1, $2, $3, etc., corresponding to the position of the parameter after the function’s name. The $0 variable is reserved for the function name.