From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 61BD76DE012F for ; Tue, 12 Apr 2016 00:23:44 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.177 X-Spam-Level: X-Spam-Status: No, score=-0.177 tagged_above=-999 required=5 tests=[AWL=-0.110, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.652, UNPARSEABLE_RELAY=0.001] 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 rEjzYVkgnW1l for ; Tue, 12 Apr 2016 00:23:36 -0700 (PDT) Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by arlo.cworth.org (Postfix) with ESMTPS id DBE246DE0127 for ; Tue, 12 Apr 2016 00:23:35 -0700 (PDT) Received: by mail-wm0-f54.google.com with SMTP id l6so175248822wml.1 for ; Tue, 12 Apr 2016 00:23:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dme-org.20150623.gappssmtp.com; s=20150623; h=to:subject:in-reply-to:references:from:date:message-id:mime-version; bh=b0a0OlGUCi2g6zdsBf8rUR1CBqlNXsdqUeTTKltBVC4=; b=L6PFyVqGIkGHU7jPF4a1XdtAQdwvkHibluGQOhQ52qY4EJInz56m2NewduS4EcoDHu tFEiL0FpugbJ9ujeu5/WvKwSxmD4HPcQbDhypJ2OtTKCZ9hVbx4gNgxmwJIZMbTuSy/+ +nlpCQHk0G1Rzz0RL7IZfhU2OBWe8vGaJjO3KTeXblWlQIgu2lW7Hr+eCUHi6XBix96W mavpSdUAbGsxgEC2nQWcq5mf3FtHqzEUcEcEh8BpBiJ6Y2e6moFR7QUrhH4EcV3vSouM VEg8E2ID+w/HhNSKrzma2EZObape3kcGMlJtF1N9eHt6dCjNs4d55U20HPE3v34bMwZP wq2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:in-reply-to:references:from:date :message-id:mime-version; bh=b0a0OlGUCi2g6zdsBf8rUR1CBqlNXsdqUeTTKltBVC4=; b=KBGtd+TUP2fqX438V/Cy8EAGuecifQi93N6Zp4uqBOPQZYinHQ5A49YAqFQxEa+qLl CkTZsvGihlyehnb7RVRiPEkD0IQY+YEiMJDmT50gaJgFwaDuHHjKv/Q+1O71oiDH3cjD Mzxe6MUl5MdJmzcTCLwo3s36lhVolVo9MMAF1AT60EW6mwixgvTKitCWB0WYNrZonhUG DXWNrYkQF3JUyFGM/JGSvQxB4u7O6f29WoRMV1ijQYSlN0NpP8G5D8bnrjeYbWr47Cnm jmHGOLBqsQ//MwfRLIZ49x+3hqf+LIYZsqYVK3aqfFNguiGTTKh9q/67HJZVQqgPeH1H XPHQ== X-Gm-Message-State: AD7BkJIG3XkSwT3Ue8JmaXpKYNWzb23YpFZpbbNN97byS46a+A7xNchlWryrOlclaYyxoQ== X-Received: by 10.28.58.77 with SMTP id h74mr22726459wma.82.1460445813920; Tue, 12 Apr 2016 00:23:33 -0700 (PDT) Received: from disaster-area.hh.sledj.net ([2a01:348:1a2:1:ea39:35ff:fe2c:a227]) by smtp.gmail.com with ESMTPSA id n3sm31658620wja.6.2016.04.12.00.23.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Apr 2016 00:23:32 -0700 (PDT) Received: from localhost (disaster-area.hh.sledj.net [local]) by disaster-area.hh.sledj.net (OpenSMTPD) with ESMTPA id a975fab3; Tue, 12 Apr 2016 07:23:31 +0000 (UTC) To: Daniel Kahn Gillmor , David Bremner , notmuch@notmuchmail.org Subject: Re: notmuch-emacs replying produces excessive indenting on multipart/signed or multipart/mixed amil? In-Reply-To: <87oa9fsl9i.fsf@alice.fifthhorseman.net> References: <87lh4nm62m.fsf@alice.fifthhorseman.net> <87wpo6fvju.fsf@zancas.localnet> <87ziszson5.fsf@alice.fifthhorseman.net> <8760vn7k5g.fsf@zancas.localnet> <87oa9fsl9i.fsf@alice.fifthhorseman.net> From: David Edmondson Date: Tue, 12 Apr 2016 08:23:31 +0100 Message-ID: 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: Tue, 12 Apr 2016 07:23:44 -0000 On Mon, Apr 11 2016, Daniel Kahn Gillmor wrote: > On Mon 2016-04-11 20:20:11 -0400, David Bremner wrote: >> I have the feeling I don't understand the problem. I replied to your >> message, and didn't see any extra indentation there. I thought my reply >> to the list was test enough. So what am I missing? > > Aha, it is due to a setting, thanks. it's due to > notmuch-show-indent-multipart -- try setting it to "t" ? > > i find that setting useful during notmuch-show buffers, but i don't > think it should apply when generating a reply message. We can try binding it to nil during reply generation. Will generate patch...