From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Schoepe Subject: Re: Comments break lists when exporting to TeX Date: Wed, 23 May 2012 14:43:39 +0200 Message-ID: <874nr7dq4k.fsf@schoepe.localhost> References: <87likkw3hh.fsf@schoepe.localhost> <871umbcclu.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54995) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SXAv4-0000sd-QN for emacs-orgmode@gnu.org; Wed, 23 May 2012 08:44:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SXAuu-0003np-Nx for emacs-orgmode@gnu.org; Wed, 23 May 2012 08:44:02 -0400 Received: from mail-wg0-f49.google.com ([74.125.82.49]:59725) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SXAuu-0003n0-EF for emacs-orgmode@gnu.org; Wed, 23 May 2012 08:43:52 -0400 Received: by wgbds1 with SMTP id ds1so5309549wgb.30 for ; Wed, 23 May 2012 05:43:49 -0700 (PDT) In-Reply-To: <871umbcclu.fsf@gmail.com> 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain On Wed, 23.05.2012 14:21, Nicolas Goaziou wrote: > At the moment you insert text at column 0, the list ends. You can use > inline comments (i.e. #+ This isn't) instead. This however, does not solve my original problem, since it doesn't work with #+INCLUDE (with version 7.8.09): * Test - This will not indent the code properly as a part of the list element #+INCLUDE foo.c src c - This will print "#+INCLUDE .." literally: #+INCLUDE foo.c src c - This works as expected: #+BEGIN_SRC c #+END_SRC Of course I could fall back to something like \lstlistinginput, but that works only for TeX-export and hence defeats the whole point of result-format-agnostic directives such as #+INCLUDE (at least when it's used for source files). > I do not. Export is consistent with in-buffer behaviour. You have > created two lists here, not one, and it has nothing to do with export. I find it odd for a comment to have such an effect on the "semantics" of the document. My intuition about comments (that aren't special directives) is that they have no effect on the final result (the PDF in this case, or the binary in the case of compilable source code). I think what I'm saying is that the comment shouldn't break up the lists in the buffer either, but I don't have any strong feelings about this, as long I can get #+INCLUDE to work in list elements. (But it would be a nice, general rule that would allow #+INCLUDE to work as "expected". Another alternative would be to make all such directives also work when they're not at column 0). Cheers, Daniel --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJPvNt7AAoJEIaTAtce+Z+JkKMQAIskBTDo8w995uGO5etC3YfD wi2JzvAfmac0A6C+6myXkDU/DaJEL+R5YkuGjpfYiVwWdmMZVrGZX14DxpHEuSfy Dhb1NtBY0wlKhjE8cAJCjiLBlv2HDD0SJzfmHnAcs2Dt3/0AU8o/0DvPuTQlsi77 8li0196GYf5v+air3VZBgUbWzynZDEGwbicn8KMW7P4c0hqt1+UlwD7Mkj9EGvpo Y2sjPqH4cwLdusp5PqQZr/8Cgz31tkf4eEAIsRVRIVyFMtAvlsxyALYP/vv93Us9 L4UtzWl2BkX8zgdoK/v+RaGd+rFeShddra1qpur8u91+IBTv7WD4eZY0oOyH+Mlq c/c16+1NMVcHgeCbd5l4oCR1cUsIfVxw3GZaek47aneUeEla7XK99MoxAyugLVjX 9SJowUJQIIHEG/Z0kAqCFMT3GJs0wXoSbWBLeFPJxgyxlNGan1oRaPdvvgW+0IlJ vOLX/BeK8kmVo3BEutZATABih/jwPC83AGZrO5XGTGl1NRYj+GbXhTlxXa9DJJNU GUNTVOSfZeEEINHxPUSabuaXRbSRVzIwbTaRNaRhyQkEcVWTJVCJxw2c/jyIDvbQ K9uSR0xnvCFRpLMpZCFrHNJ2e2T2xHmWK5+7HQIUQCXDD857Oz5Z3oQ0ejRQHNN8 XbipLI9pq4y3JXoYrEau =db/a -----END PGP SIGNATURE----- --=-=-=--