Age | Commit message (Collapse) | Author |
|
This required a bump of supported GNU Make version, as Make 3.81 that's
shipped by modern macOS failed to process our new Makefile. The bump
shouldn't inconvenience anyone, because:
- macOS users can easily get a newer Make from Homebrew, which they
already use for other dependencies of ours;
- non-macOS users probably have Make 4.0+ because it was released in
2013, earlier than our minimum supported C++ compiler.
Fixes #792.
|
|
|
|
|
|
|
|
|
|
|
|
I dropped Alpine version from the Rust tag ("rust:1.53.0-alpine3.12" →
"rust:1.55.0-alpine") because the Alpine version doesn't actually matter
to us, and referencing Docker Hub to figure out which Alpine version is
used for which Rust release is needless work for us.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Resolves #1643.
|
|
demure on IRC pointed out that it might be good to mention integration
with newsreading services, but it felt unfair to call out just that
single feature, so I wrote a whole section.
|
|
goz mentioned this on IRC.
|
|
Lars Wirzenius offers to review FOSS READMEs[1], so I submitted ours.
This commit addresses most of the feedback.
> A slight concern is that it doesn't explain, or link to an
> explanation, what "an RSS/Atom feed reader" is or what it's for.
> Perhaps adding words to the effect that it's good for following blogs
> and news sites? And link to
> https://en.wikipedia.org/wiki/News_aggregator for more information?
Done, although I expect my explanation of a "feed reader" can be
improved.
> A carefully arranged screenshot of a terminal with the software
> running would add some punch and give an indication of what the
> software is like.
Done. I also took an opportunity to replace the screenshot on our
website, as it was getting dated.
> I find the logo credit and licensing at the top to be distracting.
> Couuld they be moved to the end, with the licensing information of the
> software itself?
Agree, done. All the legalese is now at the end of the README.
> I like that […] there are […] pointers at […] where to get support,
> although I'm worried that support is needed. The word support could
> perhaps be tweaked: help, maybe? Support sounds so formal.
I'm in two minds about this. "Support" might sound formal, but "Help"
won't look as well as a heading IMHO.
1. https://liw.fi/readme-review/
|
|
|
|
|
|
I think it makes more sense to put it amidst the other instructions,
rather than keep it at the very end.
|
|
Release Newsboat 2.22.1
Fixed
=====
- Slow scrolling in the article list (regression) (#1372) (Alexander Batischev)
- Segfaults if `swap-title-and-hints` is enabled (regression) (#1399) (Dennis
van der Schagt)
- Build failure on GCC 9 due to `maybe-uninitialized` warning which `-Werror`
turns into an error (Alexander Batischev)
|
|
Provide guidelines on how to contribute to Newsboat.
Resolves: #28
|
|
|
|
|
|
|
|
It lacks `std::is_trivially_move_constructible` from <type_traits>. This
trait is used by the cxx crate which we're going to use from now on, so
GCC 4.9 has to go.
|
|
Kudos to @ttldtor for pointing out that Coveralls provides a GitHub
Action.
|
|
Fixes #896.
|
|
|
|
|
|
https://github.com/newsboat/newsboat/pull/1174#pullrequestreview-483127665
|
|
The following notice is added to the website:
If you have found a vulnerability, please email
security@newsboat.org, and use the aforementioned PGP key if at all
possible.
|
|
|
|
The code is over-indented by two spaces, making it look unaligned in the
resulting HTML.
|
|
|
|
|
|
|
|
This builds on top of the previous commit to fix #966.
|
|
Fixes https://github.com/newsboat/newsboat/issues/966
Thanks for the info @Minoru
|
|
Travis deprecated travis-ci.org, so I moved the repo over to
travis-ci.com a while ago.
|
|
|
|
Cherry-picked from #907, which was later reverted by
6a4e5af4449fd25964295cf8322ca69273e30378.
|
|
newsboat/feature/3-doc-dotdir-and-xdg-take-2"
This reverts commit 5c8ff095fa0f0c481e5c893e43e8293c0358ac4c, reversing
changes made to 6bf7fc91ab4d8dc49c54ebdb333747b83af01ec4. Those changes
made it a requirement to have "urls" file. I (the author of the changes)
thought that this requirement already exists, but it didn't. I thought
the "urls" file is used to decide what directories to use, but according
to ConfigPaths::find_dirs_xdg(), we only check if XDG config directory
exists. Requiring the urls file seems unnecessary, since users can
configure a different `urls-source`.
Kudos to @carno for spotting the regression.
|
|
|
|
|
|
https://github.com/asciidoctor/asciidoctor/blob/master/CHANGELOG.adoc#user-content-1-5-3-2015-10-31-mojavelinux
Kudos to @dennisschagt for digging through the changelog.
|
|
|
|
|
|
|