View Single Post
Old 02-16-2018, 08:48 PM   #14
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,682
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by roger64 View Post
I tend to think that there should be no "invisible characters" in Code view. Code view job is to show the code. Point.
A narrow non-breaking space is not "invisible." A zero-width joiner is invisible. A soft hyphen is invisible. A narrow non-breaking space is a visible space.

Code View is there to show code. Code contains spaces. Point.

If you want your special space characters to be more visible in Code View, then don't use characters--use entities. We're not going to make them glow, or underline them, or blink at you, or anything else like that.

Code View is going to show the glyph or an entity. Those are the choices.

The very definition of a monospaced font is that all characters occupy the same amount of horizontal space, by the way. Therefore, a monospaced font with nnbsp support, would not BE a monospaced font (which are the only type of fonts Code View supports).

Last edited by DiapDealer; 02-16-2018 at 09:03 PM.
DiapDealer is offline   Reply With Quote