From: Kyle Meyer <kyle@kyleam.com>
To: meta@public-inbox.org
Subject: Re: lei q: --stdin confuses --mua
Date: Sat, 17 Apr 2021 12:04:42 -0400 [thread overview]
Message-ID: <87sg3olwx1.fsf@kyleam.com> (raw)
In-Reply-To: <87v98klxg3.fsf@kyleam.com>
Kyle Meyer writes:
> [*] 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
guh, that's a confusing typo: s/don't not/don't/
> with --stdin either.
next prev parent reply other threads:[~2021-04-17 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 15:53 lei q: --stdin confuses --mua Kyle Meyer
2021-04-17 16:04 ` Kyle Meyer [this message]
2021-04-17 19:00 ` [PATCH] lei q: fix MUA spawn after reading query from stdin Eric Wong
2021-04-17 20:13 ` Kyle Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg3olwx1.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).