From: "\ Jorge Timón" <jtimonmv@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: =<<<...>>>= invalid
Date: Tue, 18 Sep 2012 20:12:56 +0200 [thread overview]
Message-ID: <CABOyFfpOPR6zcf5mR0r8DsGPodSO3P-ZaHkOee+_a+dP5TqDaw@mail.gmail.com> (raw)
In-Reply-To: <CABOyFfo4KbgS0e2qidc1kuhew9zuWPfQte04+REuQLDOGRHRRQ@mail.gmail.com>
Org-mode version 6.30c at home, even with the snapshot. I'll probably
update and follow your advice, thank you.
On 9/18/12, Jorge Timón <jtimonmv@gmail.com> wrote:
> I still get \texttt{<<<} \ldots{} \texttt{>>>}
>
> I have Org-mode version 6.33x at work. I'll check later at home, where
> I have both emacs23 and emacs24 (snapshot).
>
> On 9/17/12, Nick Dokos <nicholas.dokos@hp.com> wrote:
>> Jorge Timón <jtimonmv@gmail.com> wrote:
>>
>>> I wouldn't care about the spaces and I would prefer not to use latex.
>>> The problem is that that produces:
>>>
>>> \texttt{<<<} \ldots{} \texttt{>>>}
>>>
>>
>> Did you try it with the tildes instead of the equal signs?
>> Here, both old and new exporters produce
>>
>> aaa \verb~<<<~ \ldots{} \verb~>>>~ aa a a
>>
>> at least with the version I'm running (Org-mode version 7.9.1
>> (release_7.9.1-214-gf025d1))
>>
>> Nick
>>
>>> and then latex joins the first << and the first >> together, which is
>>> really ugly.
>>>
>>> My document is already LaTeX specific, but if I'm able replace more
>>> latex with org mode, I should consider a later edition of the tex
>>> produced to keep it backend-independent. Not critical for this
>>> document, but it is always cool to be able to export to different
>>> formats.
>>>
>>> Thank you for the suggestion, anyway.
>>>
>>> On 9/17/12, Nick Dokos <nicholas.dokos@hp.com> wrote:
>>> > 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
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>> --
>>> Jorge Timón
>>>
>>
>
>
> --
> Jorge Timón
>
--
Jorge Timón
prev parent reply other threads:[~2012-09-18 18:12 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
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 [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=CABOyFfpOPR6zcf5mR0r8DsGPodSO3P-ZaHkOee+_a+dP5TqDaw@mail.gmail.com \
--to=jtimonmv@gmail.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).