Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot install with sixel lib #628

Open
minhquan186 opened this issue Dec 7, 2024 · 2 comments · May be fixed by #638
Open

Cannot install with sixel lib #628

minhquan186 opened this issue Dec 7, 2024 · 2 comments · May be fixed by #638
Labels
bug Something isn't working

Comments

@minhquan186
Copy link

Describe the bug
Cannot Install spotify_player with sixel support on Windows 10 using cargo

To Reproduce
Run cargo install spotify_player --features lyric-finder,sixel

Expected behaviour
Install spotify_player with sixel support successfully.

Log and backtrace
Installation problem, no log needed

Screenshots
image

Environment

  • OS: Windows
  • Application version: v0.20.3
  • Application features: lyric-finder, sixel

Additional context
I'm using Windows Terminal Preview 1.22.2912.0 which has libsixel supported (see this blog)
If I use cargo install spotify_player --features lyric-finder,image I can install and use it normally

@minhquan186 minhquan186 added the bug Something isn't working label Dec 7, 2024
@aome510
Copy link
Owner

aome510 commented Dec 8, 2024

I don't really know much about sixel support for windows. Maybe the library sixel-sys doesn't support windows

@minhquan186
Copy link
Author

I think sixel-sys could be an issue here.
I use another program (chafa) with sixel supported and it works fine
image
Could you also double check the version of sixel-sys that used in spotify_player?
Thanks in advance

@juliamertz juliamertz linked a pull request Dec 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants