From: Itai Berli <itai.berli@gmail.com>
To: 27526@debbugs.gnu.org
Subject: bug#27526: 25.1; Nonconformance to Unicode bidirectionality algorithm due to paragraph separator
Date: Wed, 12 Jul 2017 18:10:19 +0300 [thread overview]
Message-ID: <CABsNJ=O6jWbAiz4xGGNKhS0OZG9_+hPUHvVZziiJuy6eT6CTgQ@mail.gmail.com> (raw)
In-Reply-To: <83a84knlh9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
Is there any progress with allowing the user to customize the
end-of-paragraph mark to be the OS paragraph separator character?
On Tue, Jul 4, 2017 at 8:46 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Itai Berli <itai.berli@gmail.com>
> > Date: Tue, 4 Jul 2017 20:01:25 +0300
> >
> > You did, but it would be much nicer for a noob like me to be able to
> simply type in my .emacs file something
> > like: (bidi.markers.visible false), or maybe even
> >
> > (bidi.markers.ALM null)
> > (bidi.markers.RLM ⊲)
> > (bidi.markers.LRM ⊳)
>
> Sorry, I don't see why the exact way how to customize this is so
> important. glyphless-char-display-control is a user-level
> customizable variable, not some obscure feature that requires Lisp
> programming to tailor it to your needs.
>
> > Isn't the Bidi feature important and complicated enough to merit its own
> tailored set of customizable
> > parameters?
>
> It does have its private customizations, but this one isn't one of
> them, I don't see why it should be. The characters of the Cf general
> category are quite a few, and Emacs handled them all the same, because
> they all have the same nature.
>
[-- Attachment #2: Type: text/html, Size: 1653 bytes --]
next prev parent reply other threads:[~2017-07-12 15:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 9:16 bug#27526: 25.1; Nonconformance to Unicode bidirectionality algorithm due to paragraph separator Itai Berli
2017-06-29 9:42 ` bug#27526: Explicit directionality marks CAN be inserted! Itai Berli
2017-06-29 14:49 ` bug#27526: 25.1; Nonconformance to Unicode bidirectionality algorithm due to paragraph separator Eli Zaretskii
2017-06-29 18:36 ` Itai Berli
2017-07-04 10:42 ` Itai Berli
2017-07-04 15:03 ` Eli Zaretskii
2017-07-04 15:57 ` Itai Berli
2017-07-04 16:18 ` Eli Zaretskii
2017-07-04 16:37 ` Itai Berli
2017-07-04 16:47 ` Eli Zaretskii
2017-07-04 17:01 ` Itai Berli
2017-07-04 17:46 ` Eli Zaretskii
2017-07-12 15:10 ` Itai Berli [this message]
2017-07-12 15:36 ` Eli Zaretskii
2017-07-12 15:52 ` Itai Berli
2017-07-12 16:12 ` Eli Zaretskii
2017-07-17 14:54 ` Eli Zaretskii
2017-07-17 15:16 ` Itai Berli
2017-07-17 15:23 ` Jean-Christophe Helary
2017-07-17 18:33 ` Itai Berli
2017-07-17 20:20 ` Eli Zaretskii
2017-07-17 20:43 ` Itai Berli
2017-07-18 2:33 ` Eli Zaretskii
2017-07-18 2:45 ` Glenn Morris
2017-07-18 4:01 ` Itai Berli
2017-07-18 4:54 ` Eli Zaretskii
2017-07-18 5:52 ` Itai Berli
2017-07-18 13:27 ` Itai Berli
2017-07-18 14:44 ` Eli Zaretskii
2017-07-18 15:22 ` Itai Berli
2017-07-18 15:55 ` Eli Zaretskii
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='CABsNJ=O6jWbAiz4xGGNKhS0OZG9_+hPUHvVZziiJuy6eT6CTgQ@mail.gmail.com' \
--to=itai.berli@gmail.com \
--cc=27526@debbugs.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.
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.