-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Suggestions for Strings (even a bug?) #41
Comments
Let's leave the The "(mutable)" and "13B" parts you query come from this: julia> s = "Páll"
"Páll"
julia> ismutable(s)
true
julia> Base.summarysize(s)
13 This actually understates the size of the
This sounds like a terminal theme issue.
The characters you use in |
You mean it's different for you or that I could change with a theme? I think I have default theme/terminal for Linux Mint, likely same as for Ubuntu. And blue is always bad on black, so I think you want to have good defaults. |
It's terminal theme-dependent, and I think a strong argument can be made that basic ANSI colours should all be easily legible.
This depends entirely on the lightness ratio. For reference, here's what I experience on two of my computers: and I'd recommend setting terminal themes that have good contrast ratios across all main colours, and short of that you can customise the |
Strings are immutable, so "String (mutable)" is misleading, even if implemented somehow by something mutable, maybe just special-case and override that output?
Aslo while 5B is correct, do you know where 13B comes from? I doubt it's even correct. The minimum (malloc) allocation in Julia is 16 bytes it seems, here seemingly 8-byte overhead added.
Also blue on black background isn't the best color. Hard to see for "5 "codepoints]" and also for "Extended ASCII", where does that come from? Not strictly wrong, but state UTF-8? Or "UTF-8 (extended ASCII)"? And ASCII/UTF-8 when that applies?
I know why this happens "┌╴'Ã'╶─┐┌╴'¡'╶─┐", a bit misleading... could show like:
┌───- 'á' -───┐
┌╴'Ã'╶─┐┌╴'¡'╶─┐
The text was updated successfully, but these errors were encountered: