From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 72E256DE13E7 for ; Tue, 16 Feb 2016 10:37:22 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.307 X-Spam-Level: X-Spam-Status: No, score=-0.307 tagged_above=-999 required=5 tests=[AWL=0.244, RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9y4C4l19xXc for ; Tue, 16 Feb 2016 10:37:20 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 1CDDE6DE0FC5 for ; Tue, 16 Feb 2016 10:37:19 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1aVkUF-0006iR-AH; Tue, 16 Feb 2016 13:36:35 -0500 Received: (nullmailer pid 10229 invoked by uid 1000); Tue, 16 Feb 2016 18:37:14 -0000 From: David Bremner To: "W. Trevor King" Cc: notmuch@notmuchmail.org Subject: Re: [PATCH] nmbug: Allow Unicode tags and IDs in Python 2 In-Reply-To: <20160216175641.GN4265@odin.tremily.us> References: <87lh6kvmbc.fsf@zancas.localnet> <20160216175641.GN4265@odin.tremily.us> User-Agent: Notmuch/0.21+5~gca076ce (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Tue, 16 Feb 2016 14:37:14 -0400 Message-ID: <87wpq4v6w5.fsf@tesseract.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 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: Tue, 16 Feb 2016 18:37:22 -0000 "W. Trevor King" writes: > >> At first I thought there might be problems with non-utf8 message-ids, >> but that turns out not to be the case [1]. It seems like it would take >> a fairly heroic effort to get non-UTF8 tags into the database (perhaps >> by calling the library interface with bad strings?) so we can probably >> ignore this case. It might be good to document the limitation though, >> since AFAIK, dump and restore can roundtrip any old crap. > > How about in a NEWS entry in v2 of this series, and then echoing that > NEWS entry in the notmuch-dtags (or whatever) man page once I work up > that series? Sure, sounds fine d