all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Export to html and latex fails on these (relatively common) strings [8.2.10 (8.2.10-16-g4c37a9-elpa @ /home/mzimmermann/.emacs.d/elpa/org-20141110/)]
Date: Fri, 14 Nov 2014 10:42:25 +0100	[thread overview]
Message-ID: <87zjbut8xq.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r3x6dtdl.fsf@gmx.us> (rasmus@gmx.us's message of "Fri, 14 Nov 2014 10:27:34 +0100")

Rasmus <rasmus@gmx.us> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> IMO, it is worth pondering if we should drop the defective support for
>> table.el tables in Org.
>
> Fine with me.  Last I checked I was not able to get the output of
> tabel.el tables to be satisfying (e.g. I think I gave up on having them
> follow booktabs when exporting to LaTeX).
>
> What are the advances of table.el?  Multicolumns and multiline row?

Basically, yes.

Note that dropping support for table.el tables in Org doesn't mean it is
impossible to add them in an Org buffer: these tables are pretty much
major mode agnostic.

However, M-q will fill them, C-c ' will not edit them and export will
have to be done by hand, using features explained in "table.el"
comments.


Regards,

  reply	other threads:[~2014-11-14  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 22:45 Bug: Export to html and latex fails on these (relatively common) strings [8.2.10 (8.2.10-16-g4c37a9-elpa @ /home/mzimmermann/.emacs.d/elpa/org-20141110/)] Milan Zimmermann
2014-11-14  8:30 ` Nicolas Goaziou
2014-11-14  9:27   ` Rasmus
2014-11-14  9:42     ` Nicolas Goaziou [this message]
2014-11-14 10:35       ` Rasmus
2014-11-14 15:51   ` Milan Zimmermann
2014-11-14 15:55     ` Milan Zimmermann

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

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

  git send-email \
    --in-reply-to=87zjbut8xq.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.