From: John Hendy <jw.hendy@gmail.com>
To: Daniel Bausch <DanielBausch@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Way to replace normal tabular env with booktabs?
Date: Fri, 13 Jan 2012 13:03:36 -0600 [thread overview]
Message-ID: <CA+M2ft_a-JPm8E4T-TnMgOMVGzyUn5GbvO=Uv27q+B4RWn8-7A@mail.gmail.com> (raw)
In-Reply-To: <201201131932.54357.DanielBausch@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
On Fri, Jan 13, 2012 at 12:32 PM, Daniel Bausch <DanielBausch@gmx.de> wrote:
> Hello!
>
> > On a usage note, I was surprised that the patch causes automatic
> insertion
> > of top and bottom rules even when the org table doesn't use ascii
> > top/bottom rules. In fact, if you use "|-" to put ascii rules on an org
> > chart using this patch, you get double rules.
>
> Disclaimer: I did not test this at all, but am interested in a convenient
> booktabs support, too.
>
> I think it is reasonable to put the top and bottom rules automatically, as
> booktabs somewhat defines that as the intended look. So it would be
> redundant
> to require a |- on top and bottom for all tables on the org side. I even
> think that org tables with top and bottom rules do not look good, because
> the
> vertical lines do not stop at the horizontal lines (from a visual point of
> view). This way it looks like is a very small empty table line above and
> below the table.
>
>
I can see that point. I guess I was just surprised given the org-mode
default.
Perhaps it is just a preference with the look. I don't mind having them
"closed in" by ascii rules. In any case, what probably *shouldn't* happen
are double rules if someone by habit puts rules on their org table with |-.
That's the current behavior.
Best regards,
John
> Daniel
>
>
[-- Attachment #2: Type: text/html, Size: 2033 bytes --]
next prev parent reply other threads:[~2012-01-13 19:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 18:50 Way to replace normal tabular env with booktabs? John Hendy
2012-01-12 20:12 ` Thomas S. Dye
2012-01-12 23:19 ` John Hendy
2012-01-13 0:01 ` Thomas S. Dye
2012-01-13 13:21 ` John Hendy
2012-01-13 14:52 ` Niels Giesen
2012-01-13 15:35 ` John Hendy
2012-01-13 15:39 ` Carsten Dominik
2012-01-13 15:48 ` John Hendy
2012-01-13 18:32 ` Daniel Bausch
2012-01-13 19:03 ` John Hendy [this message]
2012-02-03 23:24 ` John Hendy
2012-02-04 15:54 ` Nicolas Goaziou
2012-02-08 13:17 ` Niels Giesen
2012-02-08 22:32 ` Nicolas Goaziou
2012-02-09 19:50 ` John Hendy
2012-02-09 19:57 ` Thomas S. Dye
2012-02-09 20:20 ` John Hendy
2012-02-09 20:24 ` Nick Dokos
2012-02-09 20:27 ` Thomas S. Dye
2012-02-09 20:29 ` Nick Dokos
2012-02-09 21:09 ` John Hendy
2012-02-09 21:26 ` John Hendy
2012-02-09 22:04 ` Thomas S. Dye
2012-02-13 22:13 ` John Hendy
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='CA+M2ft_a-JPm8E4T-TnMgOMVGzyUn5GbvO=Uv27q+B4RWn8-7A@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=DanielBausch@gmx.de \
--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).