From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 31127 invoked from network); 17 May 2023 19:41:17 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 17 May 2023 19:41:17 -0000
Received: from pb-smtp21.pobox.com ([173.228.157.53]) by 9front; Wed May 17 15:38:07 -0400 2023
Received: from pb-smtp21.pobox.com (unknown [127.0.0.1])
	by pb-smtp21.pobox.com (Postfix) with ESMTP id F310D1EA2F0
	for <9front@9front.org>; Wed, 17 May 2023 15:38:01 -0400 (EDT)
	(envelope-from unobe@cpan.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=message-id
	:to:subject:date:from:in-reply-to:mime-version:content-type
	:content-transfer-encoding; s=sasl; bh=QOGFZmZi+AI4o9CrB44c7mQ5o
	PflFKcR6Nx6Pk8r3/Y=; b=WLxCJyCqzHCf+uhHVYpB4EX9qpAVRmj0fJy84LDN4
	g9MCopoxc7PxUynuPwGoCcPHq9FBKWy3qeSsbQAfrsXGNkQ2D24Uy/+TQITVxN6D
	AUwqWFecFw8OkvNSGngTSEgoeWGnD6tMDUo/Y3kCDdMWNFtwdVVBldbc30tH2xBy
	+k=
Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1])
	by pb-smtp21.pobox.com (Postfix) with ESMTP id EC9961EA2EF
	for <9front@9front.org>; Wed, 17 May 2023 15:38:01 -0400 (EDT)
	(envelope-from unobe@cpan.org)
Received: from strider.localdomain (unknown [75.204.169.210])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pb-smtp21.pobox.com (Postfix) with ESMTPSA id 8EE821EA2EB
	for <9front@9front.org>; Wed, 17 May 2023 15:37:58 -0400 (EDT)
	(envelope-from unobe@cpan.org)
Message-ID: <F0301CCE90C536319047E401F8A8BCDE@smtp.pobox.com>
To: 9front@9front.org
Date: Wed, 17 May 2023 12:37:56 -0700
From: unobe@cpan.org
In-Reply-To: <238c17d3-d6b1-b12e-1c1a-39b1b658202b@posixcafe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID:
 53F77E1C-F4EA-11ED-B58E-B31D44D1D7AA-09620299!pb-smtp21.pobox.com
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: structured stateless engine-oriented callback YAML property rich-client locator 
Subject: Re: [9front] vnc: fix farsi key symbols
Reply-To: 9front@9front.org
Precedence: bulk

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.