From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Yuan Fu Newsgroups: gmane.emacs.devel Subject: Re: Line wrap reconsidered Date: Tue, 26 May 2020 00:46:01 -0400 Message-ID: <522C17DE-71ED-45E1-BB66-62C041804AA7@gmail.com> References: <92FF4412-04FB-4521-B6CE-52B08526E4E5@gmail.com> <878shfsq35.fsf@gnus.org> <6795D9A1-904E-4C6F-AE86-9EDD52718F01@gmail.com> <090B0FA5-2AA6-4134-BB8B-3FD9BFCC5AA0@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_3BBC85C9-C199-4777-B436-0615CAD1B8D0" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="48525"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel To: Lars Ingebrigtsen , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 26 06:46:47 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jdRUF-000CWt-4V for ged-emacs-devel@m.gmane-mx.org; Tue, 26 May 2020 06:46:47 +0200 Original-Received: from localhost ([::1]:39186 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdRUE-0001I8-5D for ged-emacs-devel@m.gmane-mx.org; Tue, 26 May 2020 00:46:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54542) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jdRTZ-0000qq-0G for emacs-devel@gnu.org; Tue, 26 May 2020 00:46:05 -0400 Original-Received: from mail-qk1-x736.google.com ([2607:f8b0:4864:20::736]:39284) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jdRTY-0002Ee-80; Tue, 26 May 2020 00:46:04 -0400 Original-Received: by mail-qk1-x736.google.com with SMTP id w3so13857780qkb.6; Mon, 25 May 2020 21:46:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=nKvBXEHdM0VrvGGbkjL1uqMhFviFYwiBYo8/7QwJHno=; b=TXnPHFfPTX8htjfLo2m2evzlKgEV/LzZh3lD7F8lwsjdk3skK6k6Pa9+ipV9/yXdHk 12O7D4ydVm2hH68rryV4y5ofzOHGsEOAyq2xiJMFpi/WeolnGJwOrYKPyOsQRqB/DyUo fefPBxBdA5xagOMmbgnSe0kHkWDAUycmjDXgnH7icyfNKpUt6e27QiwkklKEuTnK/owR HEsf3g8I1exgydLecKeP/zrjkA0leN78KZUh+P8Q9DVlC47y/fUloOndr0dgJm3uh7BV Vn4gkqXsWmlpsCZu+/t+2umDF+jxpqYEHrZkVSNnkP3msCTTmDBBHY6G46p5LgYYQgaI q+/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=nKvBXEHdM0VrvGGbkjL1uqMhFviFYwiBYo8/7QwJHno=; b=FO8GpFzF21kbRBO5loS2o1IXnoomACVty/l235SWpLgPGavqkZ5swdaoeA3rLsNVuv +/oBiKLxQfKaUIDZ9A4pf+g2DqBplhe7LG4jFjiA7KOx5L8VCF+CEJ704OIqw3CKlhgr qo86qtlCJhRKKMG/HY+c5NWLkTDtg2BG44ZsNrvPSo2Mgh8FwpJxymynt2mwDqYXJdTS 1+LkFnGJNcWfrqa4vpJByvW7Y/nARZzJYtNYuZNTK802RKYRh3gRIgS1SxzZh3pTT5Q/ erUKr0fZQ+PJzfAbKQFGY4KYLRTlJVvI5VDanvmRDfKn8UiFJ6W4fR6kAlZ3I94y+ozY BKEw== X-Gm-Message-State: AOAM531dBhzYdJbClsFWZ2EdFPhZRK4oDm1MDjdGmI0/9OZKpTE7qWmJ OmSguMZoC2fMn7cJZ9MemOg= X-Google-Smtp-Source: ABdhPJwpI6RUIi/R2zNIO01KT8WgJU18FaUqmabxTJ4WXiblzJKBkbnsF1eQOD9xwhqez7ZR1a9bgA== X-Received: by 2002:a05:620a:1003:: with SMTP id z3mr11696820qkj.217.1590468362702; Mon, 25 May 2020 21:46:02 -0700 (PDT) Original-Received: from [192.168.1.10] (c-174-60-229-153.hsd1.pa.comcast.net. [174.60.229.153]) by smtp.gmail.com with ESMTPSA id v2sm8398008qtq.8.2020.05.25.21.46.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 May 2020 21:46:02 -0700 (PDT) In-Reply-To: <090B0FA5-2AA6-4134-BB8B-3FD9BFCC5AA0@gmail.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) Received-SPF: pass client-ip=2607:f8b0:4864:20::736; envelope-from=casouri@gmail.com; helo=mail-qk1-x736.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:251427 Archived-At: --Apple-Mail=_3BBC85C9-C199-4777-B436-0615CAD1B8D0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Ok, turns out category table is the way to go. There are already = category tables defined for my use case: "Not at eol=E2=80=9D(>), "Not = at bol=E2=80=9D(<) and =E2=80=9Cline breakable=E2=80=9D(|). They are = used for filling but are just as appropriate as for wrapping. Now there = seems to be two routes: one is to directly use category tables to = determine whether to wrap, one is to still use text property to = determine whether to wrap, and use category table to apply text = property. Which approach is more efficient?=20 Besides efficiency concerns, using text properties allows use cases = described by Ihor, where user can customize on what to wrap and what not = to. That seems nice. Yuan= --Apple-Mail=_3BBC85C9-C199-4777-B436-0615CAD1B8D0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Ok, turns out = category table is the way to go. There are already category tables = defined for my use case: "Not at eol=E2=80=9D(>), "Not at = bol=E2=80=9D(<) and =E2=80=9Cline breakable=E2=80=9D(|). They are = used for filling but are just as appropriate as for wrapping. Now there = seems to be two routes: one is to directly use category tables to = determine whether to wrap, one is to still use text property to = determine whether to wrap, and use category table to apply text = property. Which approach is more efficient? 

Besides efficiency concerns, using text = properties allows use cases described by Ihor, where user can = customize on what to wrap and what not to. That seems nice.

Yuan
= --Apple-Mail=_3BBC85C9-C199-4777-B436-0615CAD1B8D0--