all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: jidanni@jidanni.org
To: cyd@stupidchicken.com
Cc: emacs-w3m@namazu.org, 3640@emacsbugs.donarmstrong.com
Subject: bug#3640: I can't see all characters in my files anymore
Date: Tue, 23 Jun 2009 10:44:12 +0800	[thread overview]
Message-ID: <87ocsfuer6.fsf__2751.16749476201$1245777536$gmane$org@jidanni.org> (raw)
In-Reply-To: 87prcwf3e5.fsf@stupidchicken.com

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.





  parent reply	other threads:[~2009-06-23  2:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 19:57 bug#3640: I can't see all characters in my files anymore Chong Yidong
2009-06-23  2:43 ` jidanni
2009-06-23  2:44 ` jidanni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-21 14:54 jidanni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='87ocsfuer6.fsf__2751.16749476201$1245777536$gmane$org@jidanni.org' \
    --to=jidanni@jidanni.org \
    --cc=3640@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-w3m@namazu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.