emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: nicholas.dokos@hp.com
Cc: Steven Haryanto <stevenharyanto@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: A simpler way to write literal examples?
Date: Wed, 25 May 2011 10:01:05 -0600	[thread overview]
Message-ID: <87hb8ihiri.fsf@gmail.com> (raw)
In-Reply-To: <13042.1306337108@alphaville.dokosmarshall.org> (Nick Dokos's message of "Wed, 25 May 2011 11:25:08 -0400")

> What is the problem with #+BEGIN_EXAMPLE/#+END_EXAMPLE? IOW, why do you need
> an alternative syntax? If your answer is "too much typing", check out
> section 15.2, "Easy templates", in the Org manual.

Also, see the function `org-toggle-fixed-width-section' bound to (C-c :)

Best -- Eric

Eric Schulte

  reply	other threads:[~2011-05-25 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25  9:43 A simpler way to write literal examples? Steven Haryanto
2011-05-25 15:25 ` Nick Dokos
2011-05-25 16:01   ` Eric Schulte [this message]
2011-06-01  1:53   ` Steven Haryanto
2011-06-01  7:29 ` Carsten Dominik

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:

  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=87hb8ihiri.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=stevenharyanto@gmail.com \


* 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


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