Results 26 - 50 of about 100 results out of about 3363 pages. (0.13 seconds)
- CategoryCategory . . . 1 match
- ...## Please edit system and help pages ONLY in the master wiki!
## For more information, please see MoinMoin:MoinDev/Translation.
##master-page:Unknown-Page
##master-date:Unknown-Dat...
- BraceExpansion . . . 1 match
- .../Patterns#Brace_Expansion|Bash guide]]
* [[https://web.archive.org/web/20220408004618/https://wiki.bash-hackers.org/syntax/expansion/brace|Bash-hackers wiki]]
----
CategoryShell...
- BourneShell . . . 1 match
- ...e symbol (|). This was taken over from the predecessor, the Thompson shell, which is the reason why modern shells certainly never implemented it.
----
CategoryShell CategoryUnix...
- Bashism . . . 1 match
- ...[[http://www.etalabs.net/sh_tricks.html|Rich's sh tricks]] has some clever yet surprisingly powerful hacks for dealing with the limitations of the POSIX shell.
----
CategoryShell...
- BashWeaknesses . . . 1 match
- ...more attention than normal to every single good practice rule and uphold a consistent style throughout the entire code to avoid ''too'' much headache later on.
----
CategoryShell...
- BashToolbox . . . 1 match
- ...eue[0]}" || return
IFS= read -r -d '' <&"${_queue[0]}"
printf %s "$REPLY"
} # _____________________________________________________________________
}}}
----
CategoryShell...
- BashSyntaxReference . . . 1 match
- ...''var''`//`''search''`/`''replace''`}`||`x=${x//foo/bar}`||Expands to the value of ''var'' with all instances of ''search'' (a glob) replaced by ''replace''.||
----
CategoryShell...
- BashSheet . . . 1 match
- ...ut to standard error from now on to a log file'''.
* `echo "Fatal error occurred! Terminating!"; exit 1`
. '''Show an error message and exit the script'''.
----
CategoryShell...
- BashProgramming/06 . . . 1 match
- ... The second allows far more flexibility.
----
<- [[../05|Avoiding code injection]] | '''Data structures''' | [[../Ex01|Example 1: Modifying a config file]] ->
----
CategoryShell...
- BashProgramming . . . 1 match
- ...le:
{{{
foo() { ...; }
export -f foo
find . -type f -exec bash -c 'for f; do foo "$f"; done' x {} +
}}}
----
'''Basic concepts''' | [[/02|Tool selection]] ->
----
CategoryShell...
- BashPitfalls . . . 1 match
- ...oo}> file`, `> "$BASHPID"`, `< "${foo=bar}"`, or `(cmd1 & cmd2 & wait) > >(...)`.
Also see https://www.vidarholen.net/contents/blog/?p=865.
----
CategoryShell CategoryBashguide...
- BashParser . . . 1 match
- ...ts''). That means that `$name` is not safe from having its result cut up, because the cutting up happens after `$name` is replaced by the value within `name`.
----
CategoryShell...
- BashLoadableBuiltins . . . 1 match
- ...nd at:
* http://cfajohnson.com/shell/bash/loadables/
* https://web.archive.org/web/20160303032434/http://cfajohnson.com/shell/articles/dynamically-loadable/
----
CategoryShell...
- BashGuide . . . 1 match
- ...ntrol]]
* [[/Practices|Practices]]
* Choosing your shell; quoting; readability; debugging.
----
[[BashGuide/CommandsAndArguments|Commands and Arguments ->]]
----
CategoryShell...
- BashFAQ/111 . . . 1 match
- ...186&tbm=nws|Search Google News for 'CVE-2014-7186']]
* [[https://www.google.com/webhp?tbm=nws#q=CVE-2014-7187&tbm=nws|Search Google News for 'CVE-2014-7187']]
----
CategoryShell...
- BashFAQ/103 . . . 1 match
- ...e was not last modified in Januari 2010
$ inTime file 1945-2010 && echo "file was last modified after The War"
file was last modified after The War
}}}
----
CategoryShell...
- BashFAQ/101 . . . 1 match
- ...case $2 in
*[^0-9]*|'') :;;
*) st=$2;;
esac
warn "$1"
exit "$st"
}
}}}
Since it's your script, you get to decide how fancy you want to make it.
----
CategoryShell...
- BashFAQ/100 . . . 1 match
- ...retend [[BashFAQ/105|set -e]] and [[BashFAQ/112|set -u]] don't exist.
=== See Also ===
[[BashFAQ/073|Parameter expansion]] (terse version, with handy tables).
----
CategoryShell...
- BashFAQ/084 . . . 1 match
- ...e example of a recursive function.
fact() {
if (($1 <= 1)); then
r=1
else
fact "$(($1 - 1))"
((r *= $1))
fi
}
fact 11
echo "$r"
}}}
----
CategoryShell...
- BashFAQ/066 . . . 1 match
- ... [[ $var == !(!(foo)|!(bar)|!(more)) ]] && ...
}}}
But this is quite unclear and not much shorter than just writing out separate expressions for each pattern.
----
CategoryShell...
- BashFAQ/050 . . . 1 match
- ...rite out meaningful (possibly even date-stamped) lines describing what you're doing.
{{{
echo "Populating database table"
mysql -u me -p somedbname < file
}}}
----
CategoryShell...
- BashFAQ/049 . . . 1 match
- ...}}}
Every invocation of this gives the update to the file from where we stopped last. If you know the line number from where you want to start, set n to that.
----
CategoryShell...
- BashFAQ/048 . . . 1 match
- ... to populate variables indirectly '''with''' `eval`, please see [[BashFAQ/006#eval]].
* [[http://wiki.bash-hackers.org/commands/builtin/eval | More examples]]
----
CategoryShell...
- BashFAQ/047 . . . 1 match
- ...[http://wiki.bash-hackers.org/howto/redirection_tutorial|redirection tutorial]] (with an example that redirects stdout to one pipe and stderr to another pipe).
----
CategoryShell...
- BashFAQ/046 . . . 1 match
- ...peset -a '[colors]' bar
$ bar[blue]=test1
$ typeset -p bar
typeset -a '[colors]' bar=([blue]=test)
$ bar[orange]=test
ksh: colors: invalid value orange
}}}
----
CategoryShell...