From: Jambunathan K <kjambunathan@gmail.com>
To: Christian Wittern <cwittern@gmail.com>
Cc: Nicolas Goaziou <n.goaziou@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Side-by-side support
Date: Mon, 23 Jan 2012 22:04:54 +0530 [thread overview]
Message-ID: <81bopucr81.fsf@gmail.com> (raw)
In-Reply-To: <4F1CBD8F.2050404@gmail.com> (Christian Wittern's message of "Mon, 23 Jan 2012 10:53:19 +0900")
Hello Christian
Christian Wittern <cwittern@gmail.com> writes:
> On 2012-01-20 05:03, Jambunathan K wrote:
>> "side-by-side" has surfaced in the list for the second time, I think it
>> deserves to be supported "out of the box".
> I strongly support this, since I have a lot of files with side-by-side
> content. The first question is of course how does the org source look
> like.
I think laying out tables either "list tables" (or for that matter, it's
"beamer equivalent") will become particularly "inconvenient" to edit. In
both the cases, the two-dimensional structure is laid out along the
single-dimension and it would become difficult to "remember" which
column or row when one is editing at a given point in time.
> In my case, I have simply separated the columns by a <tab> character
> and set the tab-width to a sensible value for nice on-screen display.
> These are 'text' and 'translation of that text' side-by-side,
When you are saying on-screen display, I presume you are referring to
the Emacs screen? I have a strong feeling that you are using two column
editing. Otherwise, it would be extremely difficult to keep one's
sanity.
See
C-h k C-x 6 2
(info "(emacs) Two-Column").
I have a wild-thought. Why not use use 2C editing for creating
multi-paragraph Org tables.
I am Ccing Nicolas (who is likely to have thought more about this stuff)
since the last conversation.
> sometimes interrupted by section headers, notes and so on. Therefore I
> end up with multiple 'tables', which will need to have the same width
> throughout the document. Therefore for this use-case, I would like to
> see a global setting for the relative width of these columns.
--
next prev parent reply other threads:[~2012-01-23 16:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 8:52 [ODT] image scaling overridden by long caption Andreas Leha
2012-01-19 20:03 ` Jambunathan K
2012-01-21 10:18 ` Andreas Leha
2012-01-23 19:53 ` Jambunathan K
2012-01-23 21:20 ` Nicolas Goaziou
2012-02-01 9:16 ` comments and attributes Jambunathan K
2012-02-01 13:04 ` Nicolas Goaziou
2012-02-15 0:03 ` [ODT] image scaling overridden by long caption Andreas Leha
2012-01-27 14:40 ` Jambunathan K
2012-01-27 22:41 ` Andreas Leha
2012-01-31 4:59 ` Jambunathan K
2012-02-07 10:04 ` Andreas Leha
2012-01-23 1:53 ` Side-by-side support (was:Re: [ODT] image scaling overridden by long caption) Christian Wittern
2012-01-23 16:34 ` Jambunathan K [this message]
2012-01-23 23:51 ` Side-by-side support Christian Wittern
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=81bopucr81.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=cwittern@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).