emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: =?ISO-8859-1?B?CUpvcmdlIFRpbfNu?= <jtimonmv@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: =<<<...>>>= invalid
Date: Mon, 17 Sep 2012 16:53:46 -0400	[thread overview]
Message-ID: <10059.1347915226@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from =?ISO-8859-1?B?CUpvcmdlIFRpbfNu?= <jtimonmv@gmail.com> of "Mon\, 17 Sep 2012 22\:10\:04 +0200." <CABOyFfqGcQwxFRXAVH_pUp-3a7nLLVOAVNqKiuow7cWeEY6FKw@mail.gmail.com>

	Jorge Timón <jtimonmv@gmail.com> wrote:

> The only way I know to do what I want is \verb=<<<=...\verb=>>>=, in
> case someone has a similar problem.
> 

If you don't mind the extra space around the dots, you can say

   aaa ~<<<~ ... ~>>>~ aa a a

the advantage being that it is backend-independent, so it will export
correctly to HTML and presumably all the other backends --- at least
with the new exporter: I didn't try the old one.

There are ways to deal with the spaces as well (the one before the dots
is no problem: it's the one after that causes a problem in this case),
but imo they are not worth the bother unless you really, really need that
exact behavior. I'd rather live with the spaces (or edit the resulting latex
file, but that has disadvantages of its own).

Nick

  reply	other threads:[~2012-09-17 20:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-15 21:34 =<<<...>>>= invalid  Jorge Timón
2012-09-17 19:17 `  Jorge Timón
2012-09-17 19:24 ` Achim Gratz
2012-09-17 20:10   `  Jorge Timón
2012-09-17 20:53     ` Nick Dokos [this message]
2012-09-17 21:21       `  Jorge Timón
2012-09-17 21:33         ` Nick Dokos
2012-09-18  8:27           `  Jorge Timón
2012-09-18 18:12             `  Jorge Timón

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=10059.1347915226@alphaville.americas.hpqcorp.net \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jtimonmv@gmail.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).