emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Feature Request] Cross headings in tables
Date: Fri, 22 Feb 2013 21:59:51 +0100	[thread overview]
Message-ID: <DC33939E-FCA4-40CC-AC2C-7E93D07BD9CE@gmail.com> (raw)
In-Reply-To: <87txp4nl6r.fsf@Rainer.invalid>


On 22.2.2013, at 21:33, Achim Gratz <Stromeko@nexgo.de> wrote:

> Carsten Dominik writes:
>>> I think the cleanest way to implement this would be to _not_ modify Org
>>> syntax, because it is export back-end very specific. Something like:
>>> 
>>> #+attr_html: :header-groups (1 3)
>>> | This      | will      |
>>> | be        | a header  |
>>> |-----------+-----------|
>>> | This      | won't     |
>>> |-----------+-----------|
>>> | This will | be too    |
>>> |-----------+-----------|
>>> | This      | won't too |
>> 
>> I really like this approach, to mark the header groups in an attribute
>> - maybe an backend-independent attribute?
> 
> I can see the appeal from a programmers' point of view, but from a user
> perspective this is extremely obscure, especially if that table spans a
> few pages and has many such extra header rows (hey, why not ask the user
> to write the table in XML to start with?).  In any case, the current way
> of dealing with headers in org-element and the exporters doesn't admit
> either.
> 
>> The reason why I prefer this approach is that I am weary of new
>> syntax in Org-mode that will take up new characters of character
>> chains.  For the case of tables, if I could go back, I would even
>> remove some of the syntax I introduced, for example for defining the
>> values of constants - that should have been an attribute-link thing as
>> well.  Probably even row and column naming, could have been done in
>> this way.
> 
> Hindsight is 20/20. :-)
> 
> But going this route takes us even further from "Your life in plain
> text." towards "Your life in another programming language." because you
> will need a special viewer or editor to make sense of it for all but the
> most trivial cases.

Point taken.

- Carsten

> 
> 
> Regards,
> Achim.
> -- 
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
> 
> SD adaptation for Waldorf microQ V2.22R2:
> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
> 
> 

  reply	other threads:[~2013-02-22 21:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 17:46 Quoting formula "cookies" in table? Achim Gratz
2010-10-05  1:25 ` Carsten Dominik
2010-10-05 17:10   ` Achim Gratz
2010-10-05 17:24     ` Carsten Dominik
2010-10-06 17:37       ` Achim Gratz
2010-10-05 17:54 ` [Feature Request] Cross headings in tables Achim Gratz
2011-01-16 18:44   ` Achim Gratz
2011-02-02 12:30     ` Lawrence Mitchell
2011-02-02 20:49       ` Achim Gratz
2011-02-08 21:52         ` Achim Gratz
2011-03-20  9:16           ` Achim Gratz
2011-05-29 18:18           ` [Orgmode] " Carsten Dominik
2011-05-30 21:02             ` Achim Gratz
2011-05-31  7:21               ` Carsten Dominik
2011-05-31  8:07                 ` Lawrence Mitchell
2011-05-31 18:01                 ` Achim Gratz
2011-05-31 18:44                   ` Jambunathan K
2011-06-02 16:12                   ` Carsten Dominik
2011-06-07 19:42                 ` Achim Gratz
2013-02-16 19:21                   ` Achim Gratz
2013-02-17  8:35                     ` Nicolas Goaziou
2013-02-17 19:41                       ` Achim Gratz
2013-02-17 21:06                         ` Achim Gratz
2013-02-22 12:31                       ` Carsten Dominik
2013-02-22 20:33                         ` Achim Gratz
2013-02-22 20:59                           ` Carsten Dominik [this message]
2013-02-23  8:10                           ` Bastien
2013-02-23 12:26                       ` Achim Gratz

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=DC33939E-FCA4-40CC-AC2C-7E93D07BD9CE@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=Stromeko@nexgo.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).