From: ori@eigenstate.org
To: kim.lassila@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] iOS drawterm
Date: Wed, 25 Mar 2020 10:40:21 -0700 [thread overview]
Message-ID: <AA2A4AFDB97A6CB53FE2939ACC471DC5@eigenstate.org> (raw)
In-Reply-To: <C0129E6D-C2FF-4453-8C88-699E570404D7@gmail.com>
> Yes, I have tested vncs and vncv in 9front. They were written for the old protocol version 3.3 which does not support local mouse cursor or resizing the screen. It would improve the usability quite a bit if support for the latest protocol was added to these programs. Mouse cursor drawn by vncs is red, choppy and lags the real hardware cursor. It would be a lot better if vncs supported the local mouse cursor extension available in the newer protocol version.
When did you test? Support for resizing landed in the client, at least, in
2018, and works fine for me.
changeset: 6677:5b0b9082b2c3
user: cinap_lenrek@felloff.net
date: Mon Aug 20 19:23:42 2018 +0200
summary: vncs: support for desktop resize extension, update devdraw
I use it regularly when I need to view web pages -- I VNC into a Vultr VPS
running Chrome.
I can't speak to the server side support, though, since I usually just use
rcpu when speaking to plan 9 systems, or drawterm when on Unix. Especially
over fast networks, I find it much more responsive, and exposing local
devices through /mnt/term makes using it much nicer.
next prev parent reply other threads:[~2020-03-25 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 6:19 Anthony Sorace
2020-03-25 11:19 ` [9fans] " Kim Lassila
2020-03-25 12:41 ` Jeremy O'Brien
2020-03-25 16:32 ` Kim Lassila
2020-03-25 17:40 ` ori [this message]
2020-03-25 17:25 ` Anthony Sorace
2020-03-25 17:49 ` Ethan Gardener
2020-03-27 12:25 ` Ole-Hjalmar Kristensen
2020-03-25 17:51 ` Skip Tavakkolian
2020-03-27 5:51 ` Anthony Sorace
2020-03-27 12:21 ` Ethan Gardener
2020-03-31 8:52 ` yy
2020-03-31 10:58 ` Ethan Gardener
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=AA2A4AFDB97A6CB53FE2939ACC471DC5@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
--cc=kim.lassila@gmail.com \
/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).