-
Notifications
You must be signed in to change notification settings - Fork 9
siggo 0.9.0. on FreeBSD slightly broken interface #42
Comments
Hey! This looks like you might have installed using Edit: just saw that you re-built from source. Hrrmmm... I'll try and test if I can. I don't have a FreeBSD box available. I can test on MacOS and Ubuntu. |
Thanks for the reply. Another piece of info I realized: |
Same issue on Arch linux, building from the 0.9.0 AUR entry. I have rebuilt with a fresh go installation with no change to the UI effect mentioned here. |
Yeah, I forgot to mention that too, I tried multiple terminal emulators, all of them had the same results. I also tried 2 or 3 different fonts, that also didn't help. |
Hey guys, I am able to reproduce the error. It looks like somehow the contact names are read from the signal-cli data file sandwiched between some unicode that I'm not familiar with: \u2068 and \u2069 I am not sure why this is happening, but hopefully I can get you a fix soon. |
Just trying this project out today, also confirming the issue on arch. Possibly related: https://www.w3.org/International/questions/qa-bidi-unicode-controls |
Hey guys, this should be fixed on master. Please try it out and re-open if you still see this issue. |
@derricw Seems to have fixed it! Now running into a crash:
Related: #41 |
Ok, I built it after fixing u_int type: and now the issue with UI seems gone, thanks @derricw! |
@sharksforarms Thanks. Since @kilix-git is reporting this particular problem fixed, I'll leave this one closed and work on #41. |
@derricw Issue resolved. This is working beautifully again on Arch. Many thanks. |
Hello,
Basically, my siggo now looks like this, any idea where should I start troubleshooting? The area where my contacts are present makes the adjacent text field shifted by one character to the left, which makes the text field corrupted. Some random characters appear there, which nobody typed, the borders are shifted, etc, see picture.
Running on FreeBSD 12.2-p4, I rebuilt siggo from source again just to be sure, the issue is there.
The text was updated successfully, but these errors were encountered: