From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.0.0.0/16 X-Spam-Status: No, score=-3.2 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out2.migadu.com (out2.migadu.com [IPv6:2001:41d0:2:aacc::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 6B4531F4B4 for ; Sat, 17 Apr 2021 15:53:23 +0000 (UTC) X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1618674798; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=SlzimS1Xpvvonfwsg9HQ99tBI7XJ8TyVUQdoFqWMl6s=; b=thpVLndD8hHyAQaKUUEc+2v6BYi2+3KrNVmSgW6+4mqulVyAd4UZKgjx3N0laEW7lTDLZx xruFI7Hkv7K2Z20zbxhnQsSCXWiNEbL8tKPl+GXt0sziisNz+xw4F8wJhFKyjDzse3/3Eh Yd/Kl64Go/5OilEwK75o0zTqZDj/6REJEqReVK78FXcdkTLwxmGPGRzNR4U90C7zwd6x1g kpeihPNONIzRpuUp6IMJYwdo4Tlnv0k//Gr5yPPjaYmzJ6Vkc2F5LwIhLpFWnlT6+dUAE9 9yJMpWz9ivY+jlCMpOjXVBSIYdxVeniqzSCNMvwF+K7zJVAfGpCgbNlcLrrsoA== From: Kyle Meyer To: meta@public-inbox.org Subject: lei q: --stdin confuses --mua Date: Sat, 17 Apr 2021 11:53:16 -0400 Message-ID: <87v98klxg3.fsf@kyleam.com> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kyle@kyleam.com List-Id: I used `lei p2p' to track down an associated thread recently. It worked nicely, though I noticed that I wasn't able to jump straight into mutt via --mua. Here's an example using public-inbox.git. Feeding the p2q output on stdin, I'm told that no recipients were specified, and the command exits rather than dropping me into mutt's interface. $ lei p2q 8ab43c1c27c725a8ef9307f5dba3e565169d48ca | \ lei q -q -tt - -o mboxcl2:/tmp/t.mbox --mua=mutt No recipients were specified. I'm not a mutt user, but I think that's because mutt sees that stdin isn't attached to a tty. I haven't tried anything on my end yet, but perhaps there's a clean way to make --stdin and --mua [*] work together. Thoughts? [*] The only other --mua value I checked was 'mail' (and that shows a similar issue), but I'm guessing other MUAs don't not work well with --stdin either.