From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Itai Berli Newsgroups: gmane.emacs.bugs Subject: bug#27526: 25.1; Nonconformance to Unicode bidirectionality algorithm due to paragraph separator Date: Mon, 17 Jul 2017 21:33:07 +0300 Message-ID: References: <83inj8nt0h.fsf@gnu.org> <83eftwnpk0.fsf@gnu.org> <83shhvcdvq.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a11423ae8bec901055487a3ae" X-Trace: blaine.gmane.org 1500316531 4916 195.159.176.226 (17 Jul 2017 18:35:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 17 Jul 2017 18:35:31 +0000 (UTC) To: 27526@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jul 17 20:35:24 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dXArc-0000yz-Fd for geb-bug-gnu-emacs@m.gmane.org; Mon, 17 Jul 2017 20:35:24 +0200 Original-Received: from localhost ([::1]:51964 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dXAri-0005vd-4q for geb-bug-gnu-emacs@m.gmane.org; Mon, 17 Jul 2017 14:35:30 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58582) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dXAqN-00054w-8c for bug-gnu-emacs@gnu.org; Mon, 17 Jul 2017 14:34:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dXAqK-0004bn-J5 for bug-gnu-emacs@gnu.org; Mon, 17 Jul 2017 14:34:07 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:42098) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dXAqK-0004b8-Ec for bug-gnu-emacs@gnu.org; Mon, 17 Jul 2017 14:34:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dXAqI-0000Is-Fz for bug-gnu-emacs@gnu.org; Mon, 17 Jul 2017 14:34:04 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Itai Berli Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 17 Jul 2017 18:34:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 27526 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 27526-submit@debbugs.gnu.org id=B27526.15003164361155 (code B ref 27526); Mon, 17 Jul 2017 18:34:02 +0000 Original-Received: (at 27526) by debbugs.gnu.org; 17 Jul 2017 18:33:56 +0000 Original-Received: from localhost ([127.0.0.1]:44775 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dXAqC-0000IZ-DA for submit@debbugs.gnu.org; Mon, 17 Jul 2017 14:33:56 -0400 Original-Received: from mail-wm0-f44.google.com ([74.125.82.44]:36513) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dXAqA-0000IL-4T for 27526@debbugs.gnu.org; Mon, 17 Jul 2017 14:33:54 -0400 Original-Received: by mail-wm0-f44.google.com with SMTP id t70so23805141wmt.1 for <27526@debbugs.gnu.org>; Mon, 17 Jul 2017 11:33:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=KqYwU4sYLGfpFjwNzRIYCFCJumabrl6/Usq0VOZjl7Q=; b=nsK2IP39bsw5ooMxYXBMAFE6yAA5HEY2DdsG89GniieOcF5yiXDVgaf78ZcmuaEvnb f+8QLWDmA0V6e1eOV+I8o1icqLACsWaaLvNsM7vy/SRWPppgWfUF77uFQHvtUtHziIrR RIUflkOZhFhX2IHaeBWfJiGhYYowUuHFjAMnvqo68mlOjfylPqqMmvrceLxzEV/ddhVN AM8wmDKYUQeFDN+54un3dsTjHr7H2GZx+pomWBtBiPUn2jkLVV9Q+FIMLiOfahsFr9ZH OnXUDViQ/qgpmQ6msNdxGha+shCtV1RK79hQppxv7BCKjP5dBMjZHNICMlRiAQ2essef euVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=KqYwU4sYLGfpFjwNzRIYCFCJumabrl6/Usq0VOZjl7Q=; b=q457xjstTRzjRrPUHb///CiS8Bbh7tdyGXG6OG2VwG7cPsd90iEDdh6a5bf4QhSP45 GzOuPHWLYcICc9MohEpa0Y5cDJ0jUYp4SJt1f4fXduHFCzg+C0wceGgTyufx9dX5y8DD /75kkI1kzi1IQXmBQmxOIajaIUgswangNQo3+/mvIg2O7RoDx5f27x8bmLJqB6JbuOBL KdEr6HB6ksQRd+XhUweNg1qAL1cbbEipUFwikFaDnDk8ZckYJch0vHRBmOiiOPiKgLeN G24FKKQgSmhvFBN0X2dRE/voop38UdxNwj3/Y0MKLK1RTCCzCjDHE/KTc+BJbap4Dmjo J1IA== X-Gm-Message-State: AIVw110f33h1lY9KX/mQRRUdPzbsz+NQpFseVuCVOdcIkDhxpkKlgaXc nR/LOGhA53QkghTZyo63ZZ3ASH5lietK X-Received: by 10.28.45.197 with SMTP id t188mr4763764wmt.78.1500316428056; Mon, 17 Jul 2017 11:33:48 -0700 (PDT) Original-Received: by 10.28.197.9 with HTTP; Mon, 17 Jul 2017 11:33:07 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:134683 Archived-At: --001a11423ae8bec901055487a3ae Content-Type: text/plain; charset="UTF-8" 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 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 wrote: > >> > Date: Tue, 04 Jul 2017 19:18:39 +0300 >> > From: Eli Zaretskii >> > Cc: 27526@debbugs.gnu.org >> > >> > > From: Itai Berli >> > > 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. >> > > > --001a11423ae8bec901055487a3ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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:

<= div>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 easi= er for me to wait till this patch makes it to the official release.

It's actually pretty easy t= o 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:
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 Zaretsk= ii <= eliz@gnu.org> wrote:
> D= ate: Tue, 04 Jul 2017 19:18:39 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 27526@d= ebbugs.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 whe= ther the bidi imiplementation will consider the
> > newline character as the paragraph separator or an empty line? >
> Could be.=C2=A0 I'd need to carefully review the code to say for s= ure.
> Originally, the regexp which defines where paragraph begins was
> customizable, but it led to grave bugs, so I removed that.=C2=A0 Maybe= a
> more restricted facility could avoid such pitfalls.

It turned out to be relatively easy, so I implemented this on t= he
master branch of the Emacs Git repository.=C2=A0 There are two new
variables that you should set to "^" to get the behavior you want= ed.
I hope you can build the master branch and see whether the new
facilities solve your case.

Thanks.



--001a11423ae8bec901055487a3ae--