Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 1E79A431FD7 for ; Sun, 2 Nov 2014 06:55:15 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gya0LEW6tr1g for ; Sun, 2 Nov 2014 06:55:07 -0800 (PST) Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 5CA2A431FAF for ; Sun, 2 Nov 2014 06:55:07 -0800 (PST) Received: by mail-wg0-f46.google.com with SMTP id x13so9437426wgg.19 for ; Sun, 02 Nov 2014 06:55:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:subject:to:references:in-reply-to :user-agent:message-id:mime-version:content-type :content-transfer-encoding; bh=TcLOqP/0wx//znhrJeW8/cYRAwvTI4khGBgP0hiShGI=; b=KeGMZHHLxQP9KWDcaUPGf2yiMWttr+dB7GXhdBqJctbXeDYeAsQRmgQUtqiX0jYMhO swRwcYOWOGw/+4xLJar8r4m3s1DSTNSEjkQHJY0lPeBwjXI6DbqkvP8jBazhBmN8D2rM JCrbyILElKoTYXuIxLrQzbmL8N2bE/qqMySXf3GtTrHmHGT4MZ1S28gseQ4/zmv9yMBO pgG7RlQyBAh/eosMsnbJIN8qpofPi/o02hzmYg7s/SWAuHFN+mAgRZh2YQXwnrP4W+3S xMuwIcjoJiI1ButciQc+l4hnvi5rilfgaQgNi52qJszzOAB10VPM1vXAr9yYBdcI5bXa 23zg== X-Gm-Message-State: ALoCoQmV41dEKFN0skOmSAjSIUH3Obe8O4lO1ZDOZ2IKaX9w4OdVvFykgQGsfs102c/vqDkUTZEJ X-Received: by 10.180.9.103 with SMTP id y7mr10354792wia.5.1414940104709; Sun, 02 Nov 2014 06:55:04 -0800 (PST) Received: from localhost (216.89-20-249.enivest.net. [89.20.249.216]) by mx.google.com with ESMTPSA id cw6sm18881401wjb.18.2014.11.02.06.55.03 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 02 Nov 2014 06:55:03 -0800 (PST) Date: Sun, 02 Nov 2014 14:55:19 +0000 From: Gaute Hope Subject: [abunchoftags] =?iso-8859-1?Q?=FCberalpha=3A?= sync X-Keywords with notmuch tags To: notmuch@notmuchmail.org References: In-Reply-To: User-Agent: astroid/v2612f530 (https://github.com/gauteh/astroid) Message-Id: <1414939426-astroid-0-jvzqu7va0w-13521@strange> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2014 14:55:15 -0000 hi, there has been a lot of discussion about getting gmail label syncing with notmuch tags over time. one approach is to use the X-Keywords header t= hat offlineimap now supports (kept in sync with GMail labels). I believe this was originally developed by an at the time notmuch user. I haven't found any script or program that completes the link with the notmuch tags so I've set up a _very_ _experimental_ program that does this sync. It checks mtimes of files so that it only syncs files that have been changed (and detects files that notmuch new does not). It has not been in use much yet, but if anyone is interested it is located here: https://github.com/gauteh/abunchoftags have a look at the README.md. Including a small section on some of the pitfalls you might encounter because of the way I prefer to have things or because of logical mistakes that I may have made. Otherwise refer to the source code. At the end is a proposed way of doing a full sync as well as an example fetch_and_sync.sh script in the examples folder. Please don't use uncritically - it may definitely eat all your mail! This approach depends on _modifying_ and rewriting your email (tag-to-keyword sync, not the other way around). Hope it may be useful to someone, this is not a release of a finished program - but there will probably never be such a thing. It works for me, but doesn't necessarily for you. The examples depend on the lastmod patches [0]. Some rudimentary performance stats:=20 Running a full keyword-to-tag sync on a Macbook Pro with around 55k messages on an encfs volume took 1m48s and used about 108MB of memory. Running a full tag-to-keyword check on the same message base with 3 changed messages took about 1m5s and 100MB of memory. The subsequent scans of only changed files takes very little time. Cheers, Gaute [0] id:1413181203-1676-1-git-send-email-aclements@csail.mit.edu =