From mboxrd@z Thu Jan 1 00:00:00 1970 From: Skip Collins Subject: Re: What to use for tables with lengthy text in cells? Date: Thu, 5 Mar 2015 12:31:24 -0500 Message-ID: References: <87oao9oplu.fsf@gmail.com> <87egp3l6wd.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0158c7c21e9fab05108df141 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45244) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YTZcn-0007T2-20 for emacs-orgmode@gnu.org; Thu, 05 Mar 2015 12:31:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YTZcg-00059A-MR for emacs-orgmode@gnu.org; Thu, 05 Mar 2015 12:31:53 -0500 Received: from mail-lb0-x22c.google.com ([2a00:1450:4010:c04::22c]:34231) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YTZcg-00058p-A4 for emacs-orgmode@gnu.org; Thu, 05 Mar 2015 12:31:46 -0500 Received: by lbiv13 with SMTP id v13so34299472lbi.1 for ; Thu, 05 Mar 2015 09:31:45 -0800 (PST) In-Reply-To: <87egp3l6wd.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Tory S. Anderson" Cc: Org Mode --089e0158c7c21e9fab05108df141 Content-Type: text/plain; charset=UTF-8 Yes, it would be incompatible. But there could be a mechanism to enable the multi-line mode on a per-table basis. For display and grouping purposes, horizontal lines could still be allowed by adding two consecutive lines: |-------------------------------------+-----| |-------------------------------------+-----| Or another character could be used for the line separator: |=====================================+=====| 2015-03-05 11:56 GMT-05:00 Tory S. Anderson : > > 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 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? --089e0158c7c21e9fab05108df141 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes, it would be incompatible. But there could be a mechan= ism to enable the multi-line mode on a per-table basis. For display and gro= uping purposes, horizontal lines could still be allowed by adding two conse= cutive lines:
|---------------------= ----------------+-----|
|-------------------------------------+-----|

Or another character could be used for the line separator:
<= font face=3D"monospace, monospace">|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+= =3D=3D=3D=3D=3D|


2015-03-05 11:56 GMT-05:00 Tory S. Ander= son <torys.anderson@gmail.co= m>:
>
> Not a bad idea, but this would be incompatible w= ith 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 m= ode
> > in which horizontal lines are used to separate rows:
&g= t; >
> > | Lorem ipsum dolor sit amet, =C2=A0 =C2=A0 =C2=A0 =C2= =A0 | foo |
> > | consectetur adipiscing elit. Sed =C2=A0 =C2=A0| = =C2=A0 =C2=A0 |
> > | sit amet luctus sapien. Phasellus =C2=A0 | = =C2=A0 =C2=A0 |
> > | malesuada, ipsum et hendrerit =C2=A0 =C2=A0 = =C2=A0 | =C2=A0 =C2=A0 |
> > | mattis, neque neque sodales risus, = =C2=A0| =C2=A0 =C2=A0 |
> > | hendrerit consectetur enim ipsum eu = | =C2=A0 =C2=A0 |
> > | felis. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2= =A0 =C2=A0 |
> > |-------------------------------------+-----|
= > > | Vestibulum ante ipsum primis in =C2=A0 =C2=A0 | bar |
> &= gt; | faucibus orci luctus et ultrices =C2=A0 =C2=A0| =C2=A0 =C2=A0 |
&g= t; > | posuere cubilia Curae; Nulla dictum | =C2=A0 =C2=A0 |
> >= ; | iaculis sodales. Sed elementum =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 |> > | semper leo, venenatis lacinia odio =C2=A0| =C2=A0 =C2=A0 |
= > > | eleifend vitae. Aliquam lectus =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2= =A0 |
> > | felis, tempor nec lacus ut, =C2=A0 =C2=A0 =C2=A0 =C2= =A0 | =C2=A0 =C2=A0 |
> > | consequat tincidunt nisl. =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=A0 |
> > |------------------= -------------------+-----|
> > | Fusce eu nunc sit amet orci =C2= =A0 =C2=A0 =C2=A0 =C2=A0 | baz |
> > | lobortis accumsan. Vivamus = laoreet =C2=A0| =C2=A0 =C2=A0 |
> > | ante pellentesque, scelerisq= ue =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 |
> > | tellus nec, ultrice= s nibh. Etiam =C2=A0 =C2=A0| =C2=A0 =C2=A0 |
> > | scelerisque lob= ortis erat, in =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=A0 |
> > | consec= tetur nisi tincidunt a. Duis =C2=A0| =C2=A0 =C2=A0 |
> > | eu est = elit. Pellentesque fringilla | =C2=A0 =C2=A0 |
> > | gravida ligul= a, non convallis =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2=A0 |
> > | ligu= la viverra sollicitudin. =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0 =C2=A0 |
&g= t; >
> > Perhaps adding the required machinery to allow in-cell= paragraph
> > filling would not be too difficult?
--089e0158c7c21e9fab05108df141--