From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] acme font loading: requesting feedback
Date: Sun, 26 Mar 2023 10:56:54 -0700 [thread overview]
Message-ID: <CAJSxfmLdTs8_VWe_hyWdsoZP1sjE6gCEGhq6f2i9nfL4BHytCQ@mail.gmail.com> (raw)
I ran into a situation that makes me think the default order of acme
font loading is wrong. I ran into it on plan9port when trying to
change default fonts to Go fonts with an existing acme.dump but I
think it's applicable to all Plan 9 forks.
I think when explicit -F -f are given, they should have precedence
over acme.dump. The current behavior can be preserved with 'Load'
where the reload can be forced due to buyer's remorse. I think a quick
hack would be to add a flag to rowloadfonts to force the order.
yes/no?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T6e48857b327d5df7-Mffbb5c9a391456e585cd3f25
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
reply other threads:[~2023-03-26 17:57 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=CAJSxfmLdTs8_VWe_hyWdsoZP1sjE6gCEGhq6f2i9nfL4BHytCQ@mail.gmail.com \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
/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).