From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id aBAeLc99UWM7zQAAbAwnHQ (envelope-from ) for ; Thu, 20 Oct 2022 18:56:47 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id UDgeLM99UWMTOwEAG6o9tA (envelope-from ) for ; Thu, 20 Oct 2022 18:56:47 +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 3B0AC822B for ; Thu, 20 Oct 2022 18:56:47 +0200 (CEST) Received: from localhost ([::1]:35510 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1olYqX-0006lF-Su for larch@yhetil.org; Thu, 20 Oct 2022 12:56:42 -0400 Received: from [::1] (helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1olYqH-0004jx-Sm for larch@yhetil.org; Thu, 20 Oct 2022 12:56:25 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:51518) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1olYpQ-0002lh-7B for emacs-orgmode@gnu.org; Thu, 20 Oct 2022 12:55:35 -0400 Received: from mout02.posteo.de ([185.67.36.66]:57605) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1olYpN-0003HN-4z for emacs-orgmode@gnu.org; Thu, 20 Oct 2022 12:55:31 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id E3258240105 for ; Thu, 20 Oct 2022 18:55:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1666284925; bh=tJWazat39/6cumOM984YU7y24kBTI7yN1ZksrY2Isy8=; h=From:To:Cc:Subject:Date:From; b=R9P6CFD+P01EsjWLryFxVS9F5WPaPInjBnivYnGNOujrbG0oIwA2yKPW3IF9Mlmm4 1AmPlrx496tLkIl2KbIz3cbRE8m3Vwj8KkHHHUXq/gjxRseYz/n1z2l6bewsZJirui MSmzGpFSb0dAHsYrHY5PBrwRdnq7YgpXW3M9NTyPhfn59i94qcnoU7oEpkFMytdQW3 ICM/jiMpmC6PfS6Cui61AgeL07YRqagnj+UboQQXsXJe3yWNcj43j2NtlxwPl1RsXV wDKWSztO1+hrJdTxFkboLN1z3uql6mrT27hIfsL6PZh2yvzUACq5jJxxG1n5xCEBYA t1ofD1lMt+etg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4MtYcs0NK9z9rxS; Thu, 20 Oct 2022 18:55:25 +0200 (CEST) From: =?utf-8?Q?Juan_Manuel_Mac=C3=ADas?= To: Max Nikulin Cc: emacs-orgmode@gnu.org, Ihor Radchenko 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> <874jw2conh.fsf@posteo.net> <87edv5hhgb.fsf@localhost> <87o7u9rz1a.fsf@posteo.net> <87o7u8cvox.fsf@localhost> <87wn8wysg0.fsf@posteo.net> <87lepcyozt.fsf@posteo.net> <65a1c205-cd18-4abe-b36d-a93763d7f5e8@gmail.com> Date: Thu, 20 Oct 2022 16:55:22 +0000 In-Reply-To: <65a1c205-cd18-4abe-b36d-a93763d7f5e8@gmail.com> (Max Nikulin's message of "Thu, 20 Oct 2022 00:07:54 +0700") Message-ID: <87tu3ywi2t.fsf@posteo.net> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.66; envelope-from=maciaschain@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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_MED=-2.3, 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=1666285007; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=S736MaA+uTm23dvCq34WIv4WJTPQ4WsZr1Zzgu6INb4=; b=THBb2/fjEmIy/U5l0tpjaLxQWYTNog0aZJpQe5FPccVtD3pjrqHP1mRviQ7JWSwJIKlMIm X/Uq8Ml0K5V+3IL7pZFA9rbVVA3YEesD+ninlzaAJfcDeM5YdERgSLO7rPojPr4tY+gjJN JRn6L+0IQOrpL/Q6j8m0r/VERCplu/YpZ8cyjuoJZQpNGYstaJ6hlSMSOynMgpACW7wLw9 KqJltuSNtM7FB5p4EbnU9GoL1jSe5d6VSLyv4pnbZBCLEgr9nVYgwrtgyQrXZlvZ/Ca5Aa QNlY3lmGJtuZM9LqaxDssqjpKTF5rgvMH7ZKmDSwl2iCKL8oCbLQ+R9ctE5inw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1666285007; a=rsa-sha256; cv=none; b=OH/Z25UtZyay+epU4vbzZnxF6w84yffJ+2ciQEjOXSkB4A4Q/yVSqh828tl4hl3xZLjFrj TKC7OXuRRIok+11fBGgLJvnnMYpB8GgJTYHo9ggVESbvQo+AmwilVuyuiebl4uFKmmUb0h JN7MiW0CcJOrCGeh0PxeyW9JJGnlp9d/I3ajXHt6aRleTtPDJ0mO3ubgCi0zupMg6W+4Er 0sc3vkFF4UHIK+0S39Xe1Uddh8H4Cf0Z5KwC5/RuYThNgS+tDKtNdNGn3KpItGre4Jvty8 O12E8dK2QI0ut3jEaJf70rmsI2OwO7lZcDzFJz44sfpzlJZ1itfGnZDBewa/vg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=R9P6CFD+; 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: -5.73 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=R9P6CFD+; 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: 3B0AC822B X-Spam-Score: -5.73 X-Migadu-Scanner: scn0.migadu.com X-TUID: WqPQRyCY0JLk Max Nikulin writes: > I have started a discussion requesting for a \\-like command without > optional arguments. Maybe somebody will suggest a better workaround > instead. > https://github.com/lvjr/tabularray/discussions/321 I've had a look at the thread. What do you think of that \NewTableCommand\empty{} workaround mentioned at https://github.com/lvjr/tabularray/discussions/321#discussioncomment-3920957? Since the \empty option only has problems in tabularray, maybe we could keep it, and put in the documentation some recommendations for tabularray users. I imagine they would have to add a @@latex:\empty@@ before each row that follows a line. A bit laborious, I'm afraid. Another possibility that occurs to me is that the string reserved for \empty, [0pt], etc., is a defcustom, with a value of \empty by default. So the user would choose what suits him best. By the way (a little digression), I was curious to see if these age-old LaTeX problems with line breaking exist in ConTeXt as well. Since I'm completely unfamiliar with ConTeXt, the quickest thing to do has been to see what code ox-context returns for the org tables. The answer is that there are no such problems, and one can safely put a square bracket at the beginning of a row. It is also true that the table syntax in ConTeXt is radically different from that in LaTeX. And there is also no problem if I put @@context:a\[b]@@. Some screenshots: https://i.imgur.com/2k1TaU9.png https://i.imgur.com/8i9qlEH.png Many times I've been tempted to give ConTeXt a try, but I've always run into two things: ConTeXt's perennially experimental status and a horrible lack of documentation. In addition, backward compatibility is not usually respected, since ConTeXt, although it is free software, does not have community development as a priority, but rather the company behind it, Pragma. >> I've tried all the packages involved in tables that I can think of >> (longtable, siunitx, tabularx, booktabs, array, and I don't know if I >> forgot any) and in all of them the \empty solution works fine. It seems >> that tabularray is the black sheep here. > > I think tabularray is unique with a regexp-based parser. I had a hope > that new approach does not allow newline between \\ and its arguments, > but unfortunately compatibility with older code is preserved in this > aspect. > > From LaTeX companion I remember supertabular as an alternative for > longtable, but I am unsure if it is alive yet. True, I had forgotten about this package (I don't think I've ever used it). It looks like it has a 2020 new version: @manual{supertabular, title = {The \texttt{supertabular} package}, subtitle = {A multi-page tables package}, author = {Johannes L. Braams}, date = {2020-02-02}, version = {4.1g}, license = {lppl1.3c}, url = {https://mirror.ctan.org/macros/latex/contrib/supertabular}, pkgurl = {https://ctan.org/pkg/supertabular}, } (bibtex entry obtained from: https://www.ctan.org/pkg/ctan-bibdata)