From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: [Feature Request] Cross headings in tables Date: Sun, 17 Feb 2013 20:41:37 +0100 Message-ID: <87ehgeafta.fsf@Rainer.invalid> References: <87ocb96ebn.fsf@Rainer.invalid> <87eic4le49.fsf@Rainer.invalid> <87d3nwzo22.fsf@Rainer.invalid> <87ei7qxiuf.fsf@Rainer.invalid> <87wrlakxcv.fsf@Rainer.invalid> <87zkm3yk96.fsf@Rainer.invalid> <87tyc1xwam.fsf@Rainer.invalid> <87obfk12uh.fsf_-_@Rainer.invalid> <87y5enpcc9.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:44020) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U7A7W-0004ex-Un for emacs-orgmode@gnu.org; Sun, 17 Feb 2013 14:41:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U7A7Q-0003Tn-LW for emacs-orgmode@gnu.org; Sun, 17 Feb 2013 14:41:54 -0500 Received: from plane.gmane.org ([80.91.229.3]:33441) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U7A7Q-0003Te-EZ for emacs-orgmode@gnu.org; Sun, 17 Feb 2013 14:41:48 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1U7A7i-00086E-Uf for emacs-orgmode@gnu.org; Sun, 17 Feb 2013 20:42:06 +0100 Received: from pd9eb5ed7.dip.t-dialin.net ([217.235.94.215]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Feb 2013 20:42:06 +0100 Received: from Stromeko by pd9eb5ed7.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Feb 2013 20:42:06 +0100 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: emacs-orgmode@gnu.org Nicolas Goaziou writes: > You only need to modify org-element if Org syntax has been changed. Yes, thats exactly what I want. >> Also, it appears that each element can have only one property or did >> I miss something? It seems that having a way to get the (main) >> property and then asking if there are sub-properties on that element >> would allow simpler code in this particular instance and likely >> elsewhere. Maybe I missed how to do it, though. > > I don't understand that part. (org-element-property :type row) This will return a single symbol 'standard or 'rule inside a table. If there was a way to ask "which kind of rule" later, this would enable a much more elegant implementation. > http://orgmode.org/worg/dev/org-export-reference.html > > for a list of all properties associated to a given element or object > type. So you are saying that a table row could get an additional property to record which rule-type it has and whether it is a header row or not? > I think the cleanest way to implement this would be to _not_ modify Org > syntax, because it is export back-end very specific. This is an impressive hack, but is largely unuseable IMHO. And whether a table row is a header or not is certainly not back-end specific or at least it shouldn't be: the back-end gets told if it should format a table row as a header or as a normal row and that code is all in ox. The only other part of the code that needs to know which row groups are headers is when column formulas are involved. The original hack tried to keep things backwards compatible, but I think that it would have merit to allow tables with separators that don't introduce any headers (as several people have asked for in the past) and that simply isn't in the cards with the current syntax. So, a row group would only be a header when the following rule was "|~" and the first row group wouldn't need to be special any more. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds