9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p on Retina Macs
Date: Fri,  6 Sep 2013 00:14:12 -0400	[thread overview]
Message-ID: <CADSkJJXnpdFUtNowbLZFbUXMBghP8o45cMPTmYdNtuMA51Z9UA@mail.gmail.com> (raw)
In-Reply-To: <3874A7DD-47F1-4320-9DB6-E9E34D22FB3D@monkey.org>

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

What Marius wrote is mostly accurate. If you set devdrawretina=1 you get
tinier pixels; acme, sam, and 9term know to draw thicker lines in response;
other programs do not.

If you want fonts that look somewhat like the Plan 9 bitmaps, I use this
with acme:

#!/bin/bash
export devdrawretina=1
/usr/local/plan9/bin/acme -f /mnt/font/LucidaGrande/25a/font -F
/mnt/font/Menlo-Regular/25a/font "$@"

It would be nice if acme, sam, 9term adjusted the font size to match the
display DPI accordingly. I have code that does this (I lied above; I
actually start acme with size 15a fonts and it scales to decide to use the
25a fonts), but I am not happy enough with it yet. The main thing that is
missing is that if the window changes from retina to non-retina or vice
versa (for example, you use a retina laptop with an external monitor and
drag a window from one screen to the other), acme and sam know to redraw
with thicker or thinner lines but I don't quite have to font adjustment
during resize correct.

The lack of on-the-fly font resizing is a continual source of pain for me
(I end up having to restart acme a lot), and at some point I will finish
it. Ideally I want to get to the point where devdrawretina=1 acme (no other
arguments) just works.

For fun, try 'devdrawretina=1 9term -f /mnt/font/Menlo-Regular/80a/font'
and then in that window run 'unicode fffe'.

Russ

[-- Attachment #2: Type: text/html, Size: 1608 bytes --]

  reply	other threads:[~2013-09-06  4:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 17:05 marius eriksen
2013-08-16 21:35 ` Rob Pike
2013-09-06  3:32   ` marius a. eriksen
2013-09-06  4:14     ` Russ Cox [this message]
2013-09-06  4:18       ` marius eriksen
2013-09-06 11:24       ` James A. Robinson

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=CADSkJJXnpdFUtNowbLZFbUXMBghP8o45cMPTmYdNtuMA51Z9UA@mail.gmail.com \
    --to=rsc@swtch.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).