emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "\	Jorge Timón" <jtimonmv@gmail.com>
To: emacs-orgmode@gnu.org
Subject: =<<<...>>>= invalid
Date: Sat, 15 Sep 2012 23:34:17 +0200	[thread overview]
Message-ID: <CABOyFfpqYGCBvmQJVzfrPv+UsVmqpcbSaFS7pkKgkz19-PT3+w@mail.gmail.com> (raw)

Hi, I'm working with a document to export to LaTeX and I had a crazy
problem that only reproduced with emacs23, not with the emacs-snapshot
repository for ubuntu. But it started to happen with the latest
snapshot too.
Lot's of short words (3 or less chars) appeared as links and when I
exported the document to LaTeX they all appeared with
\hyperref{sec-1}.
Finally I identified the part that was messing with the export and it
was ~<<<...>>>~ or =<<<...>>>=.
It seems that two << are treated speacially, I don't know.
I'll fix that later but I don't really know how. =aaa= was supposed to
be \{verbatim}. <<<...>>> is a sintaxis to call CUDA kernels, the
place to put the parameters and I want to mention it in the text. I'll
use =< < <...> > >= for now and the dammed symbols still couple.

The "little words as links" is a strange thing. I thought it was for
being on windows at first, but it was about the version: I had ubuntu
with emacs24 at home and winXP with emacs23 at work. I can't rememeber
if it happened with other documents but in any case doesn't looks
good. Has anyone had a similar problem with another "forbidden
string"?
How can I put that string verbatim in my text?
Do I have to go back to "pure LaTeX" for that paragraph?

Thank you in advance.

If the error doesn't reproduce just like that, please tell me and I'll
do more tests in a separate document or link you to a copy. Well, I'll
just do it now:
http://preann.svn.sourceforge.net/viewvc/preann/preann/doc/preann-doc.org

Note: I've using emacs only for five months and I don't think I can
change to another editor if it has not org-mode, congratulations to
the developers. I still feel that something bigger is going to come
out of this.
Still using Eclipse for coding, but that has to change.

-- 
Jorge Timón

next             reply	other threads:[~2012-09-15 21:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-15 21:34  Jorge Timón [this message]
2012-09-17 19:17 ` =<<<...>>>= invalid  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

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=CABOyFfpqYGCBvmQJVzfrPv+UsVmqpcbSaFS7pkKgkz19-PT3+w@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

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