From: Rustom Mody <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: beginner questions
Date: Wed, 2 Oct 2013 07:34:55 -0700 (PDT) [thread overview]
Message-ID: <5b95e531-0b04-443a-9324-9335f7cffebf@googlegroups.com> (raw)
In-Reply-To: <mailman.3227.1380675393.10748.help-gnu-emacs@gnu.org>
On Wednesday, October 2, 2013 6:26:06 AM UTC+5:30, Stefan Monnier wrote:
> > Finally switched to vi. It showed me:
>
> > [[http://cs.brown.edu/people/pw/papers/monist.ps<200e>][Philosophical diffs between OOp and FP]]
>
>
> > 200e??? What the hell...
>
>
> Indeed, as the display engine becomes more powerful over time, the
> general rule gets broken more and more often. Unicode is a source of
> lots of problems along this way (e.g. with all the barely visible
> characters such as the one above, as well as all the "different
> character, but displays identically"). There are some libraries that
> try to help with this, e.g. uni-confusable (in GNU ELPA), but it's
> a hard problem because there is no single "right thing to do".
Thanks Stefan. I appreciate that choosing the right action is probably very hard.
I was just pointing out that your statement: What you see is all there is to see
seems to be eminently suitable for an editor (as against say a browser, a word-processor etc) and it would be a shame if emacs started breaking that rule more than necessary.
prev parent reply other threads:[~2013-10-02 14:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 7:55 beginner questions JohnF
2013-09-25 9:26 ` Pascal J. Bourguignon
2013-09-25 11:18 ` JohnF
2013-09-25 12:55 ` Pascal J. Bourguignon
2013-09-28 8:39 ` JohnF
2013-09-28 15:30 ` Pascal J. Bourguignon
2013-09-28 17:11 ` Rustom Mody
2013-09-28 18:07 ` Pascal J. Bourguignon
2013-09-29 3:45 ` Drew Adams
2013-09-28 22:32 ` Kai Grossjohann
2013-09-29 8:30 ` Drew Adams
2013-09-29 7:27 ` JohnF
2013-09-29 13:45 ` Pascal J. Bourguignon
2013-09-30 8:46 ` JohnF
2013-09-26 2:22 ` Jude DaShiell
2013-09-25 17:47 ` Doug Lewan
[not found] ` <mailman.2869.1380131281.10748.help-gnu-emacs@gnu.org>
2013-09-26 7:44 ` JohnF
2013-09-26 17:52 ` Ken Goldman
[not found] ` <mailman.2943.1380217948.10748.help-gnu-emacs@gnu.org>
2013-09-27 2:37 ` Rustom Mody
2013-09-28 8:16 ` JohnF
2013-09-28 18:18 ` Stefan Monnier
[not found] ` <mailman.3090.1380392333.10748.help-gnu-emacs@gnu.org>
2013-09-29 7:58 ` JohnF
2013-10-01 17:27 ` Rustom Mody
2013-10-01 17:57 ` Eli Zaretskii
2013-10-01 20:02 ` Joost Kremers
2013-10-02 0:56 ` Stefan Monnier
[not found] ` <mailman.3227.1380675393.10748.help-gnu-emacs@gnu.org>
2013-10-02 14:34 ` Rustom Mody [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b95e531-0b04-443a-9324-9335f7cffebf@googlegroups.com \
--to=rustompmody@gmail.com \
--cc=help-gnu-emacs@gnu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).