bug#27526: 25.1; Nonconformance to Unicode bidirectionality algorithm due to paragraph separator

[Itai Berli <itai.berli@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]

Eli, what version number should I download?

On Mon, Jul 17, 2017 at 6:23 PM, Jean-Christophe Helary <
jean.christophe.helary@gmail.com> wrote:

>
> On Jul 18, 2017, at 0:16, Itai Berli <itai.berli@gmail.com> wrote:
>
> Thanks. I've never built Emacs from source. I think it might be easier for
> me to wait till this patch makes it to the official release.
>
>
> It's actually pretty easy to build from source. The easiest way (that
> depends on your platform) is to install the version that corresponds to
> HEAD. The slightly less trivial way is toget the code from Savannah:
> https://savannah.gnu.org/projects/emacs
> clone the code and follow the instructions.
> I got used to doing that a few weeks ago and it is fascinating to see all
> the new features pouring in everyday.
>
> Jean-Christophe
>
>
> On Mon, Jul 17, 2017 at 5:54 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> > Date: Tue, 04 Jul 2017 19:18:39 +0300
>> > From: Eli Zaretskii <eliz@gnu.org>
>> > Cc: 27526@debbugs.gnu.org
>> >
>> > > From: Itai Berli <itai.berli@gmail.com>
>> > > Date: Tue, 4 Jul 2017 18:57:33 +0300
>> > >
>> > > How about letting the user decide what's best for them? Would it be
>> possible to add an option to Emacs that a
>> > > user can set, say, in their .emacs file, which will determine whether
>> the bidi imiplementation will consider the
>> > > newline character as the paragraph separator or an empty line?
>> >
>> > Could be.  I'd need to carefully review the code to say for sure.
>> > Originally, the regexp which defines where paragraph begins was
>> > customizable, but it led to grave bugs, so I removed that.  Maybe a
>> > more restricted facility could avoid such pitfalls.
>>
>> It turned out to be relatively easy, so I implemented this on the
>> master branch of the Emacs Git repository.  There are two new
>> variables that you should set to "^" to get the behavior you wanted.
>> I hope you can build the master branch and see whether the new
>> facilities solve your case.
>>
>> Thanks.
>>
>
>
>

[-- Attachment #2: Type: text/html, Size: 3477 bytes --]