1 Return-Path: <james@hackervisions.org>
\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 046594048D3
\r
6 for <notmuch@notmuchmail.org>; Fri, 12 Mar 2010 07:01:14 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-1.308 tagged_above=-999 required=5 tests=[AWL=1.191,
\r
12 BAYES_00=-2.599, RDNS_DYNAMIC=0.1] autolearn=no
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id fGcTOT2MRAcA for <notmuch@notmuchmail.org>;
\r
16 Fri, 12 Mar 2010 07:01:12 -0800 (PST)
\r
17 Received: from hackervisions.org (67-207-143-141.slicehost.net
\r
19 by olra.theworths.org (Postfix) with ESMTP id 2D4B14048D0
\r
20 for <notmuch@notmuchmail.org>; Fri, 12 Mar 2010 07:01:12 -0800 (PST)
\r
21 Received: from ool-18bd392a.dyn.optonline.net ([24.189.57.42] helo=localhost)
\r
22 by hv with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69)
\r
23 (envelope-from <james@hackervisions.org>)
\r
24 id 1Nq6MR-0006xh-8L; Fri, 12 Mar 2010 10:01:11 -0500
\r
25 From: James Vasile <james@hackervisions.org>
\r
26 To: Michal Sojka <sojkam1@fel.cvut.cz>, notmuch@notmuchmail.org
\r
27 In-Reply-To: <87iq92m12o.fsf@steelpick.localdomain>
\r
28 References: <87aauhp9kk.fsf@hackervisions.org>
\r
29 <87pr3bm2sn.fsf@steelpick.localdomain>
\r
30 <87fx46hq7w.fsf@hackervisions.org>
\r
31 <87ljdyn7zi.fsf@steelpick.localdomain>
\r
32 <876352hccg.fsf@softwarefreedom.org>
\r
33 <87iq92m12o.fsf@steelpick.localdomain>
\r
34 Date: Fri, 12 Mar 2010 10:01:04 -0500
\r
35 Message-ID: <87zl2deg9b.fsf@hackervisions.org>
\r
37 Content-Type: text/plain; charset=us-ascii
\r
38 Subject: Re: [notmuch] [PATCH] Change From and Bcc when creating reply draft
\r
40 X-BeenThere: notmuch@notmuchmail.org
\r
41 X-Mailman-Version: 2.1.13
\r
43 List-Id: "Use and development of the notmuch mail system."
\r
44 <notmuch.notmuchmail.org>
\r
45 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
46 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
47 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
48 List-Post: <mailto:notmuch@notmuchmail.org>
\r
49 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
50 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
51 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
52 X-List-Received-Date: Fri, 12 Mar 2010 15:01:14 -0000
\r
54 On Fri, 12 Mar 2010 08:49:35 +0100, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
\r
55 > On Thu, 11 Mar 2010, James Vasile wrote:
\r
56 > > On Thu, 11 Mar 2010 17:22:41 +0100, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
\r
57 > > > thanks for clarification. It all sounds reasonable. The only problem I
\r
58 > > > can see now is that if I create a new account on my machine and run
\r
59 > > > emacs there, then the value of user-mail-address is <login>@<hostname>
\r
60 > > > which doesn't refer to existing mailbox. I think that the header should
\r
61 > > > only be rewritten if these variables are known to have valid values. Do
\r
62 > > > you know how to do this?
\r
65 > > I explicitly set these in my .emacs file, so I don't do any detection.
\r
66 > > If you could define "valid" I suppose you could test for such things.
\r
68 > > Something like the following works for me. I run mail-profile-foo with
\r
69 > > M-x or run it automatically with profile-guessing/setting routines.
\r
70 > > When I get the system ironed out, I'll emit patches and a wiki entry.
\r
72 > > (defun message-mode-set-profile ()
\r
74 > > (when (string= "message-mode" major-mode)
\r
75 > > (goto-char (point-min))
\r
76 > > (when (re-search-forward "^From: " nil t)
\r
78 > > (insert (format "%s <%s>" user-full-name user-mail-address)))
\r
80 > > (goto-char (point-min))
\r
81 > > (when (re-search-forward "^Bcc: " nil t)
\r
83 > > (insert (format "%s <%s>" user-full-name user-mail-address))))))
\r
85 > > (defun mail-profile-hv ()
\r
87 > > (setq mail-host-address "hackervisions.org"
\r
88 > > user-full-name "James Vasile"
\r
89 > > message-sendmail-extra-arguments '("-a" "hv")
\r
90 > > user-mail-address "james@hackervisions.org")
\r
91 > > (message-mode-set-profile)
\r
92 > > user-mail-address)
\r
93 > > (mail-profile-hv)
\r
95 > > <other mail-profile-foo functions>
\r
97 > Hmm, I understand. My worry about this approach is the following: Now it
\r
98 > is very straightforward to start using notmuch. You only answer a few
\r
99 > questions when you run notmuch for the first time and then it works. If
\r
100 > we apply your patch, some additional configuration is needed and a
\r
101 > novice might not know how to do it.
\r
103 I disagree as to how much time notmuch currently takes. To get a
\r
104 workable setup, you need to answer a few questions, setup offlineimap,
\r
105 write a tagging script, setup up folders, apply a bunch of patches,
\r
108 I've been telling people to wait 6 months instead of trying notmuch.
\r
109 That's based on how much work it is to setup, incomplete MUA, bugs, etc.
\r
111 > So at least notmuch should tell the user what and where needs to be
\r
112 > configured. Or better, provide some sane default which can be overridden
\r
113 > in a way you want it.
\r
115 > That's only my opinion. I personally would have no problem with
\r
116 > additional configuration, but on the other side I like programs which do
\r
117 > not steel my time if it is not necessary.
\r
119 That's a fair point. I hope notmuch gets easier over time, and one of
\r
120 the things I'd like to implement is sane defaults. As notmuch gets more
\r
121 user friendly, I'd like to make the pieces I write less onerous to
\r
124 For example, I have some stub code for a default profile that pulls
\r
125 values from ~/.notmuch. Then if the user doesn't do the setup, things
\r
126 should be not much different than they are now.
\r
projects / notmuch-archives.git / blob