From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Atlas Cove <Atlas48@gmx.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Syntax Proposal: Multi-line Table Cells/Text Wrapping
Date: Wed, 17 Mar 2021 23:07:57 +0100 [thread overview]
Message-ID: <87sg4tbfia.fsf@posteo.net> (raw)
In-Reply-To: <7a450ea3-b0e4-3322-04cd-fb5a5a555db8@gmx.com> (Atlas Cove's message of "Wed, 17 Mar 2021 20:29:56 +0000")
Hi,
Atlas Cove <Atlas48@gmx.com> writes:
> Code-wise, the use of the '\\' symbol is only tentative, as I
> understand that '\' has special meaning elsewhere in org's syntax, (I
> was even going to submit a patch to add two special symbols somewhere
> down the line). '\\' (or whatever symbol is decided on) would cause
> the org parser to concatenate the next line into the outputted
> previous cell, rendering the output of the first example identical to
> the second example.
I agree that what you are commenting on is the great problem of Org Mode
tables. Just a question. If I have understood it correctly, with this
new syntax you propose, should Org understand all the 'concatenated
text'
Very Citrusy! Very \\
nice indeed!
as a single row (and not as multiple rows)? If so that would be
great, since the best way to deal with this kind of tables with a lot of
text in LaTeX is with the tabularx package. For example, I would export
your table like this:
#+begin_src org
,#+LaTeX_Header:\usepackage{tabularx,array}
,#+ATTR_LaTeX: :environment tabularx :align l>{\raggedright\arraybackslash}Xl :width .6\textwidth :center t
| Name | Description | Price |
|--------------+-------------------------------------------------------+-------|
| Orange Juice | Very Citrusy! Very nice indeed! ... and a lot of text | 5.00 |
| Grape Juice | It's like wine, but you can have it all day! | 6.00 |
#+end_src
Best regards,
Juan Manuel
next prev parent reply other threads:[~2021-03-17 22:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 20:29 Syntax Proposal: Multi-line Table Cells/Text Wrapping Atlas Cove
2021-03-17 21:02 ` Daniele Nicolodi
2021-03-17 22:07 ` Juan Manuel Macías [this message]
2021-03-18 13:38 ` Atlas Cove
2021-03-18 14:04 ` Daniele Nicolodi
2021-03-18 15:15 ` Juan Manuel Macías
2021-03-18 14:19 ` Maxim Nikulin
2021-03-18 14:26 ` Timothy
2021-03-18 14:31 ` Atlas Cove
2021-03-18 21:58 ` Tim Cross
2021-03-18 22:41 ` Juan Manuel Macías
2021-03-19 8:08 ` tomas
2021-03-19 8:44 ` Juan Manuel Macías
2021-03-19 8:53 ` tomas
2021-03-19 9:22 ` Juan Manuel Macías
2021-03-19 10:14 ` tomas
2021-03-19 10:53 ` Juan Manuel Macías
2021-03-19 11:08 ` Juan Manuel Macías
2021-03-19 13:43 ` tomas
2021-03-19 15:07 ` Juan Manuel Macías
2021-03-20 22:49 ` Samuel Wales
2021-03-21 8:43 ` Juan Manuel Macías
2021-03-19 2:27 ` Timothy
2021-03-19 3:50 ` Tim Cross
2021-03-19 4:02 ` Timothy
2021-03-19 13:33 ` Eric S Fraga
2021-03-19 21:33 ` Tim Cross
2021-03-20 9:19 ` Eric S Fraga
2021-03-20 10:40 ` Juan Manuel Macías
2021-03-20 13:41 ` Andreas Eder
2021-03-20 22:06 ` Tim Cross
2021-03-22 10:54 ` Eric S Fraga
2021-04-01 6:15 ` Tom Gillespie
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=87sg4tbfia.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=Atlas48@gmx.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).