From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: [BUG] HTML exporting numbered literal examples Date: Thu, 23 Jul 2009 21:58:56 +0200 Message-ID: <877hxz5fy7.fsf@bzg.ath.cx> References: <87r5wg8lch.fsf@bzg.ath.cx> <87y6qn9xed.fsf@bzg.ath.cx> <87zlb2que2.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MU4Rc-0008Pv-CQ for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 15:59:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MU4RX-0008Gu-Ic for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 15:59:11 -0400 Received: from [199.232.76.173] (port=49864 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MU4RX-0008GQ-85 for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 15:59:07 -0400 Received: from rv-out-0708.google.com ([209.85.198.245]:13853) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MU4RW-0005lF-Oc for emacs-orgmode@gnu.org; Thu, 23 Jul 2009 15:59:06 -0400 Received: by rv-out-0708.google.com with SMTP id f25so482588rvb.6 for ; Thu, 23 Jul 2009 12:59:05 -0700 (PDT) In-Reply-To: (Ulf Stegemann's message of "Mon, 20 Jul 2009 13:36:38 +0200") 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: Ulf Stegemann Cc: emacs-orgmode@gnu.org Hi Ulf, I've finally pushed a change that allows whitespaces in labels and allow the "-r" switch to be used even if "-n" is not there. Please test it and let me know if it works as expected. Thanks, Ulf Stegemann writes: >>> conclusion. I don't think that this is a problem. From the author's >>> point of view I think he/she knows what's going on since this is not the >>> default behaviour and the `-r' switch actually has to be added. And >>> after all we are talking about links. And as with any other link if the >>> link target is self-explanatory: fine, then I can use it as link name. If >>> it is not, I should choose something less confusing for the reader. >> >> One problem is the limitation about labels you can use. E.g. labels do >> not allow whitespaces. It is hard to write meaningful self-explanatory >> link names without using whitespaces. > > Ah okay, that is a good point indeed. I wasn't aware of the fact that > labels could not contain whitespaces. > >> I will see if I can overcome this in a clean way. > > That would be great. Thanks for your efforts! > > Ulf -- Bastien