From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Comments break lists when exporting to TeX Date: Wed, 23 May 2012 15:51:23 +0200 Message-ID: <87obpfatus.fsf@gmail.com> References: <87likkw3hh.fsf@schoepe.localhost> <871umbcclu.fsf@gmail.com> <874nr7dq4k.fsf@schoepe.localhost> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34833) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SXC1A-0000gA-V7 for emacs-orgmode@gnu.org; Wed, 23 May 2012 09:54:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SXC18-0006kR-Bp for emacs-orgmode@gnu.org; Wed, 23 May 2012 09:54:24 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:51209) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SXC18-0006im-35 for emacs-orgmode@gnu.org; Wed, 23 May 2012 09:54:22 -0400 Received: by wefh52 with SMTP id h52so6059671wef.0 for ; Wed, 23 May 2012 06:54:20 -0700 (PDT) In-Reply-To: <874nr7dq4k.fsf@schoepe.localhost> (Daniel Schoepe's message of "Wed, 23 May 2012 14:43:39 +0200") 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: Daniel Schoepe Cc: emacs-orgmode@gnu.org Hello, Daniel Schoepe writes: > * 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 This should be "#+INCLUDE: "foo.c" src c", not "#+INCLUDE foo.c src c" > 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). Note that INCLUDE keyword isn't a comment. Also, again, comments have no effect on the final result: they are consistent with what happens within buffer. [...] > 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). --8<---------------cut here---------------start------------->8--- - This will print "#+INCLUDE .." literally: #+INCLUDE: "foo.c" src c --8<---------------cut here---------------end--------------->8--- This works as expected in the new exporter. Regards, -- Nicolas Goaziou