unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jesse Rosenthal <jrosenthal@jhu.edu>
To: Michal Sojka <sojkam1@fel.cvut.cz>, notmuch@notmuchmail.org
Subject: Re: Remote usage script updated
Date: Wed, 09 Feb 2011 16:13:13 -0500	[thread overview]
Message-ID: <m1k4h8syhi.fsf@watt.hwcampus.jhu.edu> (raw)
In-Reply-To: <87tygiowyi.fsf@wsheee.2x.cz>

Michal,

On Sun, 06 Feb 2011 00:58:29 +0100, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
> Hmm, this code worked well with dropbear ssh server but it seems that
> with openssh server the result is not that good. Namely, if the master
> connection is dead, the command running true blocked for a long time.

Seemed to work okay for me when I played around with it a bit (in
different circumstances, and with a confused laptop waking up from
hibernation). But I'll hold off on updating it till I can figure out the
most reliable way.

I'll definitely take your suggestion to use printf instead of manually
escaping characters. 

Thanks, in any event, for your suggestions!

By the way, I've also realized that most attachment downloading is done
not by "--format=raw" but by "notmuch part". It's possible to do caching
there as well. There are a few options there:

  * One option would be to just cache by the attachment number -- but
    this is very fragile if you delete an attachment through mutt or
    some other client that allows it.

  * cache by the hash of the attachment. The idea is that asking the
    server to fetch it, hash it, and send the hash would still save
    time over sending the whole attachment. Probably -- though most
    attachments are small enough and most connections are fast enough
    that this might not actually matter.

  * Actually stick the attachment hash in the json output in the first
    place. But this would be a lot of trouble for a small gain for
    very few.

It would come in handy when I'm trying to get a biggish pdf over a bus's
slow wireless connection. But it's certainly not a priority.

Best,
Jesse

  reply	other threads:[~2011-02-09 21:13 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
2011-02-05 23:58   ` Michal Sojka
2011-02-09 21:13     ` Jesse Rosenthal [this message]
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=m1k4h8syhi.fsf@watt.hwcampus.jhu.edu \
    --to=jrosenthal@jhu.edu \
    --cc=notmuch@notmuchmail.org \
    --cc=sojkam1@fel.cvut.cz \
    /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).