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 2542F429E28 for ; Tue, 30 Aug 2011 15:24:52 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 ckfzht9IZz42 for ; Tue, 30 Aug 2011 15:24:51 -0700 (PDT) Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by olra.theworths.org (Postfix) with ESMTP id C0EA7429E27 for ; Tue, 30 Aug 2011 15:24:51 -0700 (PDT) Received: from [192.168.13.75] (lair.fifthhorseman.net [216.254.116.241]) by che.mayfirst.org (Postfix) with ESMTPSA id 29538F970 for ; Tue, 30 Aug 2011 18:24:49 -0400 (EDT) Message-ID: <4E5D6336.7010708@fifthhorseman.net> Date: Tue, 30 Aug 2011 18:24:54 -0400 From: Daniel Kahn Gillmor User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20110807 Icedove/5.0 MIME-Version: 1.0 To: notmuch@notmuchmail.org Subject: Re: How does notmuch detect the presence of attachments? References: <4E565A61.7040600@fifthhorseman.net> <20110830062229.GC8590@lemote.jasonwoof.com> <4E5D5B7D.7050104@fifthhorseman.net> <87bov61rri.fsf@servo.factory.finestructure.net> In-Reply-To: <87bov61rri.fsf@servo.factory.finestructure.net> X-Enigmail-Version: 1.2.1 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigAAF9B294AB8CC8F1EA6279CA" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: notmuch List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2011 22:24:52 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigAAF9B294AB8CC8F1EA6279CA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 08/30/2011 06:03 PM, Jameson Graef Rollins wrote: > And we need something like: >=20 > jpg2thousandwords heh. Yes, i suspect there will be some mime types we will be unable to index in detail with xapian in the foreseeable future. Even without that, though, there's the possibility to store textual comments in a jpeg; a user of notmuch could choose to feed those comments to the xapian indexer= =2E For example: 0 dkg@pip:~/src/fence$ exiv2 -p c in-play.jpg a 2-player game of FENCE! 0 dkg@pip:~/src/fence$ I don't know if this would be useful in the real world, though, since most people probably don't put comment data in their jpegs. You can easily stuff a thousand words into a jpeg though: exiv2 modify -c "$(head -n 1000 < /usr/share/dict/words)" test.jpg proverbially yours, --dkg --------------enigAAF9B294AB8CC8F1EA6279CA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQJ8BAEBCgBmBQJOXWM2XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznp4XgP/01Sd2d5h7tTWyvEgAhxgDef 1EnNnJbvny9k6js8Ed/aG5hsu1OWRwQx0ZXpsld/yQYXzeokUAB9cJ5eaTe+B6wI nXbWDYMx+YMyu6T1f6XvstXjdivOXkKr0B0gFCQpwNnej8VKfov0MXLd9cgaqk7J cK4V7L6U01KShAp/Y1lzOvldyWFis67/kXBr7+KVf7nEZ68RngeXnBygkpNUsp3U nmvUjkCWH0GGeu90Hzg5WfgUKKgUM/aOs7JFWz1YliDxU7sfx2Y06/4KKyuf62QZ 4GXxKHxyI9AnnkwqzuDMya/iwjxhLSj7wOApZ+PyNG5Qs+m+4lQUo8lgyWJAfzne eaeGUzJGWaUllmZurm5NDz+t0LBuWk2SIW30ccEWaQafWmddTv+5FvnzdeH3YR/g fEWW63iPfD1X+UHku3/ele87NoR1Lx0Wr+VebWmZ1hqQtfjW/aMbwzh2aqHplufc fmoeh39T4rvcewkhDC/ZYyKN+NnMI5hj4BiaNQ6YLKEZtxOH0JReyDtrUO9SEOlC ImAE6K9L/7cxu1yjWxQlCbQvwlEbz/ATj7LWnHY2TTbpFRXj7mK5mDiIftHD7JEZ PBUQ0yRU73vMYuDscDmg+pOlhvW5tG0A7d3udcOmqvq0ILqYv3NvUGBnd8r5+Gsd NrjqJ1B1klTUnTVwSwsq =Ew0j -----END PGP SIGNATURE----- --------------enigAAF9B294AB8CC8F1EA6279CA--