emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bastienguerry@googlemail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Unnecessary comma escapes in HTML export of #+INCLUDE files
Date: Wed, 22 Jul 2009 09:50:56 +0200	[thread overview]
Message-ID: <87tz15jgv3.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20090722011304.GY16388@hplhtang> (Hsiu-Khuern Tang's message of "Tue, 21 Jul 2009 18:13:05 -0700")

Hi,

"Tang, Hsiu-Khuern" <hsiu-khuern.tang@hp.com> writes:

> If I include a file in my Org file, say using
>
> #+INCLUDE: "script.sh" src sh
>
> and export to HTML, the included file shows up as a <pre> block, which is nice.
> However, a leading comma is put in front of every line that starts with a #,
> even those with leading whitespace.  I understand that a comma is used to
> escape # in the first column of literal examples, to distinguish from Org
> comment lines.  (This escaping is no longer strictly necessary, since the
> #+BEGIN_EXAMPLE block can now be indented.)

I cannot reproduce this.

Which version of Org are you using?

PS: by commas do you mean columns?

-- 
 Bastien

  reply	other threads:[~2009-07-22  7:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22  1:13 Unnecessary comma escapes in HTML export of #+INCLUDE files Tang, Hsiu-Khuern
2009-07-22  7:50 ` Bastien [this message]
2009-07-22 17:35   ` Hsiu-Khuern Tang
2009-07-24  1:22     ` Bastien
2009-07-24  5:45       ` Hsiu-Khuern Tang
2009-09-01 22:03         ` Hsiu-Khuern Tang
     [not found]           ` <hsiu-khuern.tang@hp.com>
2009-09-01 22:47             ` Nick Dokos
2009-09-02  0:09               ` Hsiu-Khuern Tang
2009-09-02  6:25           ` Carsten Dominik
2009-09-02  7:40             ` Nick Dokos
2009-09-02  9:33               ` Carsten Dominik
2009-09-03  5:34                 ` Hsiu-Khuern Tang

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=87tz15jgv3.fsf@bzg.ath.cx \
    --to=bastienguerry@googlemail.com \
    --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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).