From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.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 cP5lCOncT2MEYwAAbAwnHQ (envelope-from ) for ; Wed, 19 Oct 2022 13:18:01 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id cEFGCOncT2MvbgEAauVa8A (envelope-from ) for ; Wed, 19 Oct 2022 13:18:01 +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 CFD6E695F for ; Wed, 19 Oct 2022 13:18:00 +0200 (CEST) Received: from localhost ([::1]:60394 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ol75E-00074m-0b for larch@yhetil.org; Wed, 19 Oct 2022 07:18:00 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:45656) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ol73h-00074D-Es for emacs-orgmode@gnu.org; Wed, 19 Oct 2022 07:16:30 -0400 Received: from mout01.posteo.de ([185.67.36.65]:41705) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ol73e-0002gN-0p for emacs-orgmode@gnu.org; Wed, 19 Oct 2022 07:16:25 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 3A74124002A for ; Wed, 19 Oct 2022 13:16:19 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1666178179; bh=OY4it0gLHRqVkdzq6nL0MZQ4QlBHRois0JovFyHNZp0=; h=From:To:Cc:Subject:Date:From; b=MKihHQ+R8d2TwFFYrKafgvm4ZkkfDu9WIjM2kdDhqRydeWr1vi00FuGblD5yFbDuk bdWIW4AsCj2uFYyknUIo+qFftIg6Zoo2wo8ocYOlm4daw+2dlp7cOysUN0zCGSx/0x CeiTzjH1ip5CNfDsrwtVCtjSTwBzUaAB6gxqGM5cXQa5khAoXRvr4mfGB/bt2s2X/k ZK8qhUuyfqBfmwLMQWn0Liyq4gx2D2Fv4tsMm40F6KDi54GUKpG7eh2iOgoWwKcCBk lelPK8fEPXRK0lbeFZLBUam+edFtdkr7y0wpOOG8qvahEWiHPBL4aSiOFCfZ6wV7wf bysvGjL7AsKdg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Msp814Dgrz9rxH; Wed, 19 Oct 2022 13:16:17 +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> Date: Wed, 19 Oct 2022 11:16:15 +0000 In-Reply-To: (Max Nikulin's message of "Wed, 19 Oct 2022 12:11:11 +0700") Message-ID: <87wn8wysg0.fsf@posteo.net> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.65; envelope-from=maciaschain@posteo.net; helo=mout01.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, 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=1666178280; 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=7lwsEeAAx/b9qQLJIHtVExDAzuG9U404n3j6L1FdqPI=; b=jZw0RyW5m1FnahYOrUXcv7Xt8Q46AJbI/6WxAXST9vp7Ylj5A7dlmuHipdrAc9jIJmLFzG 4f/Jt+lg3s8HOFn7ASX9dL3MH/J0Vp+L4t5cG4Tgz2NRM2blJMoC8IvKlP7DXhZwrrXh1O Tu03VpqdmekTIWFxbxEGluvH/kUFteyr+XNqXss25IWlXGSFXt5a/jcQV4iTZUID3YHelR H2uwHeitx+sOF1sOxJJDBfL762P91QsEfrrg0uWskw3rWvIm3QNsPQ2PG76vMA5WakogA+ uTVJ5i+tLkDTN6urO0FqYJiiUhNaMJVRYoif09tYJywTaCankTMkUbUh7kr+xg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1666178280; a=rsa-sha256; cv=none; b=W/QEFDxQcxl2TxDW0jXMOQPfNc1sxgUAvDUS9FMwOXd9awI68gTe5/JWpiw5+YBIbj5tbB Kn7FJ0/cILWZ/pmcquj7j3UhrGHoB1+Vnger8qo71hXNd3zbM9/R+flLEq1j+inZNPalg5 aIdvkbvXeAaYEmHEhknEToDR8PdmcYp/6ZMrU0OX+Sa5xyunLoHwvuG/5Ge34TNXp8kOjw +XltK/v11rI7ncOxCOjMmYG2pR+uoSCe9Bh1kR1z5p9VakwKHHtlre9hMssgS2qkTj5nCp eNIfxo+21UURK06jH3aRdtXr23FNp0g8Ae0vQ8GBRD6GM2ikB6eHZYWkQzhyKw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=MKihHQ+R; 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: -3.93 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=MKihHQ+R; 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: CFD6E695F X-Spam-Score: -3.93 X-Migadu-Scanner: scn0.migadu.com X-TUID: 9YK5EV1s5Uma Max Nikulin writes: > Another recipe should be used: > > | / | < | > | > | | a | b @@latex:\rule[-1em]{0pt}{1em}@@ | > | | c | d | > > I believe that a more convenient way to override [0pt] to some other > length for particular row should exist, but I have no idea which > syntax should be used. I think this new recipe you propose works fine, although I haven't done a thorough test yet. In principle, it shouldn't be a problem. By the way, now I remember that the package verse adds a series of extra arguments to \\ (p. 6 in the documentation: https://www.ctan.org/pkg/verse). As a user, the only way I can think of to add arguments instead of [0pt] or \empty is by using a small export filter to act on the final output. Perhaps putting something like !!new-argument!! on the affected row/verse/line to guide the filter. > As to tabulararray, I still consider it as an experimental package. > Perhaps I will install a more modern container. I am curious what code > handles \\[0pt]. Likely I should read docs to get impression related > to design goals and approaches to implement them. The bug tracker of > the project looks like an appropriate place to ask a question > concerning \\ variant safe for dumb exporters. Keep in mind that tabularray is a latex3 package and, in principle, everything that is latex3 is here to stay. Certainly, it is a blessing compared to the classic tabular environments, because it is tremendously versatile. That is why it already has a significant number of users: https://tex.stackexchange.com/questions/tagged/tabularray And Org already provides what is necessary to use its syntax. I've had a first look at tabularray.sty, but I'm not familiar enough with the new LaTeX 3 syntax and, frankly, I'm lost... 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. > For a while I have the following question. Is \\{} have the same > effect on tabularray parser as \\\empty? Throw an error before \hline.