From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: LaTeX export bugs? Date: Fri, 18 Sep 2009 07:37:29 +0100 Message-ID: <397D3F1D-CCD7-492F-BFED-5C949767D9C6@gmail.com> References: <87vdmjglto.fsf@mundaneum.com> <874otwduhr.fsf@mundaneum.com> <13C7ED92-A0C1-40E0-873A-F6A9143167DB@gmail.com> <874or4o19x.fsf@missioncriticalit.com> <87d45pmxnd.fsf@mundaneum.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MoX6E-0000iU-GX for emacs-orgmode@gnu.org; Fri, 18 Sep 2009 02:37:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MoX66-0000cq-Ri for emacs-orgmode@gnu.org; Fri, 18 Sep 2009 02:37:39 -0400 Received: from [199.232.76.173] (port=36223 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MoX66-0000cg-4W for emacs-orgmode@gnu.org; Fri, 18 Sep 2009 02:37:34 -0400 Received: from mail-ew0-f211.google.com ([209.85.219.211]:35167) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MoX65-0005sA-Ki for emacs-orgmode@gnu.org; Fri, 18 Sep 2009 02:37:33 -0400 Received: by ewy7 with SMTP id 7so1028252ewy.31 for ; Thu, 17 Sep 2009 23:37:32 -0700 (PDT) In-Reply-To: <87d45pmxnd.fsf@mundaneum.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?ISO-8859-1?Q?S=E9bastien_Vauban?= Cc: emacs-orgmode@gnu.org On Sep 17, 2009, at 3:52 PM, S=E9bastien Vauban wrote: > Hi Carsten, > > Francesco Pizzolante wrote: >> >>> indeed, it looks like I did make a mistake when recently trying to =20= >>> fix >>> this. >>> >>> I believe I have got it right this time (current git version), =20 >>> please >>> verify. >> >> It works perfectly now. > > Not exactly the same problem, but very similar IMHO, there is (now =20 > or still?) > a problem of highlighting with `#+BEGIN' meta info not starting in =20 > column 0. > > Just test with the following: > > --8<---------------cut here---------------start------------->8--- > * 2009-09 > > #+BEGIN: clocktable :maxlevel 2 :scope file :block yesterday > Clock summary at [2009-09-16 Wed 17:27], for Tuesday, September 15, =20= > 2009. > > | L | Headline | Time | | > |---+--------------+--------+------| > | | *Total time* | *7:25* | | > |---+--------------+--------+------| > | 1 | 2009-09 | 7:25 | | > | 2 | Some project | | 7:25 | > #+END: > --8<---------------cut here---------------end--------------->8--- Hi Sebasien, I am aware of this problem, but it is not so easy to solve. The reason for this is that dynamic blocks are written by some user function, which is not aware of any indentation to be applied. So if I would allow indentation for the BEGIN line, I would end up with #+BEGIN: clocktable | L | Headline | Time | | |---+--------------+--------+------| | | *Total time* | *7:25* | | |---+--------------+--------+------| | 1 | 2009-09 | 7:25 | | | 2 | Some project | | 7:25 | #+END: Is that the desired outcome? I guess I could enforce indentation of the block written by the user function, but I am not sure if this might cause problems in some cases. I need to think more about this. - Carsten=