Hi Tony! On So, 03 Aug 2014, Tony Mechelynck wrote:
> On 03/08/14 07:58, Paul Moore wrote: > [...] > > > >Thanks for the explanation, but with all due respect, it doesn't seem > >unreasonable to me for a user to expect that if they specify a > >commonly-used monospace font like Consolas, Lucida Console, or even > >Courier New, they should get behaviour that is similar to that of > >every other text editor around, which is that characters outside of > >the normal range of the font are displayed in a way (presumably using > >an alternative substitute font) that makes their form discernable - > >not a "no such character" box, but a usable representation. Having sto > >set a series of options that require a deep understanding of character > >sets and how fonts work should not be needed just to see the contents > >of a file to the level of clarity that Notepad can manage. I agree completely here. > >I understand that Vim does things very differently from other programs > >at an internal level to allow (for example) support for R-L character > >set handling. And I appreciate that the code in Vim is old, dating > >back to Windows 95 and earlier, and as such includes workarounds for > >limitations of some very old systems. > > Much earlier. There are (or used to be) versions of Vim for MS-DOS > and for 16-bit Windows: that should tell you. And the other editors > (such as Notepad) of that time didn't try to second-guess fonts: you > selected one, and they used that; and any character for which your > font had no glyph appeared as some "placeholder glyph", usually a > hollow box. While it is true, that the code is very old, it is not unmaintained which makes your argument just an excuse. > >But honestly, none of this matters. The simple fact is that Vim should > >be able to do (at least) as well as everything else. I don't have an > >issue with the fact that there's a problem right now, but I do expect > >at least an acknowledgement that this is a bug and that fixes when > >offered will be considered. I agree here as well. > [...] > > Well, it can. Just switch to Linux and compile Vim with GTK2. :-P You don't always have the choice. And since this seems to work with the GTK2 build (I didn't test it), I see no reason, why this behaviour should not be also enabled on other GUIs. Best, Christian -- Moral ist eine Schwäche des Gehirns. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
