From: Nathan Furnal <nathan_furnal@hotmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug on LaTeX table export
Date: Fri, 14 Oct 2022 11:40:26 +0000 [thread overview]
Message-ID: <DB4PR10MB623823870715C406559E02C78E249@DB4PR10MB6238.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87zgdyy7p6.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
Wow that's cool, sorry for not finding the original report then!
Thanks for your work =)
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Ihor Radchenko <yantar92@gmail.com>
Sent: Friday, October 14, 2022 1:18:29 PM
To: Nathan Furnal <nathan_furnal@hotmail.com>
Cc: emacs-orgmode@gnu.org <emacs-orgmode@gnu.org>
Subject: Re: Bug on LaTeX table export
Nathan Furnal <nathan_furnal@hotmail.com> writes:
> I think I found a bug in the latest snapshots of org. When an org-mode table is exported to LaTeX, a `\relax` command is now added after each new line (`\\`), before each `\hline`, this breaks LaTeX
> compilation when tables are involved. I could confirm this on a small table in a nearly empty document without any specific LaTeX class used but the one used in org-mode.
Thanks for reporting!
We have already fixed this. See
https://list.orgmode.org/87k053yw2e.fsf@localhost/T/#mcd29b958a0e0f7fcf51d67c4cbf4d27f9328acce
--
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>
[-- Attachment #2: Type: text/html, Size: 2331 bytes --]
prev parent reply other threads:[~2022-10-14 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 19:01 Bug on LaTeX table export Nathan Furnal
2022-10-14 11:18 ` Ihor Radchenko
2022-10-14 11:40 ` Nathan Furnal [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=DB4PR10MB623823870715C406559E02C78E249@DB4PR10MB6238.EURPRD10.PROD.OUTLOOK.COM \
--to=nathan_furnal@hotmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).