From: Ken Williams <Ken.Williams@windlogics.com>
To: "email@example.com" <firstname.lastname@example.org>
Subject: Re: Exporting inline code sections
Date: Mon, 13 Aug 2012 16:30:53 -0500 [thread overview]
Message-ID: <21A5E1E970CD46459ECBE86D6CC4B28C67323C4F@spexch01.WindLogics.local> (raw)
> -----Original Message-----
> From: Ken Williams
> Sent: Monday, August 13, 2012 3:37 PM
> I'm still at version 7.8.03, apologies if this has been addressed in a later
> version already.
FWIW, I just downloaded 7.8.11 and confirmed that the problem still exists there.
I wonder if the inline-code code could use a little love in general. Another thing that would be nice to accomplish with it is to be able to control the markup - right now it forces =code= markers around the output, but it might be nice to let the result flow more naturally in whatever paragraph it's part of. That would be great for stuff like report writing, where statistics calculated dynamically could be put into the report text.
CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of any kind is strictly prohibited. If you are not the intended recipient, please contact the sender via reply e-mail and destroy all copies of the original message. Thank you.
next reply other threads:[~2012-08-13 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 21:30 Ken Williams [this message]
2012-08-13 21:55 ` Exporting inline code sections Bastien
2012-08-13 22:04 ` Ken Williams
2012-08-13 23:34 ` Nick Dokos
2012-08-14 15:01 ` Ken Williams
2012-08-14 15:20 ` Nick Dokos
2012-08-14 15:25 ` Ken Williams
2012-08-14 13:52 ` Ken Williams
-- strict thread matches above, loose matches on Subject: below --
2012-08-13 20:37 Ken Williams
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).