From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id IiNOGHyZTWPbKwEAbAwnHQ (envelope-from ) for ; Mon, 17 Oct 2022 20:05:48 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id 4Nc/F3yZTWOB1gAA9RJhRA (envelope-from ) for ; Mon, 17 Oct 2022 20:05:48 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id E8C7713AE3 for ; Mon, 17 Oct 2022 20:05:47 +0200 (CEST) Received: from localhost ([::1]:57310 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1okUUl-0007qg-3r for larch@yhetil.org; Mon, 17 Oct 2022 14:05:47 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:32866) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1okUTm-0006QF-EJ for emacs-orgmode@gnu.org; Mon, 17 Oct 2022 14:04:46 -0400 Received: from mout02.posteo.de ([185.67.36.66]:38757) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1okUTj-0007rX-6n for emacs-orgmode@gnu.org; Mon, 17 Oct 2022 14:04:45 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 01157240101 for ; Mon, 17 Oct 2022 20:04:40 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1666029881; bh=6ON3hVnw9e8UFdLGO7Aj8ulDnylqm2ONI7Hn55FsB18=; h=From:To:Cc:Subject:Date:From; b=PI5zmI8b4lwjqdE2zDMy+WqtL59qN1PpXieY6IFsQDYtiPjOBSFzkNw+0DfGYAmrT bG+vaqhXLPk/gf2g6knYuALaGF6K4Mmv+ZL0o+5nNfBaYsOOZklgKshycApK3eV4vZ EBdE+5LMaDdvTC846LybydigZgjmhs6PO2jumIu+Yu4g1IR5HcYfotIq6nTbWd9KW1 KohP3aiSkACL7mQhFFi6Wz6Hv0n78f9rId2PkAnLBYNeg0GPbVWt4iTvptUtKXCRCI IVpHZ51iCUL0PfLTHBSGVVwqKrAuGrCNB7qZmxuX7CqpFpZa9mZ10GR6fDRYTWN8Cs ARaW7+YqJh+FA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4MrlJ45B5Gz9rxR; Mon, 17 Oct 2022 20:04:36 +0200 (CEST) From: =?utf-8?Q?Juan_Manuel_Mac=C3=ADas?= To: Max Nikulin Cc: emacs-orgmode@gnu.org, Ihor Radchenko , Vikas Rawal Subject: Re: Line breaks and brackets in LaTeX export References: <875ygk6a8z.fsf@posteo.net> <87a65vitbz.fsf_-_@posteo.net> <87edv6izx4.fsf@localhost> <8735bmelgu.fsf@posteo.net> <878rlecx49.fsf@posteo.net> Date: Mon, 17 Oct 2022 18:04:34 +0000 In-Reply-To: (Max Nikulin's message of "Mon, 17 Oct 2022 23:46:17 +0700") Message-ID: <874jw2conh.fsf@posteo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.67.36.66; envelope-from=maciaschain@posteo.net; helo=mout02.posteo.de 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1666029948; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=RKf5NIVtdQvGhptP/QMgxBEt0RIl/LuUbuCgwga/sds=; b=NBmluh2L2XGJ+cEOCA64gpnkaW6Muaa44Y2NpCgbU7VyMP3OJ1xZIqTJTjCAhzbNTRg+d6 r826y81UFku3eIfQU9AujuhZlmbBznMNRhYcPNErRhBqMo4OtFewh6Uwbm3z8UdAe72otB q4SIQgQhkZfKV5foMN867GApZdxHb2l1Lh7t8KThRNI0vy2M1VdKknaUL5HmJn+a36TPtL gcv41DeVz+v2jWfoHnCemOZ10KpbxxYVgDvSXj3yjT5DMVmcg/srG0MBhwmziTvtoDC3Hm jbvknD2v7LhwrXHIvx4lkDHQU6tcYQ/sgct5hY7NlB2AvsBb6GbE6A1cKb8maw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1666029948; a=rsa-sha256; cv=none; b=inzRyA8UXO0MQz1LatQWopZ7u1mYXaw6MDaEtsZVlYTTCKd/rHlvIJwZk0Dfzhtz31e0kZ uBh1MmCp7mdgTc/dNi1HcpCPKS51KHPe4DYdEFCKKHc+8k7NfaLbPn9bDOT4w2LW99cZNg 5WZsh6RxAKpdvRQoRzsWqvV0zWu/eCT9UW/v4w9Z+IWGaqXF5eNbAMAeEYUn7jFHv/OrrI nbcV5903N3Y62T5/62/dixqUVFWX/JuruImmpNs2JJ2wsDqoTVcYHYGIwAXdP8IiiUHRnL z0nd8tnRIzvtp3LdqPCBZSy1HuXF1Az6cFWMUCT4ddsrCBk27fAKz75mzZsgow== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=PI5zmI8b; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -2.62 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=PI5zmI8b; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: E8C7713AE3 X-Spam-Score: -2.62 X-Migadu-Scanner: scn1.migadu.com X-TUID: BWbDEUGhZZci Max Nikulin writes: > On 17/10/2022 22:01, Juan Manuel Mac=C3=ADas wrote: >> \documentclass{article} >> \usepackage{tabularray} > > LaTeX I have installed is too old for this package. It is marked as > "Experimental LaTeX3", so I am unsure, maybe you have found a bug in > this package. > https://ctan.org/pkg/tabularray As I said, I don't use this package. Once I wanted to start using it, because it has many interesting features, but I gave up on it because this package does not (at the moment) have support for the CMYK color space (necessary for print publication) with the xcolors package. Maybe it's a bug, but the situation is that compiling the copied examples as they are in the package manual, the result is correct (as it is also shown in the manual); but adding an unexpected element (an \empty on the last line) produces a bad result. Since you can't test the package, I've taken this screenshot: https://i.imgur.com/jkSHUMP.png I think there is a tabularray user on the list, Vikas Rawal. In fact, I also remember that I provided a patch so that he could use this package in Org (https://list.orgmode.org/CALtzAB1yM+uG_xHghCxTLRX5mgbzNvT5+PO=3DDuaBB28nCs= VqEA@mail.gmail.com/). I've cc'd him in case he wants to join the discussion. > You believe that an issue with brackets is extremely rare. It may be > true for humanitarian texts. For some users it may be a constant > source of pain e.g. in the case of interval notation as [a,b]. I have > already mentioned tables generated by code blocks, not typed directly. > I can not say that I often need to export my notes, but I was afraid > that I will be bitten by this bug because I may try to put dates close > to left margin: > > - Something\\ > [2022-10-17 Mon] > > By default dates wrapped into \textit, but it may be customized to > just "%s". > > Selectively adding some workaround require complete reimplementation > of exporters. I have some curiosity concerning pandoc approach, but I > am unsure if I will reserve some time to read its code. I see. If the selective solution is going to involve rewriting the exporters, I find that it is unaffordable in the present circumstances. It's a shame, because pandoc's solution seems ideal to me. What I couldn't say is how pandoc does it and if it does it whenever expected, because I use very little pandoc. > I found \empty when I was looking for an approach with minimal > overhead. I expect that e.g. \\[0pt] may have higher performance > penalty since it is expanded to several commands. When the idea with > "\\\relax" failed I was choosing between "\\{}" and "\\\empty". I > decided that the latter minimizes risk to add spurious space. Assuming that there is currently no alternative to the non-selective solution, and that, as you say, the presence of brackets may be more common than I initially expected, if I had to choose between \empty and [0pt], I would say that [0pt] is the safest, as it is an expected argument to \\ and equals the default space. I can't think of any unexpected results from this, but of course, it also depends on there being no package redefining \\ with another argument structure on its own. I think it would be a bad idea for a package developer, but LaTeX (and the LaTeX packages) is horribly unpredictable. Best regards, Juan Manuel=20