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 59BC3431FBF; Wed, 18 Nov 2009 01:42:17 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org 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 j-W1SQlJ7v4j; Wed, 18 Nov 2009 01:42:16 -0800 (PST) Received: from cworth.org (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 6C6B8431FAE; Wed, 18 Nov 2009 01:42:16 -0800 (PST) From: Carl Worth To: Keith Packard , Mikhail Gusarov , notmuch@notmuchmail.org In-Reply-To: References: <1258471718-6781-1-git-send-email-dottedmag@dottedmag.net> <87lji5cbwo.fsf@yoom.home.cworth.org> Date: Wed, 18 Nov 2009 01:42:02 -0800 Message-ID: <87pr7gqidx.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [notmuch] [PATCH 1/2] Close message file after parsing message headers X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.12 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: Wed, 18 Nov 2009 09:42:17 -0000 On Tue, 17 Nov 2009 13:15:25 -0800, Keith Packard wrote: > Threading the message also involves displaying the from and to contents, > which requires opening the message file. The alternative to the fix I > provided is to just parse all of the message headers when first opening > the message; it could then be immediately closed and the hash referred > to for all header data. Given the choice, just having the caller say > when it has finished with a message is probably a reasonable option... Hi Keith, Once I finally got back on the ground again, I pushed out a revised version of your patch, (didn't need the reply-to stuff anymore since I had fixed that differently in the meantime). I'm pretty happy with the state of this portion of the code now. Thanks Keith and Mikhail for your input on and code to fix this bug. -Carl