Open ljgonzalez1 opened 5 months ago
Same here, is this a confirmed bug? I'm actually also seeing it on windows.
edit: On Mac I was able to resolve by building locally with cargo build --release --no-default-features --features portaudio_backend,mpris,notify,share_clipboard,crossterm_backend
Describe the bug In Mac OS some symbols look "broken" if they are not ASCII. Aparently there are some problems displaying some non ASCII characteres, both in its own terminal and over SSH to a linux terminal WITH UTF-8/Unicode support. While running natively on linux it shows fine
To Reproduce You need either an ARM or Intel computer running Mac OS (it happens in both).
A. Through homebrew:
Install ncspot through the homebrew app:
Start ncspot and login with your credentials
B. Compile ncspot from source
Install rust with the script provided in their website:
Clone the repo (recursively just in case) and go inside the folder:
Compile de code using cargo and the recommended flags
Start ncspot and login with your credentials
Expected behavior
Curent behavior
System 1:
System 2:
Additional context
As a suggestion or a question, which files would I need to modify to add ASCII-only support? If I want to create another version of ncspot which replaces all the unicode symbols with unicode + tty-supported characters.
I have the time now, so may be I could learn rust and make a PR with a flag for compiling it that way.
... this doesn't look that bad: