newsboat: Unable to mark all articles in a feed as read

Newsboat version (copy the output of newsboat -v or the first line of git show): 2.26.0

Config file (copy from ~/.newsboat/config or ~/.config/newsboat/config):

confirm-mark-all-feeds-read no

Steps to reproduce the issue:

  1. Start Newsboat with a clean cache file, a minimal temporary config file and url file:

    newsboat -c /tmp/newsboat-cache.db -C /tmp/newsboat-config -u /tmp/newsboat-urls
    
  2. Press r or R to download at least one feed, and then open it with Enter to see its list of articles.

  3. Press A to try to mark all articles as read.

  4. The following message appears on the status bar, regardless of whether confirm-mark-all-feeds-read no is in the config file or not:

    Do you really want to mark this feed as read (y:Yes n:No)?
    
  5. Pressing y doesn’t do anything, only n does, which cancels the operation.

Other info you think is relevant:

I’m using Newsboat inside Zsh 5.8 and Alacritty 0.9.0 on Manjaro Linux.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 29 (23 by maintainers)

Most upvoted comments

@Minoru

Ignore the prompt FR question. I see what I did. That’s what I get for trying to be fancy. I’ve played with this this morning over breakfast and using the default Nord palette works way nicer (once I stopped being fancy). Will put in a PR shortly. Thanks!

Alright, @Minoru and @pittavini

You guys are going to laugh when I tell you what I tracked down.

I tried the method above to test it was my urls. System doesn’t hang. OK, must be one of my feeds… but also noted that the message to confirm the entire feed was read popped up.

So, I start removing feeds. Still hanging… hmmm… also, why don’t I see the confirm message? So, I hit y as a key next… and… the feed is read.

What I’m guessing happened in 2.26:

  1. The default behaviour for confirm-mark-feeds-read changed to true (triggering a confirm dialogue on A to read the feeds if it was not set in the config file.)
  2. The theme I use (Nord) from contrib… does not pop up a visible dialogue message in the space below the info bar for some reason - it seems invisible but obviously happens - so may be related to the colour scheme (since it works in a naked config file.).

I added confirm-mark-feeds-read false into my config file so now a simple A reads the feed when I’m done.

More to the point though, how do I fix the Nord colour scheme to make sure I see the pop up norification? I"m assuming it is a colour scheme issue - so curioous as to what controls the notification messages text in the colour scheme options so I can fix it (I am embarrassingly also the author of that theme from 3 years ago… 8-/ ).

Anyhow, lemme know if I’ve guessed right. I am quite pleased it’s not a more serious problem though! (and omg, sorry for all the trouble in tracking down what looks like a display rather than code problem.).

Just when I try to mark feeds All Read (even if it the option is set to false confirm-mark-all-feeds-read false explicitly or that option is not present in the config file.

I did some tests from Alexander’s asks and Q&A type question like confirm before exit will also cause the hang behaviour.

¯\(ツ)

I will try after work and dinner to compile directly from source and take this out of homebrew entirely to see if that does not trigger the problem. (I am very surprised it’s working for you tbh… now I’m also wondering if it is perhaps one of the feeds I have and some sort of parsing issue since that’s about the only other thing I can think of. 🤔 ).

Hehe… it is an interesting mystery though. 🕵🏼‍♂️

On Tue, Mar 8, 2022 at 3:36 PM pittavini @.***> wrote:

@wakatara https://github.com/wakatara

right monterey 12.2.1, the hanging behavior is only in the question y/n or does it happen when you read feeds too?

— Reply to this email directly, view it on GitHub https://github.com/newsboat/newsboat/issues/1932#issuecomment-1061490702, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAWMW4XHXVUCVBWGEL2YLU637PDANCNFSM5LWID2OA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

@dennisschagt Yes, I’m using a Hungarian locale. I can confirm that pressing i works.

I can create a PR with the correct translation of the message later, if that’s OK with you.

You are also right about confirm-mark-feed-read. I was a little hasty while looking for marking all articles as read in the documentation, so I mixed it up with confirm-mark-all-feeds-read.

Thank you for the help!

regardless of whether confirm-mark-all-feeds-read no is in the config file or not:

That setting is used when marking all feeds as read (default C key in the feed overview). When you mark a single feed as read (default A key in feed overview and article list), the confirm-mark-feed-read configuration is checked instead (documentation)

Pressing y doesn’t do anything, only n does, which cancels the operation.

@maxigaz: Any chance you are Hungarian? (or using the Hungarian locale?)

In the Hungarian translation, it looks like the question text is not translated (marked as “fuzzy”). If it would be translated, it would probably look something like <question in Hungarian> (i: Igen, n: Nem), meaning that you would have to press the i key instead of the y key. Could you let us know if pressing the i key works for you, or if you are not using the Hungarian locale?

Relevant part of the Hungarian translation file

https://github.com/newsboat/newsboat/blob/3572347c5e0d7a4bc564546211858c2a426a0fac/po/hu.po#L705-L721