Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 0056C6DE0356 for ; Fri, 29 Apr 2016 07:44:47 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.016 X-Spam-Level: X-Spam-Status: No, score=-0.016 tagged_above=-999 required=5 tests=[AWL=-0.005, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 FzwAykjF_rnY for ; Fri, 29 Apr 2016 07:44:39 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 121266DE0352 for ; Fri, 29 Apr 2016 07:44:39 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84) (envelope-from ) id 1aw9eh-000712-L1; Fri, 29 Apr 2016 10:44:31 -0400 Received: (nullmailer pid 15762 invoked by uid 1000); Fri, 29 Apr 2016 14:44:34 -0000 From: David Bremner To: sfischme@uwaterloo.ca, Notmuch Mail Subject: Re: message-default-mail-headers not working in notmuch 0.22 In-Reply-To: <87y47wmsfi.fsf@uwaterloo.ca> References: <87y47wmsfi.fsf@uwaterloo.ca> User-Agent: Notmuch/0.21+99~gd93d377 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Fri, 29 Apr 2016 11:44:34 -0300 Message-ID: <871t5oa2zx.fsf@zancas.localnet> 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: Fri, 29 Apr 2016 14:44:47 -0000 Sebastian Fischmeister writes: > Hi, > > After upgrading to notmuch 0.22, my emacs config seems broken: > > (setq message-default-mail-headers "Reply-to: me@example.com\nBcc: me@example.com") > > When creating a new mail, it has no header other than "To:" and > "Subject:". > > Since I cannot find any item in the NEWS related to this release, is > this expected behaviour? Looks like this problem was introduced in commit 570c0aeb40bd. Confusingly it looks like it has something to do with the different handling of "message-default-headers" and "message-default-mail-headers" in message-setup-1. d