all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 22786@debbugs.gnu.org, mohamed.hibti@gmail.com
Subject: bug#22786: 25.1.50; eww arabic rendering
Date: Wed, 02 Mar 2016 21:38:55 +0200	[thread overview]
Message-ID: <83wppk6568.fsf@gnu.org> (raw)
In-Reply-To: <87wppkrenb.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  02 Mar 2016 17:08:40 +0000)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: mohamed.hibti@gmail.com,  22786@debbugs.gnu.org
> Date: Wed, 02 Mar 2016 17:08:40 +0000
> 
> > Do we have a literal syntax for _any_ character?
> 
> We have ?\s (presumably because people found ?  too annoyingly
> fragile).  Thinking about it a bit more, I think it would be kinda nice
> to have a literal syntax for all Unicode characters.

We have categories, so you can use \cX where X is a single letter
which denotes a category.  Se "M-x describe-categories".  This is
similar to ?\s, but the available categories are rather ad-hoc.

> Something like...  er...  ?\ucLEFT-TO-RIGHT-OVERRIDE and
> \?ucPILE-OF-POO?  We have that table already, so perhaps that's
> feasible?

It's feasible, but is it really useful?  How is it different from just
typing the character in the first place?

> But it's, of course, more important for the control characters, because
> they're just incomprehensible if you just ?💩 them...

"C-x =" usually does the job for me.

> > Btw, these controls display as thin spaces on GUI frames, and as just
> > spaces on a TTY; for best results you could cover each control with an
> > invisible text property, which would make them entirely invisible.
> 
> Hm...  perhaps it's good to (vaguely) show that they're there?  I'm not
> sure.

Could be.  I think by default they shouldn't show, but we could have
an option to reveal them.





  reply	other threads:[~2016-03-02 19:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 22:50 bug#22786: 25.1.50; eww arabic rendering Mohamed Hibti
2016-02-24  1:07 ` Lars Ingebrigtsen
2016-02-24 10:16   ` Mohamed Hibti
2016-02-24 17:37     ` Eli Zaretskii
2016-02-24 18:18       ` Mohamed Hibti
2016-02-24 18:24       ` Mohamed Hibti
2016-02-24 19:11         ` Eli Zaretskii
2016-02-25  5:35     ` Lars Ingebrigtsen
2016-02-25 11:08       ` Mohamed Hibti
2016-02-25 15:55       ` Eli Zaretskii
2016-02-26  5:45         ` Lars Ingebrigtsen
2016-02-26  8:59           ` Eli Zaretskii
2016-02-28  4:13             ` Lars Ingebrigtsen
2016-02-28 15:41               ` Eli Zaretskii
2016-02-28 16:07                 ` Eli Zaretskii
2016-02-29  2:34                   ` Lars Ingebrigtsen
2016-02-29  3:38                     ` Eli Zaretskii
2016-02-29  4:36                       ` Lars Ingebrigtsen
2016-02-29 15:38                         ` Eli Zaretskii
2016-03-01  0:31                           ` Lars Ingebrigtsen
2016-03-01  8:55                             ` Mohamed HIBTI
2016-02-29  2:33                 ` Lars Ingebrigtsen
2016-02-29  3:36                   ` Eli Zaretskii
2016-02-29  4:35                     ` Lars Ingebrigtsen
2016-02-29 15:37                       ` Eli Zaretskii
2016-02-29 23:56                         ` Lars Ingebrigtsen
2016-03-01 16:44                           ` Eli Zaretskii
2016-03-02 17:01                             ` Lars Ingebrigtsen
2016-03-02 19:33                               ` Eli Zaretskii
2016-03-01  0:26                         ` Lars Ingebrigtsen
2016-03-01 16:49                           ` Eli Zaretskii
2016-03-02 17:08                             ` Lars Ingebrigtsen
2016-03-02 19:38                               ` Eli Zaretskii [this message]
2016-03-03  5:38                                 ` Lars Ingebrigtsen

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=83wppk6568.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22786@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mohamed.hibti@gmail.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.