Recherche
Voici les résultats de votre recherche.
Résultats plein texte:
- basics
- tes** in the file! You can follow the process by using ''echo'' as a fake interpreter: <code> #!/bin/ech... o in some flow control statements. An example of using the exit code of the program ''grep'' to check if... rk) to make it a comment. There's a little trick, using the pseudo command '':'' (colon) and input redire... e a variable's scope //local// to a function: * Using the ''local'' keyword, or * Using ''declare'' (
- obselete
- n and should never be used, and the explicit form using separate redirections is preferred over both. The... n the Korn and POSIX style function definitions - using both the ''function'' keyword and parentheses. It... modern shell (and then some). The only reason for using backticks is for compatibility with a real Bourne... rors, it's better to test for undefined variables using one of [[http://mywiki.wooledge.org/BashFAQ/083 |
- scripting
- ipt, it's only for us humans. I'm used to seeing/using indentation of //two space characters// (though m... uld follow one of these two rules: __**Indention using command width:**__ <code> activate some_very_long... some_other_option </code> __**Indention using two spaces:**__ <code> activate some_very_long_op... thing. Good names help document your code without using extra comments. **do not use command names for y
- behaviours
- /.bash_login'', or ''~/.profile'' (in that order, using the first one that's readable!). When a login sh... TS]] is ignored at startup * redirecting output using the ''>'', ''>|'', ''<>'', ''>&'', ''&>'', and ''... ns to the enable builtin command is forbidden * using the ''enable'' builtin command to enable disabled