From: notthewave <notthewave@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sfeed: update to 1.2.
Date: Wed, 16 Feb 2022 16:40:08 +0100 [thread overview]
Message-ID: <20220216154008.Uwdf3B-H6oNpeOp9sr6cox-ppkqkUH9Ajfd1zo3EN_M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35542@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
New comment by notthewave on void-packages repository
https://github.com/void-linux/void-packages/pull/35542#issuecomment-1041750469
Comment:
```
sfeed_content formats feed data (TSV) from sfeed(1) from stdin or for
each file to stdout as plain-text content. For HTML content it uses
lynx(1) to convert it to plain-text. At the end it uses the pager to
view the output. The sfeed_content script can be used by sfeed_curses(1)
to view content.
SFEED_HTMLCONV
The program used to convert HTML content to plain-text. If it is
not set it will use lynx by default.
```
It can be set by the user, however lynx is the default.
Not sure what to prefer here.
prev parent reply other threads:[~2022-02-16 15:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 20:36 [PR PATCH] " notthewave
2022-02-11 20:45 ` [PR REVIEW] " Chocimier
2022-02-11 21:04 ` [PR PATCH] [Updated] " notthewave
2022-02-11 21:07 ` notthewave
2022-02-11 21:08 ` notthewave
2022-02-11 21:08 ` notthewave
2022-02-11 21:11 ` notthewave
2022-02-11 21:44 ` Chocimier
2022-02-11 21:50 ` [PR PATCH] [Updated] " notthewave
2022-02-11 21:52 ` notthewave
2022-02-11 21:54 ` notthewave
2022-02-11 22:38 ` notthewave
2022-02-12 14:04 ` notthewave
2022-02-13 19:50 ` [PR PATCH] [Updated] " notthewave
2022-02-13 19:53 ` notthewave
2022-02-13 20:01 ` notthewave
2022-02-13 20:08 ` notthewave
2022-02-13 20:08 ` notthewave
2022-02-13 23:59 ` tibequadorian
2022-02-14 0:02 ` [PR PATCH] [Updated] " notthewave
2022-02-14 0:03 ` notthewave
2022-02-14 7:26 ` [PR PATCH] [Merged]: " paper42
2022-02-16 10:22 ` dkwo
2022-02-16 15:40 ` notthewave [this message]
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=20220216154008.Uwdf3B-H6oNpeOp9sr6cox-ppkqkUH9Ajfd1zo3EN_M@z \
--to=notthewave@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).