9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Philip Silva <philip.silva@protonmail.com>
To: "9front@9front.org" <9front@9front.org>
Subject: [9front] Re: hidpi
Date: Mon, 20 Dec 2021 17:04:32 +0000	[thread overview]
Message-ID: <TGEM6kZK7iI0t53xmm70veDOu25b4yHhMuBPuIRX5hWBtU57FO_erZQLO0cxk1d0KwLX2k8KOKqmO7XHSFZx1AqkE9IESpSj54eI5I9PTGc=@protonmail.com> (raw)
In-Reply-To: <fY4WlDcUa0tGFTLGmEv-NDWLzJwXsUPnq2RK3-w9N1E35Bo3N8nIXTI-BwvNAmMRQtDb_oIH63c0uucUhbK38DilSs3LuWfGeJ1vAluIggw=@protonmail.com>

> you didn't document this in the devdraw man page.

True, I could add this.

> are you sure though that we need to do this on devdraw level?

Not really sure to be honest, I only have a rough idea about libdraw or how to exchange configuration options. At least in plan9port there is also the new q(1d) command to query DPIs and 9fans.net/go/draw uses it as well. I wonder whether this could be realized by just using environment variables instead of configuring this through plan9.ini/the result of q1d in drawterm.

https://github.com/9fans/go/blob/v0.0.4/draw/init.go#L300


  parent reply	other threads:[~2021-12-20 17:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-20 16:13 [9front] hidpi Philip Silva
2021-12-20 16:34 ` hiro
2021-12-20 17:04 ` Philip Silva [this message]
2021-12-20 17:29   ` [9front] hidpi hiro
2021-12-20 19:15   ` Noam Preil
2021-12-20 19:34     ` ori
2021-12-20 20:50       ` ori
2021-12-20 21:10         ` hiro
2021-12-20 21:19           ` ori
2021-12-20 22:02             ` sirjofri
2021-12-21  0:29         ` Philip Silva
2021-12-21  8:37           ` hiro
2021-12-20 21:47       ` Noam Preil
2021-12-20 17:59 ` [9front] hidpi igor
2021-12-20 18:28   ` hiro
2021-12-20 19:27     ` Noam Preil
2021-12-20 19:02   ` Philip Silva
2021-12-22  8:39 ` igor
2021-12-22 11:31   ` Philip Silva

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='TGEM6kZK7iI0t53xmm70veDOu25b4yHhMuBPuIRX5hWBtU57FO_erZQLO0cxk1d0KwLX2k8KOKqmO7XHSFZx1AqkE9IESpSj54eI5I9PTGc=@protonmail.com' \
    --to=philip.silva@protonmail.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).