9front - general discussion about 9front
 help / color / mirror / Atom feed
From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] vnc: fix farsi key symbols
Date: Wed, 17 May 2023 12:37:56 -0700	[thread overview]
Message-ID: <F0301CCE90C536319047E401F8A8BCDE@smtp.pobox.com> (raw)
In-Reply-To: <238c17d3-d6b1-b12e-1c1a-39b1b658202b@posixcafe.org>

Quoth Jacob Moody <moody@mail.posixcafe.org>:
> I also saw other codepoints that were defaulted to the new mapping
> when perusing the file.  Perhaps a full sync is in order?  Is there
> value in keeping these old tables around for old software?  I am not
> too sure.

Yeah, perhaps a full(er) sync.

> It should be possible to create virtual 'headless' vnc servers of arbitrary resolutions.
> Maybe that will work in your case. I tend to go the other way with drawterm most of the time.

I haven't tried configuring the headless approach more--the remote
buffer is a macbook.  But yeah, I generally use drawterm, yet I have
had an issue with drawterm on dual monitors if the drawterm window is
on the external monitor--the mouse moves to the laptop's main monitor
on an action that moves the cursor (e.g., right-clicking in acme).  I
investigated briefly sometime last year to see if I could fix, and
could not.  IIRC, the mouse position always considers its movement in
the context of the main monitor.  So that restricts my usage of
drawterm to the main (laptop) monitor which has a higher resolution,
but not as big.


  reply	other threads:[~2023-05-17 19:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  0:43 unobe
2023-05-17  2:08 ` Jacob Moody
2023-05-17  2:38   ` unobe
2023-05-17  4:31     ` Jacob Moody
2023-05-17 19:37       ` unobe [this message]
2023-05-17 14:35     ` ori
2023-05-17 19:38       ` unobe
2023-05-17 20:15         ` ori
2023-05-17 20:40           ` unobe
2023-05-18 10:27             ` ori
2023-05-19  3:32               ` unobe
2023-05-24 13:34 ` mkf9

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=F0301CCE90C536319047E401F8A8BCDE@smtp.pobox.com \
    --to=unobe@cpan.org \
    --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).