From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] mscan reliance on stdin
Date: Wed, 19 May 2021 11:25:24 +0200 [thread overview]
Message-ID: <20210519092524.TN0AklP-SD_xTYsz8CRrc_hy4a9AjUocf6V3Sodtyro@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-208@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
Closed issue by hallyn on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/208
Description:
If I do 'mscan' after an 'mseq -S', it shows the sequence. If I do 'mscan < /dev/null', it shows nothing. If I do "mscan' again, it shows all messages again. I noticed this when running mscan inside a script launched through dmenu. Doing 'mseq | mscan' worked around it in that script, but this seemed unintentional based on the code.
next prev parent reply other threads:[~2021-05-19 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 3:16 [ISSUE] " hallyn
2021-05-19 9:25 ` leahneukirchen
2021-05-19 9:25 ` leahneukirchen [this message]
2021-05-19 15:02 ` hallyn
2021-05-19 15:03 ` hallyn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210519092524.TN0AklP-SD_xTYsz8CRrc_hy4a9AjUocf6V3Sodtyro@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).