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 848 invoked from network); 17 May 2023 20:45:54 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 17 May 2023 20:45:54 -0000
Received: from pb-smtp20.pobox.com ([173.228.157.52]) by 9front; Wed May 17 16:40:58 -0400 2023
Received: from pb-smtp20.pobox.com (unknown [127.0.0.1])
	by pb-smtp20.pobox.com (Postfix) with ESMTP id 243F8205BCA
	for <9front@9front.org>; Wed, 17 May 2023 16:40:54 -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=G7KvgqswuXi625Z1b0uzRt3pu
	SE92+S5uNU1cIEUfXA=; b=jNJVjPMz7dkT27KiARnWVe1Mo1rUuJORwVWHU4Ndn
	NafIyaMnS+3wkCFCGj9HIlqOf39HMRPSyc8g51Db9svAYfjbUtlx0wBY+g+tP6iM
	/sqvWZXixj1sqrNqVIKpoBZtF0FeqNLSdFOb8rs/kLvB47DlfaxuugT1Kb3DNoQO
	5I=
Received: from pb-smtp20.sea.icgroup.com (unknown [127.0.0.1])
	by pb-smtp20.pobox.com (Postfix) with ESMTP id 1C2AF205BC9
	for <9front@9front.org>; Wed, 17 May 2023 16:40:54 -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-smtp20.pobox.com (Postfix) with ESMTPSA id 05A2E205BC7
	for <9front@9front.org>; Wed, 17 May 2023 16:40:50 -0400 (EDT)
	(envelope-from unobe@cpan.org)
Message-ID: <24371734A4160CC703EBFBDF65FB87FF@smtp.pobox.com>
To: 9front@9front.org
Date: Wed, 17 May 2023 13:40:48 -0700
From: unobe@cpan.org
In-Reply-To: <2920921AB89918777AF3AA373174BB1A@eigenstate.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID:
 1C843728-F4F3-11ED-810F-C2DA088D43B2-09620299!pb-smtp20.pobox.com
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: enhancement hardware 
Subject: Re: [9front] vnc: fix farsi key symbols
Reply-To: 9front@9front.org
Precedence: bulk

Quoth ori@eigenstate.org:
> Quoth unobe@cpan.org:
> > Quoth ori@eigenstate.org:
> > > Typically, I use tigervnc, which scales the resolution of the remote
> > > virtual X11 server to match the resolution of the output window.
> > 
> > Thanks, ori.
> > 
> > I was trying to go from the other direction using vncv(1), and using
> > Mac OS X's native VNC server.
> > 
> 
> I should clarify: I use tigervnc as the server, and vncv as the
> client. Resizing the client window in vncv(1) will resize the
> server's framebuffer.

Oh, sorry for misunderstanding; that makes sense.  I was looking at
the RFB protocol and saw there is a way to specify the desktop size,
so I think it can be set from the client-side too.  Specifically
/sys/src/cmd/vnc/draw.c:/^requestupdate would need updating to either
allow viewing a different area of the remote frame buffer. Or maybe
there's another configuration knob that can be turned to scale.

Anyway, thanks again for the clarification.