emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Daniel Schoepe <daniel@schoepe.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Comments break lists when exporting to TeX
Date: Wed, 23 May 2012 15:51:23 +0200	[thread overview]
Message-ID: <87obpfatus.fsf@gmail.com> (raw)
In-Reply-To: <874nr7dq4k.fsf@schoepe.localhost> (Daniel Schoepe's message of "Wed, 23 May 2012 14:43:39 +0200")

Hello,

Daniel Schoepe <daniel@schoepe.org> 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
>   <contents of foo.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

     prev parent reply	other threads:[~2012-05-23 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 17:05 Comments break lists when exporting to TeX Daniel Schoepe
2012-05-23 12:21 ` Nicolas Goaziou
2012-05-23 12:43   ` Daniel Schoepe
2012-05-23 13:51     ` Nicolas Goaziou [this message]

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=87obpfatus.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=daniel@schoepe.org \
    --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

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).