emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: Syntax Proposal: Multi-line Table Cells/Text Wrapping
Date: Fri, 19 Mar 2021 09:08:43 +0100	[thread overview]
Message-ID: <20210319080843.GA24268@tuxteam.de> (raw)
In-Reply-To: <8735wsdr08.fsf@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]

On Thu, Mar 18, 2021 at 11:41:11PM +0100, Juan Manuel Macías wrote:
> Tim Cross <theophilusx@gmail.com> writes:
> 
> > From watching these discussions in the past, I think the big stumbling
> > block is how easily multi-row columns can be added and maintained in the
> > various export formats [...]

> I don't know if anyone has come up with this other possibility: if the
> problem is (usually) the inconvenience of editing cells with a lot of
> text within an Org document (since when exporting to LaTeX [...]

I think this point is very important: "multi-row" is ambiguous.

Does it mean the rendering in Org?  In someother output format? Are the
row breaks chosen by the user (and thus they have /some/ "meaning") or
are they chosen by some rendering mechanism (word wrap, perhaps
hyphenation)?

> the possibility of editing a cell in a dedicated buffer would be very
> practical here.

If the aim is "just rendering in Org" and "breaks have no special
meaning" (so each render is allowed to re-flow), then your approach
makes sense (I think Org table has something like that: you can
set the column width and shrink/expand the column appropriately.
Personally, I've found that somewhat awkward, so I don't use it,
but OTOH I'm not a heavy table user: perhaps that's why).

Cheers
 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2021-03-19  8:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 20:29 Atlas Cove
2021-03-17 21:02 ` Daniele Nicolodi
2021-03-17 22:07 ` Juan Manuel Macías
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 [this message]
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=20210319080843.GA24268@tuxteam.de \
    --to=tomas@tuxteam.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).