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 C98CC6DE1075 for ; Wed, 10 Apr 2019 04:19:20 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.307 X-Spam-Level: X-Spam-Status: No, score=0.307 tagged_above=-999 required=5 tests=[AWL=-0.347, DKIMWL_WL_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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 9ENTAd8oAoUv for ; Wed, 10 Apr 2019 04:19:19 -0700 (PDT) Received: from mail-wm1-f41.google.com (mail-wm1-f41.google.com [209.85.128.41]) by arlo.cworth.org (Postfix) with ESMTPS id 736D86DE1029 for ; Wed, 10 Apr 2019 04:19:19 -0700 (PDT) Received: by mail-wm1-f41.google.com with SMTP id 4so2186114wmf.1 for ; Wed, 10 Apr 2019 04:19:19 -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=pZU2Lw3Wgsd9Eb79in7pFo7kKwejup6NOzpPadsSK/M=; b=WRU6mOY2GE6sN2D3H5eF+n9XLCHcZgEUAyQbOMbT9+HecgesZYBNo5D3fZdk75XxAh xWzcpF1ASHmiBlA60QUjpmtV+jyK0KrcuvSdRSLROOqbDKZkHWljfme8yejMJeGmCrkw /4lyjqVRaUA79vkKJnRPFUAG4wlX6kG0LtPgmFYAix96NuqxNrTXGj210I6XtBjjlQpD ussN8tZdujDIhcpBrztUbIetlvMJLZkWc9yIs/D+6GMQ7QoOL0DoSVpyrnneRljAPBac I4GJjwmI9SJb+cUFrZYbJXY9BRJpD62E1AvM7GQP+qfqn/9VeaT7VjGs2r8e7csEE3WG 8wZw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:subject:in-reply-to:references:from:date :message-id:mime-version; bh=pZU2Lw3Wgsd9Eb79in7pFo7kKwejup6NOzpPadsSK/M=; b=JdAMtR+N6hI03WNokW4vNgSD8yiQBJbpKgc3yAg0WAy6hibke9JTlKpjVYmSoftxW8 ivH5+SBgXsUplLuIZh8D5RqMKyst7nHD+mibRnZaJSO4E7xoN54vXK5+sYf5MMZ2nPMO APcfkXiacN/ZnEsc2+GjN1s1nvzg9QzJb9xIW9z1y6soyOkU7DCvTvxbCSGvM5Sv+2wl uUbfa//k6hXCUcy9bdN2BNKPJEodpLAiP6QXn3GDo4hJHwV0IO7HxUA3aznB6SKA/TAQ OJP9oJi8NAklaVSaRo2V4e50geXIB0EyQBQrIhh5H2sZskdx79F1Y0NnDh/LjmYI3rzv /BBw== X-Gm-Message-State: APjAAAX91f1+1ltJTam3/Xw9ujDqKhIoGfx3gRVk1ZZquAlr8ZQ1QfEQ 5B1sBvRl1KecAiChOrQfs1x/Wg== X-Google-Smtp-Source: APXvYqx7PaoobTNLkh1sElazbN/CZmjTjZNsxoowvebZr46YNUIacZrBGm408cfno3DSrUKr8QGIiA== X-Received: by 2002:a05:600c:28d:: with SMTP id 13mr1306884wmk.82.1554895157723; Wed, 10 Apr 2019 04:19:17 -0700 (PDT) Received: from disaster-area.hh.sledj.net (disaster-area.hh.sledj.net. [81.149.164.25]) by smtp.gmail.com with ESMTPSA id q3sm47451346wrr.75.2019.04.10.04.19.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Apr 2019 04:19:16 -0700 (PDT) Received: from localhost (disaster-area.hh.sledj.net [local]) by disaster-area.hh.sledj.net (OpenSMTPD) with ESMTPA id 3a67e6e1; Wed, 10 Apr 2019 11:19:15 +0000 (UTC) To: Pierre Neidhardt , notmuch@notmuchmail.org Subject: Re: Reply inline in notmuch-show buffer, "mu4e-conversation style" In-Reply-To: <87a7gyb06w.fsf@ambrevar.xyz> References: <877ecvb0q7.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> <877ecvm05y.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> <87tvffqwp0.fsf@ambrevar.xyz> <87a7gyb06w.fsf@ambrevar.xyz> X-HGTTG: heart-of-gold From: David Edmondson Date: Wed, 10 Apr 2019 12:19:15 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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, 10 Apr 2019 11:19:20 -0000 On Wednesday, 2019-04-10 at 12:53:59 +02, Pierre Neidhardt wrote: > David Edmondson writes: >> Maybe something akin to gnus-dired-mode would be interesting - it would >> be used in notmuch-show mode and yank selected text into the current >> message-mode buffer (including quoting). > > That could work too. We might have to store the name of the composition > buffer in a variable that's buffer-local to the notmuch-show buffer, so > that Notmuch does not get confused when composing several emails at the > same time. gnus-dired just asks if it is unsure which of the existing composition buffers you want to use. > Having a conversation area in the same buffer has > some benefits though: > > - Less key presses to start composing. How? Don't I still have to hit one key? > - No need to play with buffers to display both the thread and the composition. If a thread is any length, I will want to split the window to show older mail while I'm writing my comments at the bottom of the thread. So there might only be one buffer, but two windows, so I'm not sure of the benefit. > - The above problem disappears, there is no need to manually keep a > relation ship between 2 buffers since there is only one buffer. > > With this workflow however, we don't need to cite the previous email > when composing. Well, this presumes a particular workflow and set of mail clients. Whether it's a good idea to top post without the bottom is debatable, I think. > So it'd be nice to have an option to discard the > citation (I think it is a nice option in general). > > This could be done with `notmuch-mua-cite-function', or, maybe better, > have a dedicated option so that `notmuch-mua-reply' does not include the > citation in the first place. > > Thoughts? > > -- > Pierre Neidhardt > https://ambrevar.xyz/ dme. -- All those lines and circles, to me, a mystery.