GNU bug report logs - #3640
I can't see all characters in my files anymore

Previous Next

Full log

Message #22 received at 3640 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: jidanni <at> jidanni.org
To: cyd <at> stupidchicken.com
Cc: 3640 <at> debbugs.gnu.org, emacs-w3m <at> namazu.org
Subject: Re: I can't see all characters in my files anymore
Date: Tue, 23 Jun 2009 10:44:12 +0800

OK, I cooked up this workaround in .emacs:

;;Just to see if there are any zero width >‎<, U+200E LEFT-TO-RIGHT MARK
;;hiding in our files, we do:
(global-whitespace-mode 1)
(setq whitespace-style '(spaces))
;;Set neighbor characters on fire in order to see where the
;;"invisible man" is:
(setq whitespace-space-regexp "\\(.?\x200E+.?\\)")
(put 'whitespace-space-before-tab 'face-alias 'whitespace-space);fire color
;;Works except if it is the only char on a line. (In emacs -nw it is
;;width 1, not zero, for me.)

What a pain. But then to turn it on in emacs-w3m,
(add-hook 'w3m-mode-hook
	  (lambda ()
	    (whitespace-mode 1)))
But that kills all of emacs-w3m's font-locks.

Why can't there be a way to not allow any "invisible man" characters
from hiding, like it was in emacs22. Just make them show up as this
dotted box like in xterm, so we know something is funny there.
Is there some variable that can stop 0 width characters being smuggled
around under the users' noses unaware?

I mean isn't that what separates us from the MicroSoft users, they don't
know what is going on inside their files, but we do -- until now.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.