From: Wanrong Lin <wanrong.lin@gmail.com>
To: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: Re: Blank lines in literal html
Date: Sun, 09 Dec 2007 18:08:54 -0500 [thread overview]
Message-ID: <475C7586.9010105@gmail.com> (raw)
In-Reply-To: <878x44ekw6.fsf@bzg.ath.cx>
Bastien wrote:
> Hi Wanrong,
>
> Wanrong Lin <wanrong.lin@gmail.com> 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
>> "\\(<p>\\)\\([ \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
next prev parent reply other threads:[~2007-12-09 23:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 19:06 Blank lines in literal html Wanrong Lin
2007-12-05 19:31 ` Wanrong Lin
2007-12-09 1:07 ` Bastien
2007-12-09 23:08 ` Wanrong Lin [this message]
2007-12-10 0:26 ` Bastien
2007-12-10 1:57 ` Wanrong Lin
2007-12-10 14:33 ` Bastien
2007-12-17 8:57 ` Carsten Dominik
2007-12-18 3:00 ` Wanrong Lin
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=475C7586.9010105@gmail.com \
--to=wanrong.lin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).