emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH v2] Re: [BUG] Tables with square brackets do not compile in PDF (latex) export [9.5 (release_9.5-59-g52e6f1 @ /home/sjt015/repo/emacs/lisp/org/)]
Date: Tue, 11 Oct 2022 11:36:52 +0800	[thread overview]
Message-ID: <874jwbuj3f.fsf@localhost> (raw)
In-Reply-To: <ti1had$802$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

> Ihor, I have tried your patch (v2). With a tiny test file it works as 
> expected. I have not managed to add some text immediately after \relax 
> to break this command.
> ...
> Reading with more attention, I do not think that second constant really 
> makes the code more clear. I had a hope that it is enough to introduce a 
> single constant, but it seems it is not the case. I did not expect that 
> newline should not be added e.g. planning export handler. Perhaps it is 
> better to commit v1.
> ...
> A minor naming inconsistency: "line-break" and "linebreak".

Thanks for testing!
I applied the version 1 of the patch onto main changing the
org-latex-linebreak-safe to org-latex-line-break-safe.



Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

      reply	other threads:[~2022-10-11  3:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 16:16 [BUG] Tables with square brackets do not compile in PDF (latex) export [9.5 (release_9.5-59-g52e6f1 @ /home/sjt015/repo/emacs/lisp/org/)] Stewart Thomas
2021-11-13 14:57 ` Max Nikulin
2022-10-07  8:31   ` [PATCH] " Ihor Radchenko
2022-10-07 11:34     ` Max Nikulin
2022-10-08  5:17       ` [PATCH v2] " Ihor Radchenko
2022-10-10 16:30         ` Max Nikulin
2022-10-11  3:36           ` Ihor Radchenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874jwbuj3f.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).