From: Ihor Radchenko <yantar92@posteo.net>
To: aurelien@francillon.net
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Org export to latex/pdf with longtabu adds extra line (\\) when #+NAME is present but no #+CAPTION [9.8-pre (release_9.7.11-145-g28b631 @ /home/aurel/admin/org-bugreport/org/lisp/)]
Date: Thu, 03 Oct 2024 17:56:07 +0000 [thread overview]
Message-ID: <87r08xcbpk.fsf@localhost> (raw)
In-Reply-To: <ZvSBf2tBM4Udws9l@crashtoo>
> when exporting org table to latex/pdf with longtabu environment the
> generated latex includes extra \\ if the #+NAME tag is present,
> inserting an needed row, the resulting table look ugly in some cases.
Thanks for reporting!
Confirmed.
> The extra \\ seem to be added at ox-latex.el line 3937 (current git head):
>
> (concat (and fontsize (concat "{" fontsize))
> (format "\\begin{%s}%s{%s}\n" table-env width alignment)
> (and above?
> (org-string-nw-p caption)
> (concat caption "\\\\\n")) ; <= HERE
> contents
> (and (not above?)
> (org-string-nw-p caption)
> (concat caption "\\\\\n"))
> (format "\\end{%s}" table-env)
> (and fontsize "}"))))
>
> When I remove the "\\\\" the generated code is correct, but I suspect
> this is may be useful in some other cases and this may not be a suitable
> fix?
Yes, the problem occurs where you pointed.
The "\\\\" part is present there from the very first commit in ox-latex.
I am not sure why it is there.
What happens if you remove "\\\\" part from the code and play around
with tables with/without #+caption/#+name?
--
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>
prev parent reply other threads:[~2024-10-03 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 21:32 [BUG] Org export to latex/pdf with longtabu adds extra line (\\) when #+NAME is present but no #+CAPTION [9.8-pre (release_9.7.11-145-g28b631 @ /home/aurel/admin/org-bugreport/org/lisp/)] Aurélien Francillon
2024-10-03 17:56 ` 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:
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=87r08xcbpk.fsf@localhost \
--to=yantar92@posteo.net \
--cc=aurelien@francillon.net \
--cc=emacs-orgmode@gnu.org \
/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).