Henrik Friedrichsen
Henrik Friedrichsen
No problem. It never happens when you need it to :smile: I restarted ncspot around 20 times yesterday as I was trying to reproduce it, but nothing :(
Unfortunately this does not seem to be possible with Cursive at the moment: gyscos/cursive#477
Both errors indicate a timeout when trying to connect to Spotify, any firewalls in place?
Ah nice detective work, I've just switched to crossterm by default in `main`, would be curious to know if the problem occurs there as well.
@ThomasFrans I think you are onto something w.r.t this: > From what I can see, this is caused by the backend trying to return from the alternate screen by writing...
Maybe it's doing the exit/ backend cleanup logic twice or something, as I can't reproduce this with a test application that doesn't call `Cursive::quit()` on `SIGHUP`.
ncurses would be the reasonable choice and I was looking into this today, but unfortunately the ncurses backend has its own problems such as 256 colors not working correctly.
I appreciate your proposal. Some thoughts from my side: I have to say that I myself currently don't have the time to maintain a terminal backend, that shouldn't stop you...
In rspotify `ureq` is used for blocking interface and `reqwest` for async. Since the web API code in ncspot is still sync we can't switch to `reqwest` without larger changes.
@aubergino Is this fixed with the changes from #1343 or is that unrelated? I don't use KDE so can't reproduce it, unfortunately.