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: Tue, 4 Jul 2017 19:37:04 +0300 Message-ID: References: <83inj8nt0h.fsf@gnu.org> <83eftwnpk0.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="f403045de95ec58be5055380800b" X-Trace: blaine.gmane.org 1499186291 12632 195.159.176.226 (4 Jul 2017 16:38:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 4 Jul 2017 16:38:11 +0000 (UTC) To: 27526@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jul 04 18:38:07 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 1dSQpx-000326-Na for geb-bug-gnu-emacs@m.gmane.org; Tue, 04 Jul 2017 18:38:05 +0200 Original-Received: from localhost ([::1]:42270 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dSQq3-0001si-7M for geb-bug-gnu-emacs@m.gmane.org; Tue, 04 Jul 2017 12:38:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38246) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dSQpx-0001sc-TM for bug-gnu-emacs@gnu.org; Tue, 04 Jul 2017 12:38:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dSQpu-0006GX-PC for bug-gnu-emacs@gnu.org; Tue, 04 Jul 2017 12:38:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:49695) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dSQpu-0006GN-M0 for bug-gnu-emacs@gnu.org; Tue, 04 Jul 2017 12:38:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dSQpu-0007SI-9F for bug-gnu-emacs@gnu.org; Tue, 04 Jul 2017 12:38:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Itai Berli Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 04 Jul 2017 16:38: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.149918627328639 (code B ref 27526); Tue, 04 Jul 2017 16:38:02 +0000 Original-Received: (at 27526) by debbugs.gnu.org; 4 Jul 2017 16:37:53 +0000 Original-Received: from localhost ([127.0.0.1]:52372 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dSQpk-0007Rq-O5 for submit@debbugs.gnu.org; Tue, 04 Jul 2017 12:37:52 -0400 Original-Received: from mail-ua0-f179.google.com ([209.85.217.179]:35364) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dSQpi-0007Rb-SW for 27526@debbugs.gnu.org; Tue, 04 Jul 2017 12:37:51 -0400 Original-Received: by mail-ua0-f179.google.com with SMTP id j53so129574323uaa.2 for <27526@debbugs.gnu.org>; Tue, 04 Jul 2017 09:37:50 -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=RcEXKP0pGHaJXOFDpuQs9REtNnRqSaIq46pkxkX1Nk8=; b=t0xAL0ps3+NWpOxmZRXhQ0jrklISoYgJdN0SNskOlQ2HOfi5jcBDx44y5AS1LDHMVs vqrteqXDno+bn1XY9JLZKUwhyUOFxxv9uhiy4U8pN7um5jH2eZiRvuqh0Y4q/+lbmNcx QAGQAUuigDy4peJDu5j89Ur6ATSgbpS+YlzFcV+cE0Zx2K487FGeBmYhB3uNcmWxN8na y/9dzNiu/s88iLhMwp4u+gHxA4k1EQvsrvzUc4iIldroFd01KtRwORtGGdwZtWaVcLcL fiS0WbFE8YEi8Qwo4gUl5XZjoTJX87Kje94PG4/j1Mzjy6CtyKpMQl7ZHqhqJCR1hKhJ D0tQ== 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=RcEXKP0pGHaJXOFDpuQs9REtNnRqSaIq46pkxkX1Nk8=; b=J0IC1mfZBDCQ/9ANyHD26fzirDHHle7Gn8EubD1YdGfbSMY/65XzA3wUA8mRKRDyxB Ki8vlT9j0O3+DagX+j61Ho4tH4BXF8LVH0C0lGqXyzD+WLL2Wc/6AxnbrcoNJcJImJ7V LAPmfZJapfGYGCzIMQ2+y5OlRFS5ghX2S1gBqPJGWPkIPnjBaD4PoHdy136uhWYDpG0O SodFuAsJ1s/ceEugB4OnM9KvW+IoyxQH7grgaQ+0iVX399T2e8EpSLs1k84elrjKDkoK NDwqCEJWzyVcAfjghuRzirzf7usTcjwH3BUkWLX6w1fpFR1AOew0B8AO7YErWbFw6G90 ePTg== X-Gm-Message-State: AKS2vOz0QP6iTZ+0pNQBRKIudHGFg7esup27rACfvWhX98Gp4UMzbAnx eKh1SsKAvcdhurdB3P9EPDQDqJaM9xcX X-Received: by 10.159.49.19 with SMTP id m19mr24273553uab.46.1499186264901; Tue, 04 Jul 2017 09:37:44 -0700 (PDT) Original-Received: by 10.176.70.85 with HTTP; Tue, 4 Jul 2017 09:37:04 -0700 (PDT) In-Reply-To: <83eftwnpk0.fsf@gnu.org> 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:134176 Archived-At: --f403045de95ec58be5055380800b Content-Type: text/plain; charset="UTF-8" If you can do it, that'll be fantastic. And while you're perusing the code, perhaps you can see if it is also possible to allow the user to decide whether they want the bidi control characters to be visible or not On Tue, Jul 4, 2017 at 7:18 PM, Eli Zaretskii wrote: > > 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. > --f403045de95ec58be5055380800b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If you can do it, that'll be fantastic. And while you&= #39;re perusing the code, perhaps you can see if it is also possible to all= ow the user to decide whether they want the bidi control characters to be v= isible or not

On Tue, Jul 4, 2017 at 7:18 PM, Eli Zaretskii <eliz@gnu.org> wr= ote:
> 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 b= e 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.=C2=A0 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.=C2=A0 Maybe a more restricted facility could avoid such pitfalls.

--f403045de95ec58be5055380800b--