9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sl@stanleylieber.com
To: 9front@9front.org
Subject: mothra: proposal
Date: Wed, 18 Mar 2020 19:49:16 -0400	[thread overview]
Message-ID: <20200318234916.KUDAcAtPbXhUVNHQRYb4EAZIBtRdB1bhaG76-paKdLc@z> (raw)

i've been maintaining forks of mothra for years.  i don't anticipate
making more big changes any time soon, and i have zero time to
continue applying the changes from 9front to my several forks.

i propose to backport the following changes from my forks to 9front:

	1.) restore original default fonts.
		a.) our dejavusans is fuzzy as hell, and it sucks.
			1.) users can easily choose their own fonts
			and
			recompile.

	2.) backport my changes to libpanel to remove useless panel
	borders and fake shadow lines.  stop underlining hyperlinks,
	and instead make them blue.[0][1]
		a.) perhaps in a saner manner.
			1.) currently, lines, borders, bullet points,
			etc., are defined in all sorts of different
			places, not even entirely inside of libpanel.
			i made no attempt to address this.  in rio,
			we ended up putting all the color definitions
			into one file, for easy modification.

	3.) implement -b flag for dark mode, white-on-black text.[2]
		a.) similar to rio -b, and vt -b.
			1.) users are free to implement any desired
			schemes beyond default and -b by configuring
			the included .c files.

caveat: i do not have a lot of faith in my own ability to backport
these changes cleanly.

volunteers are welcome.

sl

[0] http://plan9.stanleylieber.com/src/mothra.white.tgz
[1] http://plan9.stanleylieber.com/src/mothra.black.tgz
[2] http://plan9.stanleylieber.com/mothra/img/20200310.png


                 reply	other threads:[~2020-03-18 23:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200318234916.KUDAcAtPbXhUVNHQRYb4EAZIBtRdB1bhaG76-paKdLc@z \
    --to=sl@stanleylieber.com \
    --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).