From: Bastien <email@example.com>
To: Kyle Meyer <firstname.lastname@example.org>
Cc: org-mode-email <email@example.com>, TEC <firstname.lastname@example.org>
Subject: Re: [PATCH] Apply emacs manual css to org pages
Date: Wed, 24 Mar 2021 09:08:49 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Kyle Meyer's message of "Tue, 29 Dec 2020 06:07:54 GMT")
Kyle Meyer <email@example.com> writes:
>> # How to create the HTML file
>> -TEXI2HTML = makeinfo --html --number-sections
>> +TEXI2HTML = makeinfo --html --number-sections --css-ref "https://www.gnu.org/software/emacs/manual.css"
I made this change and tested it online, the HTML Org manual now looks
like the Emacs manual: https://orgmode.org/manual/
Thanks for the suggestion!
> Hmm, while I barely ever look at the online manual, I thought I recalled
> it having custom styling, and indeed it looks like that was the case:
> At least based on the Wayback Machine rendering, it seems like the
> custom CSS was lost shortly after the snapshot above.
> If you look in the repo for org-manual.css, you can see there is still
> handling for it.
Yes, I remember I tried to enhance the css for the manual, and I don't
remember why this change was reverted.
> So, if we're going to go in the direction of this patch, there should be
> some mention of the previous approach, why it was dropped, and the
> handling for org-manual.css should probably be removed. Perhaps Bastien
> can help fill in some details here.
In any cas, the Emacs manual css is better than my attempt and using
it for Org makes sense IMO.
next prev parent reply other threads:[~2021-03-24 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 2:35 TEC
2020-12-23 3:42 ` Greg Minshall
2021-04-25 3:36 ` Timothy
2020-12-27 15:51 ` Amin Bandali
2020-12-27 21:29 ` Samuel Wales
2020-12-27 21:39 ` Samuel Wales
2020-12-27 21:45 ` Samuel Wales
2020-12-28 4:04 ` TEC
2020-12-28 4:31 ` Samuel Wales
2020-12-29 6:07 ` Kyle Meyer
2021-03-24 8:08 ` Bastien [this message]
2021-04-25 3:34 ` Timothy
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).