diff --git a/archive_crawler b/archive_crawler
index af36d18..2ccbc31 100644
--- a/archive_crawler
+++ b/archive_crawler
@@ -83,8 +83,9 @@ scrape_targets() {
# First, remove everything between the first line and 'name="sectok"'
# Next, remove everything after ''
# This should remove everything above and below our desired markdown
+# We also take the opportunity to convert some HTML chars
extract_markdown() {
- sed -e '1,/name="sectok"/d' -e '/<\/textarea>/,$d' "${1:-/dev/stdin}"
+ sed -e '1,/name="sectok"/d' -e '/<\/textarea>/,$d' -e 's/>/>/g' -e 's/</Attention: Since Bash 4 has been around for quite some time now (4.3 will come soon), I consider it to be "standard". This page is not maintained anymore and is left here to keep your links working. See the [[scripting:bashchanges]] page for new stuff introduced.
Besides many bugfixes since Bash 3.2, Bash 4 will bring some interesting new
features for shell users and scripters. See also [[scripting:bashchanges]] for a small general overview with more details.
@@ -15,11 +15,11 @@ feel free to write a chapter here.**
The complete list of fixes and changes is in the CHANGES or NEWS file of your
Bash 4 distribution.
-<WRAP center round download 60%>
+
The current available **stable** version is 4.4.18 release (February 03, 2018):
* ftp://ftp.cwru.edu/pub/bash/bash-4.4.18.tar.gz
* ftp://ftp.gnu.org/pub/gnu/bash/bash-4.4.18.tar.gz
-</WRAP>
+
@@ -50,10 +50,10 @@ See: [[commands:builtin:mapfile]]
The ''case'' construct understands two new action list terminators:
-The '';&'' terminator causes execution to continue with the next action list
+The '';&'' terminator causes execution to continue with the next action list
(rather than terminate the ''case'' construct).
-The '';;&'' terminator causes the ''case'' construct to test the next given
+The '';;&'' terminator causes the ''case'' construct to test the next given
pattern instead of terminating the whole execution.
See [[syntax:ccmd:case]]
@@ -124,15 +124,15 @@ See [[syntax:pe#case_modification | Case modification on parameter expansion]]
When using substring expansion on the positional parameters, a starting
index of 0 now causes $0 to be prepended to the list (if the positional parameters are used). Before, this expansion
started with $1:
-<code>
+
# this should display $0 on Bash v4, $1 on Bash v3
echo ${@:0:1}
-</code>
+
==== Globbing ====
There's a new shell option ''[[internals:shell_options#globstar | globstar]]''. When enabled, Bash will perform
-recursive globbing on ''<nowiki>**</nowiki>'' -- this means it matches all directories and files
+recursive globbing on ''**'' -- this means it matches all directories and files
from the current position in the filesystem, rather than only the current level.
The new shell option ''[[internals:shell_options#dirspell | dirspell]]'' enables spelling corrections on directory
@@ -145,23 +145,23 @@ See [[syntax:expansion:globs]]
Besides the classic method of integer indexed arrays, Bash 4 supports associative arrays.
An associative array is an array indexed by an arbitrary string, something like
-<code>
+
declare -A ASSOC
ASSOC[First]="first element"
ASSOC[Hello]="second element"
ASSOC[Peter Pan]="A weird guy"
-</code>
+
See [[syntax:arrays]]
===== Redirection =====
-There is a new ''<nowiki>&>></nowiki>'' redirection operator, which appends the standard output
-and standard error to the named file. This is the same as the good old ''<nowiki>>>FILE 2>&1</nowiki>''
+There is a new ''&>>'' redirection operator, which appends the standard output
+and standard error to the named file. This is the same as the good old ''>>FILE 2>&1''
notation.
-The parser now understands ''|&'' as a synonym for ''2>&1 |'', which redirects
+The parser now understands ''|&'' as a synonym for ''2>&1 |'', which redirects
the standard error for a command through a pipe.
See [[syntax:redirection]]
@@ -180,9 +180,9 @@ The mentioned shell options are **off by default** unless otherwise mentioned.
^Option ^Description ^
|''[[internals:shell_options#checkjobs | checkjobs]]'' | check for and report any running jobs at shell exit |
-|''[[internals:shell_options#compat31 | compat*]]'' | set compatiblity modes for older shell versions (influences regular expression matching in ''<nowiki>[[ ... ]]</nowiki>'' |
+|''[[internals:shell_options#compat31 | compat*]]'' | set compatiblity modes for older shell versions (influences regular expression matching in ''[[ ... ]]'' |
|''[[internals:shell_options#dirspell | dirspell]]'' | enables spelling corrections on directory names during globbing |
-|''[[internals:shell_options#globstar | globstar]]'' | enables recursive globbing with ''<nowiki>**</nowiki>'' |
+|''[[internals:shell_options#globstar | globstar]]'' | enables recursive globbing with ''**'' |
|''[[internals:shell_options#lastpipe | lastpipe]]'' | (4.2) to execute the last command in a pipeline in the current environment |
diff --git a/commands/builtin/caller.md b/commands/builtin/caller.md
index c341b19..3161a56 100644
--- a/commands/builtin/caller.md
+++ b/commands/builtin/caller.md
@@ -1,7 +1,7 @@
====== The caller builtin command ======
===== Synopsis =====
-<code>caller [FRAMENUMBER]</code>
+caller [FRAMENUMBER]
===== Description =====
The ''caller'' builtin command is used to print execution frames of subroutine calls. Without giving a framenumber, the topmost execution frame information is printed ("who called me") wile linenumber and filename.
@@ -18,7 +18,7 @@ This way, you can print a "stack trace" for debugging or logging purpo
The code is made very simple, just to show the basic purposes.
-<code bash>
+
#!/bin/bash
die() {
@@ -35,19 +35,19 @@ f2() { f1; }
f3() { f2; }
f3
-</code>
+
**Output**
-<code>
+
12 f1 ./callertest.sh
13 f2 ./callertest.sh
14 f3 ./callertest.sh
16 main ./callertest.sh
*** an error occured ***
-</code>
+
===== Notes =====
- * ''caller'' produces no output unless used within a script that's run from a real file. It isn't particularly useful for interactive use, but can be used to create a decent ''die'' function to track down errors in moderately complex scripts. <code>{ bash /dev/stdin; } <<<$'f(){ g; }\ng(){ h; }\nh(){ while caller $((n++)); do :; done; }\nf'</code>
+ * ''caller'' produces no output unless used within a script that's run from a real file. It isn't particularly useful for interactive use, but can be used to create a decent ''die'' function to track down errors in moderately complex scripts. { bash /dev/stdin; } <<<$'f(){ g; }\ng(){ h; }\nh(){ while caller $((n++)); do :; done; }\nf'
* For more sophisticated debugging, Bash extended debugging features are available and a number of special parameters that give more detail than caller (e.g. BASH_ARG{C,V}). Tools such as [[ http://bashdb.sourceforge.net/|Bashdb ]] can assist in using some of Bash's more advanced debug features.
* The Bash manpage and help text specifies that the argument to ''caller'' is an "expr" (whatever that means). Only an integer is actually allowed, with no special interpretation of an "expression" as far as we can tell.
diff --git a/commands/builtin/continuebreak.md b/commands/builtin/continuebreak.md
index 4597dde..8eaf805 100644
--- a/commands/builtin/continuebreak.md
+++ b/commands/builtin/continuebreak.md
@@ -1,7 +1,7 @@
-
+
You don't have an account yet? Just get one: Register