From: Parasrah <Parasrah@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mrep: fix subject not populating when pager stdout is not tty
Date: Tue, 18 Jul 2023 06:11:16 +0200 [thread overview]
Message-ID: <20230718041116.FQYjePW16gM_wX_30cio7V-xZrfaTqjptrDNy9ajvh8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-243@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
New comment by Parasrah on mblaze repository
https://github.com/leahneukirchen/mblaze/pull/243#issuecomment-1639364275
Comment:
It does not seem to:
```sh
$ export MBLAZE_PAGER=kak
$ echo "$(COLUMNS=10000 mscan -f '%S' "$file" </dev/null)"
Fatal error: stdout is not a tty
$ echo "$(MBLAZE_PAGER=cat COLUMNS=10000 mscan -f '%S' "$file")"
Test Subject
```
next prev parent reply other threads:[~2023-07-18 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 4:41 [PR PATCH] " Parasrah
2023-07-17 13:33 ` leahneukirchen
2023-07-18 4:11 ` Parasrah [this message]
2023-07-18 12:05 ` [PR PATCH] [Closed]: " leahneukirchen
2023-07-18 12:05 ` leahneukirchen
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=20230718041116.FQYjePW16gM_wX_30cio7V-xZrfaTqjptrDNy9ajvh8@z \
--to=parasrah@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).