Recherche
Voici les résultats de votre recherche.
Résultats plein texte:
- redirection
- the file descriptors 0, 1 and 2, all connected to your terminal: ^Name^FD^Description^ |''stdin''|0|sta... to the same device, the **terminal** here. Check your preferred UNIX(r)-FAQ for details, I'm too lazy ... diagnostic- and error-messages on ''stderr''. If you write a script that outputs error messages, please make sure you follow this convention! Whenever you **name** su
- obsolete
- names of files in the current working directory. You can't get globbing without word-splitting, or vic... -f''). [[http://mywiki.wooledge.org/BashFAQ/050 | You can't store a command or character-delimited list... ing"; it's not, it's just a way to find the place you've //forgotten// to put error handling.\\ Think o... Perl or ''throws'' in C++: tough love that makes you write better code. Many guides recommend avoiding
- positional-parameters
- ====== ===== Intro ===== The day will come when you want to give arguments to your scripts. These arguments are known as **positional parameters**. Some r... The first argument ===== The very first argument you can access is referenced as ''$0''. It is usually... chos ''$0'': <code> #!/bin/bash echo "$0" </code> You see, ''$0'' is always set to the name the script
- quoting
- portant, as they influence the way Bash acts upon your input. There are three recognized types: * **p... ree forms have the very same purpose: **They give you general control over parsing, expansion and expan... ds (like interpreting ANSI-C escapes in a string) you'll meet below. :!: **ATTENTION** :!: The quote c... SAME AS ### command "my multiword argument" ### YOU NEED ### MYARG="my multiword argument" command "$
- check-script
- The one of the simplest way to check your bash/sh scripts is run it and check it output or run it and c... ub.com/pahaz/bashtest|bashtest]] tool for testing your scripts. https://wiki.bash-hackers.org/howto/testing-your-scripts ==== Write simple util ==== We have a ... t passed. </sxh> Thats all. We wrote one test. You can write more tests if you want. <code> $ ls te