From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] mothra: proposal
Date: Sat, 21 Mar 2020 11:27:20 +0000 [thread overview]
Message-ID: <74c8462c-1301-458d-bbf4-0d41b414915e@www.fastmail.com> (raw)
In-Reply-To: <F33C8113101B37111E4E412220D1377D@ewsd.inri.net>
On Fri, Mar 20, 2020, at 1:27 AM, sl@stanleylieber.com wrote:
>
> >>> 3.) implement -b flag for dark mode, white-on-black text.[2]
> >>> a.) similar to rio -b, and vt -b.
> >
> > I don't like theming, but I like the propagation of dark mode
> > flags even less. If we want this, libdraw needs to signal to
> > programs which colors they should use, without a '-b' flag.
>
> i'm not capable of implementing this. also, by this logic we'd
> need to change existing behavior of rio ad vt. would we delete
> the existing flags? i'm not married to -b, but i'm also not
> advocating full-blown theming. (fwiw, i also don't quite
> understand the vehement objection to it; standardizing it
> in one library seems like the right approach.)
i'm much more opposed to flags than theming, personally. I've set a lot of x programs to dark colors, and some of them can't be done with files or x resources. i don't like to start a whole bunch of programs and leave them running, (or rather, i didn't at the time,) so i had these wrapper scripts which started programs with the options i wanted. (not just color, other things too.) writing those scripts was irritating, especially when i had to make a new one.
> to think, many years ago i thought mothra would be a good entry
> point to c. my changes to it are still the most c i've ever
> written in one place.
it could have been worse, you could have started with sam-samterm communications. i couldn't even begin to make heads or tails of that.
next parent reply other threads:[~2020-03-21 11:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F33C8113101B37111E4E412220D1377D@ewsd.inri.net>
2020-03-21 11:27 ` Ethan Gardener [this message]
[not found] <42A469F0BBA88991B13EB7B76C0079B3@ewsd.inri.net>
2020-04-12 19:16 ` ori
2020-04-12 19:21 ` ori
2020-04-12 19:42 ` Stanley Lieber
2020-04-13 0:43 ` sl
[not found] <C85FC655E82FCBE5B94289CB1073F9CC@ewsd.inri.net>
2020-03-20 3:00 ` ori
2020-03-20 3:21 ` Stanley Lieber
2020-03-20 5:04 ` umbraticus
2020-03-19 13:24 Stanley Lieber
2020-03-19 22:48 ` ori
2020-03-20 1:27 ` sl
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=74c8462c-1301-458d-bbf4-0d41b414915e@www.fastmail.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).