From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: FR: source code Date: Tue, 5 Feb 2008 17:51:44 +0100 Message-ID: <11E5ACC7-7D7C-4C14-B781-74BF142B9AD9@gmail.com> References: <87bq7w5zp0.fsf@shellarchive.co.uk> <60164EE4-391B-4801-AED1-6E0B566FF253@gmail.com> <87tzldh9zs.fsf@shellarchive.co.uk> <5476A1F0-C9C7-480B-A5B3-441CFA9DAF39@gmail.com> <87fxwv8nep.fsf@shellarchive.co.uk> <87lk6839ep.fsf@shellarchive.co.uk> Mime-Version: 1.0 (Apple Message framework v915) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JMRb7-0003gY-GC for emacs-orgmode@gnu.org; Tue, 05 Feb 2008 12:28:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JMRb3-0003fK-RS for emacs-orgmode@gnu.org; Tue, 05 Feb 2008 12:28:41 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JMRb3-0003fG-Ot for emacs-orgmode@gnu.org; Tue, 05 Feb 2008 12:28:37 -0500 Received: from wx-out-0506.google.com ([66.249.82.225]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JMRb3-0005Qd-2f for emacs-orgmode@gnu.org; Tue, 05 Feb 2008 12:28:37 -0500 Received: by wx-out-0506.google.com with SMTP id s7so2387270wxc.24 for ; Tue, 05 Feb 2008 09:28:25 -0800 (PST) In-Reply-To: <87lk6839ep.fsf@shellarchive.co.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Phil Jackson Cc: emacs-orgmode@gnu.org On Jan 29, 2008, at 5:04 PM, Phil Jackson wrote: > Phil Jackson writes: > >> Carsten Dominik 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