Recherche
Voici les résultats de votre recherche.
Résultats plein texte:
- obsolete
- cept maybe code golfers. New scripts should never use them. None of the items on this list are specifie... e operator. Overall, it's pointless syntax bloat. Use an explicit redirect instead.| |''function\ NAME(... nly ''for'' works in Bash. Needless to say, don't use it.| This table lists syntax that is specified b... g clean, safe scripts. Well-written scripts don't use word-splitting. A few exceptions are listed on th
- positional-parameters
- ves as described above. To get the function name, use ''$FUNCNAME''. ===== Shifting ===== The builtin... ' is defined (but may be null), using [[syntax:pe#use_an_alternate_value | parameter expansion for an a... ssed to the script or function. If you want to re-use your positional parameters to **call another prog... wrapper-script), then this is the choice for you, use double quoted ''"$@"''. Well, let's just say: **
- redirection
- e. you want to redirect this descriptor, you just use the number: <code> # this executes the cat-comman... or, to point to its current target file, then you use a "''&''" followed by a the descriptor number: <c... akes one or two words as operands. If you have to use operands (e.g. filenames to redirect to) that con... code also when using here-documents. The tag you use **must** be the only word in the line, to be reco
- check-script
- and check the result. This tutorial shows how-to use [[https://github.com/pahaz/bashtest|bashtest]] to... number of python code lines in the files. We can use it like **./stat.sh <dir>** ==== Create testsuit
- quoting
- om the input stream and thus effectively ignored. Use it to beautify your code: <code> # escapestr_sed(