added #EOF to help noticing eos (helped to eat my own dogfood again)

[notmuch-wiki] / remoteusage / aboriginal.mdwn

diff --git a/remoteusage/aboriginal.mdwn b/remoteusage/aboriginal.mdwn
index 8f4aa724d59933290cf089699c40f012bda4d09c..3d012b8eed684b115b2f2adc9b5820ff52d7831e 100644 (file)
--- a/remoteusage/aboriginal.mdwn
+++ b/remoteusage/aboriginal.mdwn
@@ -23,8 +23,8 @@ Write the following code to a file, for example `remote-notmuch.sh`.
        # http://notmuchmail.org/remoteusage/aboriginal/
 
        set -eu
        # http://notmuchmail.org/remoteusage/aboriginal/
 
        set -eu

-       # To trace execution, outcomment next line. Note that emacs input may ...
-       #exec 2>>remote-errors; echo -- >&2; set -x # ... change (no stderr).
+       # To trace execution, uncomment next line.
+       #BASH_XTRACEFD=6; exec 6>>remote-errors; echo -- >&6; set -x

 
        readonly SSH_CONTROL_SOCK='~'/.ssh/master-user@host:22
 
 
        readonly SSH_CONTROL_SOCK='~'/.ssh/master-user@host:22
 


@@ -57,6 +57,7 @@ Write the following code to a file, for example `remote-notmuch.sh`.
        fi
 
        echo " See`sed '1d;2d;s/.//;q' "$0"` for help."
        fi
 
        echo " See`sed '1d;2d;s/.//;q' "$0"` for help."

+       #EOF

 
 Note the `0.1` in ssh command line. It is used to avoid any opportunistic
 behaviour ssh might do; for example if control socket is not alive ssh
 
 Note the `0.1` in ssh command line. It is used to avoid any opportunistic
 behaviour ssh might do; for example if control socket is not alive ssh


@@ -147,10 +148,8 @@ run
 from command line and observe output. If it looks as it should be next uncomment
 the line
 
 from command line and observe output. If it looks as it should be next uncomment
 the line
 

-        #exec 2>>remote-errors; echo -- >&2; set -x # ... change (no stderr).
+        #BASH_XTRACEFD=6; exec 6>>remote-errors; echo -- >&6; set -x

 
 

-in `./remote-notmuch.sh` and attemt to use it from emacs again -- and then
+in `./remote-notmuch.sh` and attempt to use it from emacs again -- and then

 examine the contents of `remote-errors` in the working directory emacs was
 examine the contents of `remote-errors` in the working directory emacs was

-started. Emacs behaviour may alter slightly as all stderr goes to remote-errors
-now to take that into account when examining results (and if it fixes everything
-then start forwarding stderr to /dev/null...).
+started.