From: Carsten Dominik <carsten.dominik@gmail.com>
To: Phil Jackson <phil@shellarchive.co.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: FR: source code
Date: Tue, 5 Feb 2008 17:51:44 +0100 [thread overview]
Message-ID: <11E5ACC7-7D7C-4C14-B781-74BF142B9AD9@gmail.com> (raw)
In-Reply-To: <87lk6839ep.fsf@shellarchive.co.uk>
On Jan 29, 2008, at 5:04 PM, Phil Jackson wrote:
> Phil Jackson <phil@shellarchive.co.uk> writes:
>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
> [...]
>
>>>> I *personally* still can't decide if this is within org's scope
>>>> though, not to say I wouldn't find it very handy.
>
>>> So then am confused what you initial message was about. The feature
>>> your are asking for is then an exporting feature, right? Maybe you
>>> need to restate what exactly you would like to see.
>
>> Yes, I'm a confused young man. My final answer is: I would like to
>> see
>> syntax highlighted code in a HTML export :)
>
> So what do you think Carsten? I would like to see the:
>
> #+BEGIN_EXAMPLE lang:shell-script
> #+END_EXAMPLE
>
> That Bastien suggested. I would be willing to help out the exporter
> people if need be.
Hi Phil,
just to let you know: this idea is not forgotten. However, we have some
internal discussion about a big generalization of the exporters.
If that happens, things like special formatting of examples will be
easy to
add. Before being sure what is going to happen, I don't want to
be spending time with this.
However, since you have signed the papers now, feel free to implement
a proposal for the exporter. The routing where you want to hook into
might be org-cleaned-string-for-export - this is where the BEGIN_EXAMPLE
is currently turned into a quoted string. However, the fact that I am
pointing you to this routine might already show that the exporter
really needs a rewrite.
- Carsten
prev parent reply other threads:[~2008-02-05 17:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 11:22 FR: source code Phil Jackson
2008-01-08 14:03 ` Bastien
[not found] ` <b71b18520801082003h7baccfa9t3a0cf936c07c086a@mail.gmail.com>
2008-01-09 4:04 ` Eddward DeVilla
2008-01-09 17:33 ` Ed Hirgelt
2008-01-09 17:50 ` Russell Adams
2008-01-09 22:21 ` Adam Spiers
2008-01-16 0:36 ` Bastien
2008-01-16 1:21 ` Eddward DeVilla
2008-01-16 1:55 ` Bastien
2008-01-16 2:33 ` Tim Stewart
2008-01-16 12:05 ` Bastien
2008-01-16 16:03 ` Tim Stewart
2008-01-16 16:21 ` Carsten Dominik
2008-01-16 18:59 ` Phil Jackson
2008-01-18 8:20 ` Carsten Dominik
2008-01-18 9:59 ` Phil Jackson
2008-01-29 16:04 ` Phil Jackson
2008-01-29 18:20 ` Rick Moynihan
2008-01-29 18:32 ` Russell Adams
2008-01-29 18:49 ` Phil Jackson
2008-01-30 7:02 ` Bastien Guerry
2008-01-30 7:17 ` Bastien Guerry
2008-02-05 16:51 ` Carsten Dominik [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=11E5ACC7-7D7C-4C14-B781-74BF142B9AD9@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=phil@shellarchive.co.uk \
/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).