Recherche
Voici les résultats de votre recherche.
Résultats plein texte:
- obsolete
- Bourne, csh, or some other backward compatibility with obsolete shells, or were Bash-specific features c... red failed experiments and deprecated or replaced with a better alternative. These should be irrelevant ... nt version of POSIX, and some may be incompatible with POSIX. ^ Syntax ^ Replacement ^ Description... ey also introduce parsing ambiguity, and conflict with POSIX. Shells without this feature treat ''cmd1 &
- quoting
- ing a backslash: ''\$stuff'' * **weak quoting** with double-quotes: ''"stuff"'' * **strong quoting** with single-quotes: ''<nowiki>'stuff'</nowiki>'' All ... ("weak quoting") occurs, there are 2 ways to deal with it * if the baskslash is followed by a characte... sh variants including dash, (except busybox built with "bash compatibility" features). ===== I18N/L10N =
- redirection
- and comes from. It's a mighty tool that, together with pipelines, makes the shell powerful. The redirect... g file descriptors above 9, since you may collide with file descriptors Bash uses internally. ===== ... iting starts. If the option ''noclobber'' is set with [[commands:builtin:set | the set builtin]], with cause the redirection to fail, when ''TARGET'' names a
- positional-parameters
- '' is always set to the name the script is called with (''>'' is the prompt...): <code> > ./testscript ... ional parameters are numbered in reverse starting with the last one. ''COUNT'' may not be negative, i.e... l Parameters ===== Setting positional parameters with command line arguments, is not the only way to se... e=1" # because if you're debugging the script with "bash -x" code like this: # # if [ "$ver