From: Luis Anaya <papoanaya@hotmail.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: #+CAPTION: Not being protected when they are used with #+begin_src
Date: Sat, 7 Jul 2012 15:00:10 -0400 [thread overview]
Message-ID: <BLU0-SMTP193B44EE53FBEED46A10F43B7ED0@phx.gbl> (raw)
In-Reply-To: <87a9zb7ary.fsf@gmx.com> (Eric Schulte's message of "Sat\, 07 Jul 2012 11\:15\:29 -0600")
Eric Schulte <eric.schulte@gmx.com> writes:
>
> Instead of putting the #+Caption: line on the source block, place it on
> the result. This requires the use of named code blocks and results.
> The following alternate version of your example should give the behavior
> you're after.
>
[chomp...]
Hi Eric:
Thanks for your help but not quite what I expected. I did get the
caption now, but I am still getting the #+NAME:
See results:
.H 1 "PlantUML"
.P
#+NAME: plantuml-drawing
.P
.PSPIC "x.eps"
.FG "\fRplantuml drawing\fP"
.H 1 "Gnuplot"
.P
#+name: gnuplot-drawing
.P
.PS
copy "salida.pic"
.PE
.FG "\fRgnuplot drawing\fP"
I'm getting suspicious on the ".P" on my results during paragraph
generation. What I'll do is to temporary remove generating that ".P" and see
if that removes the #+NAME: tag. If that's the case, I have to add
another exception clause on the backend...
Thanks a bunch!
--
Luis Anaya
papo anaya aroba hot mail punto com
"Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
next prev parent reply other threads:[~2012-07-07 19:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 3:36 Exporting to groff Luis Anaya
2012-06-26 11:33 ` Nick Dokos
2012-06-26 14:09 ` Luis Anaya
2012-06-26 14:55 ` Nicolas Goaziou
2012-06-29 23:58 ` Exporting to groff, now in org-export.el Luis Anaya
2012-06-30 6:42 ` Nicolas Goaziou
2012-06-30 11:56 ` Nicolas Goaziou
2012-07-03 1:18 ` Luis Anaya
2012-07-03 9:51 ` Nicolas Goaziou
2012-07-05 22:46 ` Luis Anaya
2012-07-06 7:14 ` Nicolas Goaziou
2012-07-07 14:25 ` #+CAPTION: Not being protected when they are used with #+begin_src Luis Anaya
2012-07-07 17:15 ` Eric Schulte
2012-07-07 19:00 ` Luis Anaya [this message]
2012-07-07 19:01 ` Nicolas Goaziou
2012-07-07 19:33 ` Luis Anaya
2012-07-07 20:28 ` Exporting to groff, now in org-export.el Luis Anaya
2012-07-07 20:31 ` Luis Anaya
2012-07-07 22:59 ` suvayu ali
2012-07-08 1:49 ` Luis Anaya
2012-07-08 1:56 ` suvayu ali
2012-07-08 13:14 ` Luis Anaya
2012-07-08 14:07 ` Suvayu Ali
2012-07-09 0:29 ` Luis Anaya
2012-07-09 20:32 ` Luis Anaya
2012-07-09 21:23 ` suvayu ali
2012-07-09 21:55 ` Luis Anaya
2012-07-09 22:01 ` suvayu ali
2012-07-10 0:00 ` Luis Anaya
2012-07-10 0:21 ` suvayu ali
2012-07-10 1:09 ` Luis Anaya
2012-07-10 1:20 ` suvayu ali
2012-07-10 13:30 ` Luis Anaya
2012-06-30 22:36 ` Luis Anaya
2012-07-13 18:51 ` Luis Anaya
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=BLU0-SMTP193B44EE53FBEED46A10F43B7ED0@phx.gbl \
--to=papoanaya@hotmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.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).