From: Luis Anaya <papoanaya@hotmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Eric Schulte <eric.schulte@gmx.com>
Subject: Re: #+CAPTION: Not being protected when they are used with #+begin_src
Date: Sat, 7 Jul 2012 15:33:42 -0400 [thread overview]
Message-ID: <BLU0-SMTP81255AF98DBDBA63DDE223B7ED0@phx.gbl> (raw)
In-Reply-To: <873953tmyi.fsf@gmail.com> (Nicolas Goaziou's message of "Sat\, 07 Jul 2012 21\:01\:25 +0200")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
Hi:
> This is the known bug I told you about in another thread. It will be
> fixed soon after org-element hits core.
Oh... I guess I missed that email :( At least I know that named captions are
working for images.
In other news...
Other things I got working today are:
1. Checklists, in Groff will be: White bullet for on, Black bullet for
off and hyphen. These map to .BL command.
2. Descriptive lists. It maps to a .VL statement with an inch separation (2.54 cm's
for those in metric) between item and description.
3. Inline links for image types [[file:image.eps]] resolves to .PSPIC
"image.eps" while a [[file:image.pic]] link resolves to a .PS/.PE pair.
4. Gnuplot support, embeds gpic or eps. You get better results with gpic.
5. Direct Groff commands. Now equations can be embedded. (via EQ/EN/EC)
commands.
6. Cleaned up some of the links output to make it look pretty :)
--
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:33 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
2012-07-07 19:01 ` Nicolas Goaziou
2012-07-07 19:33 ` Luis Anaya [this message]
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-SMTP81255AF98DBDBA63DDE223B7ED0@phx.gbl \
--to=papoanaya@hotmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.com \
--cc=n.goaziou@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).