From: Samuel Wales <email@example.com>
To: TEC <firstname.lastname@example.org>
Cc: org-mode-email <email@example.com>
Subject: Re: [PATCH] Apply emacs manual css to org pages
Date: Sun, 27 Dec 2020 14:39:40 -0700 [thread overview]
Message-ID: <CAJcAo8t++f4ceP1gMMoxO6sZUoCRJTgdHxNkU7tSj6MCpHn4YA@mail.gmail.com> (raw)
if i were to make any /tiny nit-level/ suggestions from my pov it
would be somewhat wider margins, not pure white but slightly [so still
/very/ high contrast] warmer for fg, and some less-blue for links [but
i realize blue is common].
i would also do [ha ha, as if i knew what to do or even whether it is
possible] wrapping for left columns that go under text rather than
bullet for e.g this line: "• Extracting Agenda Information
Post-processing agenda information." set fonts large.
these are without regard for emacs manual as i have not seen that
online recently. great job. thank you.
On 12/27/20, Samuel Wales <firstname.lastname@example.org> wrote:
> i like the black bg, the no issues with paragraph width.
> On 12/22/20, TEC <email@example.com> wrote:
>> Hi all,
>> This is a quick patch to use the Emacs manual CSS with our generated Org
>> You can see what the single-page version of this looks like here:
>> https://tecosaur.com/resources/org/doc/manual.html and the multi-page
>> here: https://tecosaur.com/resources/org/doc/manual/
>> This should be an easy upgrade to our online documentation :)
> The Kafka Pandemic
> Please learn what misopathy is.
The Kafka Pandemic
Please learn what misopathy is.
next prev parent reply other threads:[~2020-12-27 21:40 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 [this message]
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
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).