On Thu, 21 May 2020 at 18:15, Mike Miller <python-id...@mgmiller.net> wrote: > > > On 2020-05-21 05:48, Joao S. O. Bueno wrote: > > Input _is_ hard or rare. Deal with it. > > Even the font is not uniformily configured across systems, and a glyph one > > does see here may not show properly on the terminal, or other > > > Maybe long ago. My terminals support even color emoji, have for years, and > are > all free. >
If you format all your computers from a single image, maybe. My pet project over the last year is a unicode art library, I use a Ubuntu 2018 and a Fedora system daily - on my personal machine, which is the Fedora, I've installed all available font packages an their kitchen sink. Still, emoji support varies wildly across terminal programs and even across the same terminal program in Ubuntu and on Fedora. Although, yes, it is likely that "older" glyphs like unicode mathematic symbols will be present in all of then and render . However, that does not mean it will render ok as a single-cell character in a mono-spaced font - as the character "east asian width" property is marked as "A" (Ambiguous), and may vary according to the installed font - even Qt5, perhaps the most sophisticated windowing toolkit available in the World, is severely bugged when displaying non single-width characters in a monospaced cell character environment such as coding space. (Of course, it may be that native Windows character and widget engines or Mac OS's are better in this particular requisite) > The only thing I've seen recently that doesn't is the Linux console, which I > use > rarely for admin tasks. (Oddly enough, it does handle right arrow properly.) > fbterm is an option there for those wanting more. > > Even Windows 10 has gotten in on the act terminal-wise. If you're still on XP > or 7, it's way past time to upgrade. > I consider this thread to be moot at this time - I am just answering this e-mail because you answered me directly - but I had seem no strong support, I had seem you not answering direct questioning about how this will make things harder to learn and use but for writting down your own rationalizations on it. I'd suggest you'd just pause for a bit, and read carefully some of the other e-mails, if mine, focused mainly technical infeasibility of even typing or displaying that character, and consider these questionings for real - not with the ready made answers you have ready in your mind. I am recording a video series trying to present Python programing to absolute beginners - and to keep things timely, the ambiguity between two valid quote types is already a _pain_ - which I simply try to avoid by making consistent use of just one quote type. But after a 4 hour crash course, no one that is not already familiar with coding, could come up comfortable with using both ' or " interchangibly unless I spend 30 minutes focusing ont that. > -Mike > _______________________________________________ > Python-ideas mailing list -- python-ideas@python.org > To unsubscribe send an email to python-ideas-le...@python.org > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/python-ideas@python.org/message/IMQFQ7JLOMJ2PE3MLPEHYTTWNUSH3HBQ/ > Code of Conduct: http://python.org/psf/codeofconduct/ _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/2544WLVWARH23QSLRMX2USP25RCXAOOE/ Code of Conduct: http://python.org/psf/codeofconduct/
