Recherche
Voici les résultats de votre recherche.
Résultats plein texte:
- truecolor
- ndicates truecolor is supported. <code bash> $ (echo -e '\e[48:2:1:2:3m\eP$qm\e\\' ; xxd) ^[P1$r48:2:
- scripting
- ntation level: <code> case $input in hello) echo "You said hello" ;; bye) echo "You said bye" if foo; then bar fi ;; *) echo "You said something weird..." ;; esac </code> ... var/adm/ for file in "$MY_LOG_DIRECTORY"/*; do echo "Found Logfile: $file" done </code> ==== Variable
- obselete
- ion]]<code bash> $ { bash; dash </dev/fd/0; } <<<'echo foo>/dev/null&>/dev/fd/2 echo bar' foo echo bar bar</code>| |''$[EXPRESSION]'' |''<nowiki>$((EXPRESSION))</nowiki>'' |This undocume
- color
- indicates truecolor is supported. <code bash> $ (echo -e '\e[48:2:1:2:3m\eP$qm\e\\' ; xxd) ^[P1$r48:2:
- behaviours
- `$FCEDIT' and `$EDITOR'. 41. When the `xpg_echo' option is enabled, Bash does not attempt to interpret any arguments to `echo' as options. Each argument is displayed, af... set. 2. As noted above, Bash requires the `xpg_echo' option to be enabled for the `echo' builtin to be fully conformant. Bash can be configured to b
- basics
- f that file, for example: <code bash> #!/bin/bash echo "Hello world..." </code> This is interpreted by t... the file! You can follow the process by using ''echo'' as a fake interpreter: <code> #!/bin/echo </code> We don't need a script body here, as the file will never be interpreted and executed by "''echo''". You can see what the Operating System does, i