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 BBE23431FBD for ; Sun, 26 Feb 2012 08:41:25 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.524 X-Spam-Level: X-Spam-Status: No, score=-0.524 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, URIBL_RHS_DOB=0.276] 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 zSq88S2nkDuj for ; Sun, 26 Feb 2012 08:41:19 -0800 (PST) Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 1E8FA431FBC for ; Sun, 26 Feb 2012 08:41:18 -0800 (PST) Received: by eekb47 with SMTP id b47so1185737eek.26 for ; Sun, 26 Feb 2012 08:41:15 -0800 (PST) Received-SPF: pass (google.com: domain of daniel@schoepe.org designates 10.14.202.197 as permitted sender) client-ip=10.14.202.197; Authentication-Results: mr.google.com; spf=pass (google.com: domain of daniel@schoepe.org designates 10.14.202.197 as permitted sender) smtp.mail=daniel@schoepe.org; dkim=pass header.i=daniel@schoepe.org Received: from mr.google.com ([10.14.202.197]) by 10.14.202.197 with SMTP id d45mr5889722eeo.128.1330274475097 (num_hops = 1); Sun, 26 Feb 2012 08:41:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=schoepe.org; s=google; h=from:to:subject:in-reply-to:references:user-agent:date:message-id :mime-version:content-type; bh=iXyPdN+spSXZzrv9y1qeqCjjeJb7yYMwYrZvme7Zn4c=; b=d9Nrgdsb3hn/2ViDH+dXabDxAkPZkrvh8+GsnRqDge20RsFv9AUu8nNuDw9r9HNv9L xUVfwLQRzOjXxTqpqRdyTzm7FkDJ6wukYxzQUElLrGl1k8g+anYrAacqIxzVxfHk5mim wtbfn3HicuvoubTHgNLHMtdKSAnGD9CamUtFQ= Received: by 10.14.202.197 with SMTP id d45mr4467117eeo.128.1330274474928; Sun, 26 Feb 2012 08:41:14 -0800 (PST) Received: from localhost (p4FC797DD.dip0.t-ipconnect.de. [79.199.151.221]) by mx.google.com with ESMTPS id i10sm6977446eea.8.2012.02.26.08.41.12 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 26 Feb 2012 08:41:13 -0800 (PST) From: Daniel Schoepe To: Patrick Totzke , Daniel , notmuch@notmuchmail.org Subject: Re: Replacing my name/email with "me" (or similar) in author lists In-Reply-To: <20120226112210.5422.8471@brick.lan> References: <20120226112210.5422.8471@brick.lan> User-Agent: Notmuch/0.11.1+210~ge886eec (http://notmuchmail.org) Emacs/24.0.93.1 (x86_64-pc-linux-gnu) Date: Sun, 26 Feb 2012 17:41:04 +0100 Message-ID: <87ehthfsyn.fsf@schoepe.localhost> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Gm-Message-State: ALoCoQkWg/h/8xVJLmekM16WqkU2BvHhr5TCKcyfMWdd+Sc4hfKJdbGb0BILBZOUba9SIObOyrXC 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, 26 Feb 2012 16:41:25 -0000 --=-=-= Content-Type: text/plain On Sun, 26 Feb 2012 11:22:10 +0000, Patrick Totzke wrote: > > so it would seem more appropriate that this be done in the backend. > I agree. I personally think this is a nice feature to have in all > user interfaces to notmuch and therefore it makes sense to implement it once > in the lib. Also because ~/.notmuch-config already contains a list of my addresses > and therefore should have all information needed. I'm not sure if that's a good idea: A frontend might want to make this configurable, for example to give the user the opportunity to disable it (possibly to see to which of his mail adresses he used in that thread, if they have different real name components). It might also get tricky to distinguish between someone called "me" participating in the thread and the user, which might be relevant for highlighting the latter case differently, while it's rather easy for a frontend to do the transformation itself. At least it should not be done in the library, because it'd need to read the user's addresses from configuration file which the library is not supposed to access, as far as I understand. Cheers, Daniel --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJPSmCgAAoJEIaTAtce+Z+JFxAP/igWrrnW2Q5072cYepFDlVuV Ia8yLUEXzEfl6TuKewRDl8S8cJ6VhlixnJUlgegYokcepwFPM0+ztlYh78DjqSuc uifiQZwPRwTcbz6bbZ/GLuuQjyKrUsvYeXLqwfc50H+WRgKDO+AoT7fDDXwMiHmt JrOvjZ+qqlPc1+NNoiFa8LlUQ5+sMi+Pm06b+6VgWdCshIfOnvMFXRXI4slV7h6V M+HbEnIgdlco73/WVx5U2OYjb3s2rf+JZegvGjQWdncGEm6ZpBHc16RtJmeEZYMD LDKwL+NSqraSPsxUichS9HtaSLqQSRmxa83VH7jCTiFQYjyGGPl0HTZYJjXl+Fqf sS4oRgoGSlK+vJeqarQv6LJTvagjjszxdiNjxgbRmtL+/PE++BmKhj2I/UA+ZMRO UuWg02n1rjPlfny0wx86YVsBB8XhLRZR1MCfW51Zjh4mjwGZHmUFBKR40qcNyKWu Cz0XUQxPilIAI1W2m9VZh60LXtxWzFl6IiIje+hfkm0D5pIoGni2W9CYVyqDscGz hwt7YBgpo0rvMnwIwi9kZm+wjCCtUT9YwuSnzPc9yCSngqnKDXd28fAEg+aHW1Dj OfAho9yiZgzE25WXTHKZ3MadUvKXcTrq4Jpz+Lk1EnjyJp5so5dV+WZ/mR8zrdVA cVipzHNr7vlgufzgWpm9 =dvYN -----END PGP SIGNATURE----- --=-=-=--