From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 1ADED431FDA for ; Thu, 28 Jan 2010 15:30:27 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.866 X-Spam-Level: X-Spam-Status: No, score=-0.866 tagged_above=-999 required=5 tests=[AWL=-0.867, BAYES_50=0.001] autolearn=ham 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 vscTmJD9Ifqt for ; Thu, 28 Jan 2010 15:30:26 -0800 (PST) Received: from mail-yx0-f200.google.com (mail-yx0-f200.google.com [209.85.210.200]) by olra.theworths.org (Postfix) with ESMTP id 22F1E431FD5 for ; Thu, 28 Jan 2010 15:30:26 -0800 (PST) Received: by yxe38 with SMTP id 38so1254886yxe.6 for ; Thu, 28 Jan 2010 15:30:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:subject:from:to :in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=A+pqBrMHNGZP1qwrF3AiyMp8/0i8OC0agF14SK0evws=; b=WhJg3FGBtaABDH6BAWYT8aSyvQtlcwwcV7F79XXM4QEUwWnwjrJWUI/pE+4EHeeNz9 eLkUfuA1ElGjbZdc2fU5lJ9GVuhHeo7uHUhRYx4en5yN37CYYaWwRYAVMGwyKmYSF+nW 6k63hL6kaTopH000asslyX1zqaOMH4XHteRdQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:subject:from:to:in-reply-to:references:date:message-id :user-agent:content-transfer-encoding; b=L16sdvkwgRW8dUatELTIzKk+PFhNUOs09fvf1/aHzL8q4eSKrkDI2FxH5jz7/L9M84 Z8dy58EAEBeXVE5FqSSc0WTp7j/CiiqMDID1ZW/AsDg2jO3MiGyZ8UxN9i1gkau3xeVS RkkO9/XoBz643/UzGcE0evG/giCCai7h2t0Js= Received: by 10.150.55.17 with SMTP id d17mr637080yba.155.1264721419428; Thu, 28 Jan 2010 15:30:19 -0800 (PST) Received: from localhost (umass-959-98.wireless.umass.edu [128.119.77.98]) by mx.google.com with ESMTPS id 7sm501333yxg.14.2010.01.28.15.30.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 Jan 2010 15:30:18 -0800 (PST) Content-Type: text/plain; charset=UTF-8 From: Ben Gamari To: martin f krafft , notmuch In-reply-to: <20100128221735.GE8942@lapse.rw.madduck.net> References: <20100125162247.85F0F66FA8@aether.pioto.org> <87tyu9dfhs.fsf@servo.finestructure.net> <20100128051057.GA12540@lapse.rw.madduck.net> <20100128203910.GC5237@lapse.rw.madduck.net> <1264711745-sup-8326@ben-laptop> <20100128211120.GA8942@lapse.rw.madduck.net> <1264713802-sup-620@ben-laptop> <20100128221735.GE8942@lapse.rw.madduck.net> Date: Thu, 28 Jan 2010 18:30:16 -0500 Message-Id: <1264719647-sup-9540@ben-laptop> User-Agent: Sup/git Content-Transfer-Encoding: 8bit Subject: Re: tag dir proposal [was: Re: Git as notmuch object store] 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: Thu, 28 Jan 2010 23:30:27 -0000 Excerpts from martin f krafft's message of Thu Jan 28 17:17:35 -0500 2010: > Cron-scheduling is a regular activity. I am talking about > event-based scheduling. incron could do that and fire up a process > every time a message is dropped into a directory, but notmuch > doesn't provide me with an interface to say "you don't have to > iterate the Maildir yourself since I know exactly what changed: just > update your catalog with the new message in file foo/bar.msg". Fair enough. After reading your arguments I think I might have initially misunderstood you. I would actually tend to agree. Passing paths to notmuch does seem to be a reasonable approach. > > To me, notmuch-new is not Unix-y. To me, > > find $MAILDIR -type f -print0 | xargs -0 notmuch-update > > is Unix-y. ;) > I think it really depends upon what you are doing. I can certainly see when you might be want to simply have notmuch synchronize the index against the mail store. However, it seems the majority of the time one simply desires to add a message to the index (i.e. after delivery). Therefore, it seems like there is a place for both commands. > > In my configuration, I simply have a bash script in ~/.bin that simply > > runs offlineimap followed by notmuch new. This works quite nicely. > > This is essentially the same situation as with slocate, which has to > be run from cron currently, and hence gets outdated regularly. > Compare this to a hypothetical filesystem that exposed an index of > filenames (or content even!) to user-space, which could be used to > quickly search for files in real-time without the need to run > regular updates. I know other operating systems that have this > functionality already. > > Anyway, this is going off on a tangent, I feel. > That might be true but that certainly won't stop. ;) One would think that it wouldn't be difficult to teach slocate about inotify. I briefly looked into this and found rlocate but quickly realized that it requires its own kernel module. Apparently this has been investigated[1] and the inotify watch count limit becomes an issue very quickly. I seem to recall, however, that there were some whispers on the LKML about adding an interface that would be more capable of supporting such a system. I can't seem to recall the details, however, and homework beckons. Cheers, - Ben