emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bill Hager <whager@gmail.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: BEGIN_EXAMPLE question
Date: Wed, 12 Aug 2009 11:38:02 -0400	[thread overview]
Message-ID: <f7d6d6950908120838h6bb417bm15386debdb127e6d@mail.gmail.com> (raw)
In-Reply-To: <f7d6d6950908120348v35842d37we1e27d0bec31ed29@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1421 bytes --]

On Wed, Aug 12, 2009 at 6:48 AM, Bill Hager <whager@gmail.com> wrote:

> On Wed, Aug 12, 2009 at 12:43 AM, Nick Dokos <nicholas.dokos@hp.com>wrote:
>
>> Bill Hager <whager@gmail.com> wrote:
>>
>> > I don't seem to understand #+BEGIN_EXAMPLE and it's relation to html
>> > export.  What I think is that everything between a #+BEGIN_EXAMPLE and
>> > #+END_EXAMPLE should end up in <pre> tags when I do a HTML export with
>> C-c
>> > C-e b.  However, the reality is that everything ends up in a <p> tag for
>> me.
>> >
>> > My goal is to have sections of my org file end up in <pre> tags when I
>> HTML
>> > export.  Any ideas on how I can do this?
>> >
>> > I'm running the default emacs 22.2.1 on Ubuntu Jaunty.
>> >
>>
>> I can't reproduce this. I used the following simple org file:
>>
>> ,----
>> |
>> | * Test
>> |
>> | Here's an example:
>> |
>> | #+BEGIN_EXAMPLE
>> | This is a test.
>> | #+END_EXAMPLE
>> `----
>>
>> did C-c C-e h and got the attached html file. The example is
>> <pre>'d properly I think.
>>
>
> Thanks Nick.  That does help give me something to compare against.  I've
> attached my results from the same test you did with C-c C-e h showing <p>
> tags instead of <pre> tags for the BEGIN_EXAMPLE/END_EXAMPLE section.
>
> Thanks
>


I noticed that Nick was using emacs 23.  I downloaded and compiled 23.1 from
the GNU website.  The new version properly uses <pre> tags for
#+BEGIN_EXAMPLE.

- Bill

[-- Attachment #1.2: Type: text/html, Size: 2276 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2009-08-12 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12  3:32 BEGIN_EXAMPLE question Bill Hager
2009-08-12  4:43 ` Nick Dokos
2009-08-12 10:48   ` Bill Hager
2009-08-12 15:38     ` Bill Hager [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=f7d6d6950908120838h6bb417bm15386debdb127e6d@mail.gmail.com \
    --to=whager@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /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).