1 Return-Path: <patricktotzke@googlemail.com>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id BE4DA429E25
\r
6 for <notmuch@notmuchmail.org>; Sat, 21 May 2011 11:50:47 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
\r
13 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id qup1PLzQy4Ee for <notmuch@notmuchmail.org>;
\r
17 Sat, 21 May 2011 11:50:46 -0700 (PDT)
\r
18 Received: from mail-ww0-f45.google.com (mail-ww0-f45.google.com
\r
19 [74.125.82.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client
\r
20 certificate requested) by olra.theworths.org (Postfix) with ESMTPS id
\r
21 788D8431FD0 for <notmuch@notmuchmail.org>; Sat, 21 May 2011 11:50:46 -0700
\r
23 Received: by wwi36 with SMTP id 36so4097340wwi.2
\r
24 for <notmuch@notmuchmail.org>; Sat, 21 May 2011 11:50:45 -0700 (PDT)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
\r
26 d=googlemail.com; s=gamma;
\r
27 h=domainkey-signature:date:from:to:subject:message-id:references
\r
28 :mime-version:content-type:content-disposition:in-reply-to
\r
29 :user-agent; bh=JlgFlgo0KVukxAmHnGNGEGcLcKSg09GfC2QmwtF11j8=;
\r
30 b=s1RRK8NTRLUNefWr9fKfHjC9/b9C3iT1RpxuNQ/krp0wF0czdekQ/vGw7Hfu//ry9y
\r
31 Tk6Y+9hIDoRPC7si/O/Q0izkvulEe83RiZpFuogwBtxoJE4qu+nIfNWcA3Jg0wVL2psu
\r
32 3SFXeznwys3a3V35NudN6anectzslscNGKiR4=
\r
33 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
\r
34 h=date:from:to:subject:message-id:references:mime-version
\r
35 :content-type:content-disposition:in-reply-to:user-agent;
\r
36 b=fty3b022d66XD1zoX4/FtFgd2pc33xLm2JN42YuWRMiUk9qLcZIHpNfB5QAn1cfmjb
\r
37 w+ccuuNAAXEDJsUnOJ4VvgE98QtrroiGNRUH2sGOI6yVxcbnQ7/A7OvEAyT8cz+g/6Nc
\r
38 nkSpKPxk0sNs7UEoKpBEONOuZHiq8yR+8YFAQ=
\r
39 Received: by 10.216.240.12 with SMTP id d12mr790317wer.8.1306003843449;
\r
40 Sat, 21 May 2011 11:50:43 -0700 (PDT)
\r
41 Received: from brick (cpc1-sgyl2-0-0-cust47.sgyl.cable.virginmedia.com
\r
43 by mx.google.com with ESMTPS id k76sm2437092wej.43.2011.05.21.11.50.41
\r
44 (version=TLSv1/SSLv3 cipher=OTHER);
\r
45 Sat, 21 May 2011 11:50:42 -0700 (PDT)
\r
46 Date: Sat, 21 May 2011 19:50:37 +0100
\r
47 From: Patrick Totzke <patricktotzke@googlemail.com>
\r
48 To: notmuch@notmuchmail.org
\r
49 Subject: Re: a python terminal gui?
\r
50 Message-ID: <20110521185037.GA13447@brick>
\r
51 References: <1305888097-sup-2343@optimusprime>
\r
52 <87pqndoww8.fsf@yoom.home.cworth.org>
\r
54 Content-Type: multipart/signed; micalg=pgp-sha1;
\r
55 protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj"
\r
56 Content-Disposition: inline
\r
57 In-Reply-To: <87pqndoww8.fsf@yoom.home.cworth.org>
\r
59 X-Mailman-Approved-At: Sat, 21 May 2011 22:53:56 -0700
\r
60 X-BeenThere: notmuch@notmuchmail.org
\r
61 X-Mailman-Version: 2.1.13
\r
63 List-Id: "Use and development of the notmuch mail system."
\r
64 <notmuch.notmuchmail.org>
\r
65 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
66 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
67 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
68 List-Post: <mailto:notmuch@notmuchmail.org>
\r
69 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
70 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
71 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
72 X-List-Received-Date: Sat, 21 May 2011 18:50:47 -0000
\r
76 Content-Type: text/plain; charset=us-ascii
\r
77 Content-Disposition: inline
\r
78 Content-Transfer-Encoding: quoted-printable
\r
81 sorry if this comes as a repost..
\r
83 Excerpts from Carl Worth's message of Fri May 20 23:00:23 +0100 2011:
\r
84 > > However, as a vim user I feel that the one thing that's truly missing i=
\r
86 > > maintainable, feature-rich commandline GUI.
\r
88 > "... that's not implemented in emacs" you mean? ;-)
\r
91 > It's funny to me that you used the name "notmuch-gui" since I've always
\r
92 > understood the 'G' in GUI to indicate "graphical", to distinguish from
\r
93 > non-graphical terminal interfaces like you propose here.
\r
94 I always intuitively understood "graphical" as anything visual.
\r
95 But your right, http://en.wikipedia.org/wiki/Graphical_user_interface
\r
96 suggests that a curses-like interface is not a GUI nor a CLI.
\r
97 Anyhow, I agree that at some point I'll need a real name.
\r
99 > I believe all new code should be doing "import notmuch" rather than
\r
100 > "import cnotmuch", and if there is any package that installs bindings
\r
101 > that work as "cnotmuch" we should get those updated right away.
\r
102 Thanks for the clarification. I assume I'll always get the current
\r
103 bindings distributed with notmuch itself.
\r
104 A make target inside notmuch/bindings/python would indeed be helpful.
\r
106 > > You can find the code at here: https://github.com/pazz/notmuch-gui=20
\r
107 > I was a bit surprised to see so many results in my initial view. I'd
\r
108 > expect a default view to be tag:inbox rather than tag:unread. (I didn't
\r
109 > realize I had over 100 thousand messages with the unread tag, but
\r
110 > apparently I do.) Perhaps that's a sup default that I've long since
\r
112 Yep, its an artefact of my debugging behaviour. Having the initial
\r
113 buffer show the inbox makes total sense and is also what sup does.
\r
115 > * The interface blocks for a while when searching for something (like
\r
116 > "tag:unread" in my case) that returns a *lot* of results. Are you
\r
117 > somehow sucking in all the results immediately rather than just what
\r
118 > you need to dill the current screen?
\r
119 That is surprising! I only fill the screen by iterating over an initial
\r
120 part of the iterator returned by Query.search_threads()
\r
121 I do a second query to count the messages by Query.count_messages(),
\r
122 but I'd guess that this translates to some sort of "SELECT COUNT"
\r
123 and should also be fast. Maybe there's some copying going on=20
\r
126 > * I was a bit surprised that 'i' and 'u' kept opening new buffers
\r
127 > rather than switching to an existing buffer.
\r
128 It shouldn't be like this, I agree. I'm just annoyed that sup treats
\r
129 the inbox view different from other searches, in terms of keybindings.
\r
130 But nevertheless one could have "I" point to a unique inbox search
\r
133 > * The '/' key didn't seem to do anything for me, so I wasn't able to
\r
134 > actually do any custom searches.
\r
135 This is because it really is "\" :P that was a typo in the README.
\r
137 > It looks like a fine start to me. Please let me know if there's anything
\r
138 > I can do to help with this, (in terms of hosting the code or anything
\r
140 Thanks, that's helpful. I guess it would make sense to place this under
\r
141 notmuch/contrib at a later point if it gets usable.
\r
143 Ah I have question regarding "toplevel" messages in threads:
\r
144 How can it be that a mail that is not the one that started a thread
\r
145 is contained in thread.get_toplevel_messages() ?
\r
146 The only thing I can think of is that a user somehow forced two threads
\r
147 to become one. Take this very thread for example. Why do I get
\r
148 Mueen Nawaz's reply as a toplevel message? does this mean
\r
149 that messages header has incorrect Reply-to headers set?
\r
151 @Mueen Nawaz: It's a good idea to post this on the wiki. Will do.
\r
157 Content-Type: application/pgp-signature; name="signature.asc"
\r
158 Content-Description: Digital signature
\r
160 -----BEGIN PGP SIGNATURE-----
\r
161 Version: GnuPG v1.4.11 (GNU/Linux)
\r
163 iEYEARECAAYFAk3YCX0ACgkQlDQDZ9fWxarsDwCgyfCqWxYCrE766LDk6aP9ss2V
\r
164 g8kAn0Y3BUMi7zDPqleASIR26CDZ1IFJ
\r
166 -----END PGP SIGNATURE-----
\r
168 --9amGYk9869ThD9tj--
\r