From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Jesse Rosenthal <jrosenthal@jhu.edu>, notmuch@notmuchmail.org
Subject: Re: Remote usage script updated
Date: Sat, 05 Feb 2011 08:38:33 +0100 [thread overview]
Message-ID: <87aaibylqe.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <87oc72xs35.fsf@lucky.home>
On Thu, 27 Jan 2011, Jesse Rosenthal wrote:
> Dear all,
>
> Just a note to say that I finally got around to updating the remote
> usage script on the wiki to what I'm using now. With "--format=raw" in,
> it's all pretty straightforward.
Hi Jesse,
thanks for this. I wanted to do this since the --format=raw was merged,
but didn't find the time for it. I have a few comments:
> The only things the script does now are:
>
> 1. Produces a slight pause in the "notmuch show" output to avoid that
> weird bug where emacs leaves off every tenth message or so.
I added a comment to the script to explain the sleep there. Otherwise,
people may delete the command because they think it is not needed.
> 2. Locally caches raw messages (i.e. when --format=raw) is called. This
> usually happens when getting attachments, so this is a nice way to
> avoid having to download large attachments repeatedly.
This is a good idea.
> Note this just caches based on msg-id (or a hash thereof, to avoid
> strange characters in file names). That means that if an attachment
> is deleted on the server, the cache will be out of date. An easy way
> to fix this would be to make the cache file name a concatenation of
> the msg-id hash (check that first) and the hash of the actual message
> (check that if the msg-id hash is there). I might put this in in the
> future, especially if anyone else is using the script.
>
> 3. Escapes dollar signs in the msg-id to make shell-quoting over ssh
> work.
I think that quoting with
printf -v args "%q " "$@"
instead of sed would work more reliably (see bash(1)).
> I've actually switched over to keeping my messages on my IMAP server and
> using this remote script on all of my computers. It avoids any need for
> syncing. It's been working very well for me so far.
>
> A future feature might be to integrate the ControlMaster feature of
> openssh into the script, instead of having to open a connection
> manually, but there are some complications there (dead sockets still
> around if you go offline, etc.).
In another project I worked around the dead sockets this way:
sshgw() {
local socket="$HOME/.ssh/cangw-connection"
if [[ ! -S $socket ]] || ! ssh -x -a -S $socket root@192.168.2.3 true; then
# Create master connection to speed up subsequent commands.
ssh -N -f -M -S $socket root@192.168.2.3 >/dev/null 2>&1
fi
ssh -x -a -S $socket root@192.168.2.3 "$@"
}
I guess this should work even for notmuch.
-Michal
next prev parent reply other threads:[~2011-02-05 7:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 15:51 Remote usage script updated Jesse Rosenthal
2011-01-28 2:54 ` Carl Worth
2011-01-28 20:10 ` Jesse Rosenthal
2011-02-05 7:38 ` Michal Sojka [this message]
2011-02-05 23:58 ` Michal Sojka
2011-02-09 21:13 ` Jesse Rosenthal
2011-02-11 6:55 ` Michal Sojka
2011-02-15 21:42 ` Michal Sojka
2011-03-03 16:38 ` Kristoffer Ström
2011-03-04 20:38 ` Jesse Rosenthal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87aaibylqe.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=jrosenthal@jhu.edu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).