From: jidanni@jidanni.org
To: cyd@stupidchicken.com
Cc: 3640@emacsbugs.donarmstrong.com
Subject: bug#3640: I can't see all characters in my files anymore
Date: Tue, 23 Jun 2009 10:43:32 +0800 [thread overview]
Message-ID: <87skhrwtyj.fsf@jidanni.org> (raw)
In-Reply-To: 87prcwf3e5.fsf@stupidchicken.com
>>>>> "CY" == Chong Yidong <cyd@stupidchicken.com> writes:
>> Help, I'm now shipping files to people with all kinds of embedded junk
>> in them like
>> | character: (8206, #o20016, #x200e)
>> |preferred charset: unicode (Unicode (ISO10646))
>> | code point: 0x200E
>> | syntax: . which means: punctuation
>> | buffer code: #xE2 #x80 #x8E
>> | file code: #xE2 #x80 #x8E (encoded by coding system utf-8-unix)
>> | display: by this font (glyph code)
>> | xft:-unknown-FreeSans-normal-normal-normal-*-16-*-*-*-*-0-iso10646-1 (#x8F1)
>> |
>> |Character code properties: customize what to show
>> | name: LEFT-TO-RIGHT MARK
>> | general-category: Cf (Other, Format)
>> all because I can't see them anymore now that I use emacs23.
CY> Your font claims to be able to display character code 8206. So, Emacs
CY> does not get in the way. This is not a bug.
Yes and I'm sure it does display it properly: the proper way is to make
it disappear, as it is a special direction changing character and not a
normal character.
This is where emacs needs to step in and give the user a way to be aware
his file contains such things.
Just like whitespace mode makes one aware one has whitespace.
I'll see if whitespace.el will fill my needs...
next prev parent reply other threads:[~2009-06-23 2:43 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 [this message]
2009-06-23 2:44 ` jidanni
-- 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=87skhrwtyj.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=3640@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
/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.