From: Ihor Radchenko <yantar92@posteo.net>
To: YE <yet@ego.team>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] No newline at end of exported HTML file [9.6.6 (release_9.6.6 @ /Applications/MacPorts/Emacs.app/Contents/Resources/lisp/org/)]
Date: Mon, 09 Oct 2023 11:29:14 +0000 [thread overview]
Message-ID: <878r8cm3ud.fsf@localhost> (raw)
In-Reply-To: <m2bkd8hph3.fsf@ego.team>
YE <yet@ego.team> writes:
>> May you please explain why missing newline is a problem?
>
> It's not necessarily a problem, since HTML parser implementations are
> permissive. Still, a couple of arguments for adding it by default:
>
> 1. diff tools output "\ No newline at end of file" message when a
> newline is missing. Supposedly, it's not optimal for default behavior.
IMHO, I see no problem with that message.
> 2. POSIX.1-2017 states:
> "3.206 Line
> A sequence of zero or more non- <newline> characters plus a terminating
> <newline> character."
Does POSIX has anything to do with HTML?
Were you to show us HTML standard, it would be more convincing.
> 3. Ending a line of text with a particular identifier is rather a
> canonical approach.
Not ending is also not uncommon though. And causes no harm (no bug
reports during all the >10 years when ox-html is a thing).
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-10-09 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 15:53 [BUG] No newline at end of exported HTML file [9.6.6 (release_9.6.6 @ /Applications/MacPorts/Emacs.app/Contents/Resources/lisp/org/)] YE
2023-10-07 8:27 ` Ihor Radchenko
2023-10-08 19:40 ` YE
2023-10-09 11:29 ` Ihor Radchenko [this message]
2023-10-09 11:41 ` Max Nikulin
2023-10-09 11:46 ` Ihor Radchenko
2023-10-09 11:53 ` Max Nikulin
2023-10-09 12:06 ` Ihor Radchenko
2023-10-09 12:23 ` Bruno Barbier
2023-10-09 12:47 ` Ihor Radchenko
2023-10-10 11:21 ` Ihor Radchenko
2023-10-11 8:10 ` YE
2023-10-15 8:14 ` Ihor Radchenko
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=878r8cm3ud.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=yet@ego.team \
/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).