emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: torys.anderson@gmail.com (Tory S. Anderson)
To: Skip Collins <skip.collins@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: What to use for tables with lengthy text in cells?
Date: Thu, 05 Mar 2015 11:56:50 -0500	[thread overview]
Message-ID: <87egp3l6wd.fsf@gmail.com> (raw)
In-Reply-To: <CABUh-74L_2j_GMrWMeN6wex1v9ZHB4-YDwvbKLXS28d4VeE0KA@mail.gmail.com> (Skip Collins's message of "Thu, 5 Mar 2015 11:28:03 -0500")

Not a bad idea, but this would be incompatible with the existing useof horizontal lines to separate sections and export to visual lines, right? 

Skip Collins <skip.collins@gmail.com> writes:

> Here's another suggestion. There could be an optional org table mode
> in which horizontal lines are used to separate rows:
>
> | Lorem ipsum dolor sit amet,         | foo |
> | consectetur adipiscing elit. Sed    |     |
> | sit amet luctus sapien. Phasellus   |     |
> | malesuada, ipsum et hendrerit       |     |
> | mattis, neque neque sodales risus,  |     |
> | hendrerit consectetur enim ipsum eu |     |
> | felis.                              |     |
> |-------------------------------------+-----|
> | Vestibulum ante ipsum primis in     | bar |
> | faucibus orci luctus et ultrices    |     |
> | posuere cubilia Curae; Nulla dictum |     |
> | iaculis sodales. Sed elementum      |     |
> | semper leo, venenatis lacinia odio  |     |
> | eleifend vitae. Aliquam lectus      |     |
> | felis, tempor nec lacus ut,         |     |
> | consequat tincidunt nisl.           |     |
> |-------------------------------------+-----|
> | Fusce eu nunc sit amet orci         | baz |
> | lobortis accumsan. Vivamus laoreet  |     |
> | ante pellentesque, scelerisque      |     |
> | tellus nec, ultrices nibh. Etiam    |     |
> | scelerisque lobortis erat, in       |     |
> | consectetur nisi tincidunt a. Duis  |     |
> | eu est elit. Pellentesque fringilla |     |
> | gravida ligula, non convallis       |     |
> | ligula viverra sollicitudin.        |     |
>
> Perhaps adding the required machinery to allow in-cell paragraph
> filling would not be too difficult?

  reply	other threads:[~2015-03-05 16:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 21:12 What to use for tables with lengthy text in cells? Matt Price
2015-03-02 21:25 ` Rasmus
2015-03-02 23:16 ` Charles C. Berry
2015-03-03 18:08   ` Charles C. Berry
2015-03-03 19:19     ` Tory S. Anderson
2015-03-05 15:13       ` Jude DaShiell
2015-03-05 16:28         ` Skip Collins
2015-03-05 16:56           ` Tory S. Anderson [this message]
2015-03-05 17:31             ` Skip Collins
     [not found]               ` <CAN_Dec8Tt2w4KarPXk0fW2F9GXXczYNBuRkzQpirk83dDgv=SQ@mail.gmail.com>
2015-03-06 16:34                 ` Skip Collins
2015-03-06 16:48                   ` Tory S. Anderson
2015-03-06 17:47                     ` Skip Collins

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=87egp3l6wd.fsf@gmail.com \
    --to=torys.anderson@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=skip.collins@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).