Recherche

Résultats plein texte:

obsolete

32 Occurrences trouvées, Dernière modification : il y a 18 mois

solete and deprecated syntax ====== https://wiki.bash-hackers.org/scripting/obsolete This (incomple... his first table lists syntax that is tolerated by Bash but has few if any legitimate uses. These feature... kward compatibility with obsolete shells, or were Bash-specific features considered failed experiments a... n. See: [[syntax:redirection | redirection]]<code bash> $ { bash; dash </dev/fd/0; } <<<'echo foo>/dev/n

quoting

13 Occurrences trouvées, Dernière modification : il y a 18 mois

====== Quotes and escaping ====== https://wiki.bash-hackers.org/syntax/quoting {{keywords>bash shell scripting quoting quotes escape backslash marks singl... escaping are important, as they influence the way Bash acts upon your input. There are three recognized ... eneral, a character that has a special meaning to Bash, like the dollar-sign (''$'') can be masked to no

positional-parameters

8 Occurrences trouvées, Dernière modification : il y a 18 mois

estscript__ - it just echos ''$0'': <code> #!/bin/bash echo "$0" </code> You see, ''$0'' is always set t... isn't true for login shells: <code> > echo "$0" -bash </code> In other terms, ''$0'' is not a position... y is to access specific parameters: <code> #!/bin/bash echo "Total number of arguments: $#" echo "Argume... echo "${@: -1}" </code> __**Attention**__: As of Bash 4, a ''START'' of ''0'' includes the special para

redirection

4 Occurrences trouvées, Dernière modification : il y a 18 mois

ve 9, since you may collide with file descriptors Bash uses internally. ===== Redirecting output ===... uivalent** to <code> > TARGET 2>&1 </code> Since Bash4, there's ''&<nowiki>>>TARGET</nowiki>'', which i... n is unknown, but it seems to be done on purpose. Bash 4 introduced a warning message when end-of-file i... '', to hide it), this is **the wrong way**: <code bash> # { echo OUTPUT; echo ERRORS >&2; } is to simula

check-script

3 Occurrences trouvées, Dernière modification : il y a 18 mois

The one of the simplest way to check your bash/sh scripts is run it and check it output or run it and ch... st]] tool for testing your scripts. https://wiki.bash-hackers.org/howto/testing-your-scripts ==== Writ... sh; title: simple stat.sh script> #!/usr/bin/env bash if [ -z "$1" ] then DIR=./ else DIR=$1 f

flac2mp3

1 Occurrences trouvées, Dernière modification : il y a 18 mois

####### # flac2mp3.sh Version2 ########## #!/bin/bash for FILE in *.flac; do ffmpeg -i "$FILE" -ab