can use it. Disconnecting master all future attempts to connect
from the script will fail.
+It is possible to use this solution without any changes to
+`$HOME/.ssh/config`.
+
At the end of this document there is information for some possible ways
how master ssh connection can be done.
#!/bin/bash
- set -eu
+ set -euf
+
# To trace execution, uncomment next line:
- #BASH_XTRACEFD=6; exec 6>>remote-errors; echo -- >&6; set -x
+ #exec 6>>remote-errors; BASH_XTRACEFD=6; echo -- >&6; set -x
: ${REMOTE_NOTMUCH_SSHCTRL_SOCK:=master-notmuch@remote:22}
: ${REMOTE_NOTMUCH_COMMAND:=notmuch}
(*) general most likely being ~/.emacs
+### Yet another possibility -- script to start emacs
+
+Instead of adding new configurations you could also write a special
+script which starts and configures emacs suitable for remote usage.
+Copy the following "template" to a new name e.g. in `$HOME/bin/`,
+edit the value for `master-USER@HOST3:22` and perhaps add more
+post eval-after-load notmuch configs there.
+
+ #!/bin/sh
+ :; exec "${EMACS:-emacs}" --debug-init --load "$0" "$@"; exit
+
+ (setenv "REMOTE_NOTMUCH_SSHCTRL_SOCK" "master-USER@HOST3:22")
+
+ (eval-after-load "notmuch"
+ (lambda ()
+ (setq notmuch-command (concat (file-name-directory load-file-name)
+ "remote-notmuch.sh"))
+ ;; place for more post-notmuch-load emacs configs if any
+ ))
+ (notmuch)
+
+ ;; Local Variables:
+ ;; mode: emacs-lisp
+ ;; End:
+
## Creating master connection
**(Note: all the examples below use the default master socket written in**
from command line and observe output. If it looks as it should be next uncomment
the line
- #BASH_XTRACEFD=6; exec 6>>remote-errors; echo -- >&6; set -x
+ #exec 6>>remote-errors; BASH_XTRACEFD=6; echo -- >&6; set -x
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