From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wanrong Lin Subject: Re: Re: Blank lines in literal html Date: Sun, 09 Dec 2007 18:08:54 -0500 Message-ID: <475C7586.9010105@gmail.com> References: <475453D3.30604@gmail.com> <4756FC88.1050701@gmail.com> <878x44ekw6.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J1VGj-0000Ki-Mq for emacs-orgmode@gnu.org; Sun, 09 Dec 2007 18:09:05 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J1VGh-0000Ii-Te for emacs-orgmode@gnu.org; Sun, 09 Dec 2007 18:09:05 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J1VGh-0000IT-PH for emacs-orgmode@gnu.org; Sun, 09 Dec 2007 18:09:03 -0500 Received: from py-out-1112.google.com ([64.233.166.183]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J1VGh-0003sB-4E for emacs-orgmode@gnu.org; Sun, 09 Dec 2007 18:09:03 -0500 Received: by py-out-1112.google.com with SMTP id a73so3467193pye for ; Sun, 09 Dec 2007 15:09:01 -0800 (PST) In-Reply-To: <878x44ekw6.fsf@bzg.ath.cx> 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: org-mode list Bastien wrote: > Hi Wanrong, > > Wanrong Lin writes: > > >> Finally, I decided to learn some elisp debugging techniques and as a >> practice, it seems I found the bug and fixed it with this patch (against >> org.el in 5.16b) >> >> @@ -24437,7 +24437,7 @@ >> (when (re-search-backward >> "\\(

\\)\\([ \t\r\n]*\\)\\=" (- (point) 100) t) >> (setq par (match-string 1)) >> - (replace-match "\\2\n")) >> + (replace-match "")) >> (insert line "\n") >> (while (and lines >> (get-text-property 0 'org-protected (car lines))) >> >> I am not completely sure whether this is the right fix, but so far the >> output looks OK to me. >> > > Thanks for this. I think the patch is safe (I'm testing it for two or > three days now) but I cannot predict it will be in any cases. I guess > Carsten will have a better call on this. > > (BTW, the issue your raising here concerns the way the HTML code *looks* > and IMO they are less important than issues regarding the correctness of > the HTML code... Just a thought.) > > Thanks for testing. Surely the No.1 priority is to have correct HTML syntax. But I think how the page looks comes very close as a second priority. After all, we use HTML because we want certain look (and better navigation). Wanrong