From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Amos Bird <amosbird@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Disable fontification when exporting tables
Date: Sat, 30 Sep 2017 09:36:39 +0200 [thread overview]
Message-ID: <87ing0ljso.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87a81drnsv.fsf@gmail.com> (Amos Bird's message of "Sat, 30 Sep 2017 09:13:36 +0800")
Hello,
Amos Bird <amosbird@gmail.com> writes:
>> - what are you trying to export?
>
> an Org table like this:
>
>
> | QueryID | SQL Text | Query Time (Seconds) | Query Time Hot (Seconds) |
> |---------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------+--------------------------|
> | Q0 | SELECT cab_type, count(*) FROM trips_log GROUP BY cab_type; | 10.14 | 11.57 |
> | Q1 | SELECT passenger_count, avg(total_amount) FROM trips_log GROUP BY passenger_count; | 12.00 | 6.27 |
> | Q2 | SELECT passenger_count, toYear(pickup_datetime) AS year, count(*) FROM trips_log GROUP BY passenger_count, year; | 10.45 | 7.23 |
> | Q3 | SELECT passenger_count, toYear(pickup_datetime) AS year, round(trip_distance) AS distance, count(*) FROM trips_log GROUP BY passenger_count, year, distance ORDER BY year, count(*) DESC; | 13.03 | 10.80 |
OK.
>> - to what back-end?
>
> ODT and HTML
OK.
>> - what is the exact problem?
>
> I'd like to export this table with *:nil ^:nil options while exporting other subtrees with *:t ^:t.
This is not my question. You are explaining me how you are trying to
proceed. I want to know what it the problem you are trying to solve.
Anyway, it seems you are conflating fontification in the Org buffer and
export. I guess there is no issue related to export in this thread.
> I tried surrounding the table with example block and src block but
> both look bad after exportation.
Of course. I didn't know you were exporting an Org table.
However, you could add verbatim markup
=SELECT cab_type, count(*) FROM trips_log GROUP BY cab_type;=
but, again, since I don't know exactly what the issue is, I may be wide
of the mark.
> characters when exporting.
I never suggested that.
> I also tried changing _ to \under{} and * to \asc{} but it doesn't look well in the Org buffer.
>
> I did turn on org-toggle-pretty-entities but it changes the appearance
> of other subtrees which I don't want to.
Maybe Org mode is not the appropriate mode for the task?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-09-30 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 8:29 Disable fontification when exporting tables Amos Bird
2017-09-28 18:51 ` Nicolas Goaziou
2017-09-29 2:08 ` Amos Bird
2017-09-29 19:38 ` Nicolas Goaziou
2017-09-30 1:13 ` Amos Bird
2017-09-30 7:36 ` Nicolas Goaziou [this message]
2017-09-30 7:43 ` Amos Bird
2017-09-30 7:49 ` Nicolas Goaziou
2017-09-30 7:56 ` Amos Bird
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=87ing0ljso.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=amosbird@gmail.com \
--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).