From: bauen1 <j2468h@googlemail.com>
To: James Carter <jwcart2@gmail.com>, bauen1 <j2468h@googlemail.com>
Cc: SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH 0/2] secilc/docs: add syntax highlighting for cil examples
Date: Sat, 6 Feb 2021 21:29:18 +0100 [thread overview]
Message-ID: <a8abefda-5c2b-918d-65d9-e21b89e9a2bf@gmail.com> (raw)
In-Reply-To: <CAP+JOzT3Ee=WnMfnME3N=MCytb1um3F=iBZnNUzV6xN6R8PYpg@mail.gmail.com>
On 2/5/21 12:19 AM, James Carter wrote:
> On Thu, Feb 4, 2021 at 4:28 PM bauen1 <j2468h@googlemail.com> wrote:
>
>>
>> https://glados.bauen1.xyz/misc_stuff_might_disappear/CIL_Reference_Guide3.html
>>
>
> I like version 3 the best, but I really don't like the color used for
> "self", "object_r", "h1" , etc. It just stands out too much.
This was originally meant to be a test color scheme to showcase all different "classes" of keywords that could be highlighted, not intended as an actual color theme.
I've changed the purple to a lighter pink:
https://glados.bauen1.xyz/misc_stuff_might_disappear/CIL_Reference_Guide4.html
In case someone can come up with 6 different colors that go well together, I can put together an updated theme (Colors for Strings+SpecialChars, Function, Operator, BuiltIns, Comment, Keyword).
I will send a v2 of the patch, including the color theme as a separate patch.
> ...
> I find it easier to maintain if the items were sorted in alphabetical
> order (this enables inserting new items if the need comes one day,
> without wondering whether the new items should be at the end of the
> list or if the order should match the one used in some source
> files...). Or, if you want to keep this order, please add comments
> describing how the lists were created, in order to ease future
> modifications.
Thanks for the feedback, will be implemented.
--
bauen1
https://dn42.bauen1.xyz/
next prev parent reply other threads:[~2021-02-06 20:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 17:05 [PATCH 0/2] secilc/docs: add syntax highlighting for cil examples bauen1
2021-02-04 20:17 ` James Carter
2021-02-04 21:28 ` bauen1
2021-02-04 23:19 ` James Carter
2021-02-05 9:31 ` Nicolas Iooss
2021-02-06 20:29 ` bauen1 [this message]
2021-02-06 21:04 ` [PATCH v2 1/3] secilc/docs: use fenced code blocks " bauen1
2021-02-08 17:40 ` James Carter
2021-02-08 19:38 ` bauen1
2021-02-11 23:35 ` James Carter
2021-02-06 21:04 ` [PATCH v2 2/3] secilc/docs: add syntax highlighting for secil bauen1
2021-02-08 17:43 ` James Carter
2021-02-08 19:35 ` bauen1
2021-02-08 19:45 ` James Carter
2021-02-08 19:46 ` James Carter
2021-02-11 23:35 ` James Carter
2021-02-16 14:41 ` James Carter
2021-02-06 21:05 ` [PATCH v2 3/3] secilc/docs: add custom color theme bauen1
2021-02-08 17:44 ` James Carter
2021-02-10 15:58 ` [PATCH v3 1/3] secilc/docs: use fenced code blocks for cil examples bauen1
2021-02-11 23:38 ` James Carter
2021-02-16 14:40 ` James Carter
2021-02-10 15:59 ` [PATCH v3 2/3] secilc/docs: add syntax highlighting for secil bauen1
2021-02-10 15:59 ` [PATCH v3 3/3] secilc/docs: add custom color theme bauen1
2021-02-11 23:37 ` James Carter
2021-02-16 14:41 ` James Carter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8abefda-5c2b-918d-65d9-e21b89e9a2bf@gmail.com \
--to=j2468h@googlemail.com \
--cc=jwcart2@gmail.com \
--cc=selinux@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox