dankamongmen
Skipping prohibited unicode instead of erroring
Currently printing string that contains prohibited unicode will result an error and stop printing (the error log pointed me to this line). Would it be better to skip the character and logwarn (or other level of logging) that the function skipped it?
yeah, i've thought about this. the problem is that it's really hard to indicate to the caller that there were elided glyphs, or where they were. perhaps an option, though...?
The problem with stopping at prohibited unicode is that I will have to sanitize the string myself before passing to notcurses, which would duplicate the utf8 checks.
Maybe an option would be good. Maybe you can also consider putting all the alignment and styling options in an option struct? This would be a breaking change tho. Just a random suggestion.
yep, something like that. i'm pondering what to do. open to suggestions!