From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] vultr node and mouse acceleration
Date: Thu, 8 Feb 2018 20:49:49 -0800 [thread overview]
Message-ID: <CAHwi9bxQ-=ikPAU9ky0rRB=RDd=ptNkjAFRw34a2-+dVRn2yqw@mail.gmail.com> (raw)
In-Reply-To: <CAHwi9bxZfkjU_wkK0fKcnRiDZNg7uKkyOHfh4xuYSYUwEh-m0A@mail.gmail.com>
Oh no, I got an apology instead of a fix:
Hello,
Thanks for contacting us. We are aware of these issues, yes -- we
recently applied an update to noVNC that removed support for older
versions of Windows. Certain other operating systems, including Plan 9
and its derivatives like 9front, are also affected. We apologize for
the inconvenience.
[redacted]
System Administrator
On Thu, Feb 8, 2018 at 8:44 PM, Eli Cohen <echoline@gmail.com> wrote:
> linear is not working. i thought of booting the installation media to
> see if it does it too, and it does, so i think this is a vultr issue
>
>
> On Thu, Feb 8, 2018 at 6:51 PM, Sean Hinchee <henesy.dev@gmail.com> wrote:
>> Is linear not working for disabling mouse acceleration? You could
>> always add the echo call to lib/profile.
>>
>> On Wed, Feb 7, 2018 at 3:27 PM, Eli Cohen <echoline@gmail.com> wrote:
>>> has there been a change to the way mouse acceleration is handled? i
>>> was occasionally starting up rio in vultr's web-based vnc session, and
>>> i would routinely have to:
>>>
>>> echo -n linear > '#m/mousectl'
>>>
>>> especially when booting as a terminal. now it seems to do the same
>>> thing even by default as a cpu server, and turning off mouse
>>> acceleration does not help.
>
>
>
> --
> http://echoline.org
--
http://echoline.org
next prev parent reply other threads:[~2018-02-09 4:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 21:27 Eli Cohen
2018-02-09 2:51 ` [9front] " Sean Hinchee
2018-02-09 4:44 ` Eli Cohen
2018-02-09 4:49 ` Eli Cohen [this message]
2018-02-09 21:33 ` hiro
2018-02-10 3:28 ` Eli Cohen
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='CAHwi9bxQ-=ikPAU9ky0rRB=RDd=ptNkjAFRw34a2-+dVRn2yqw@mail.gmail.com' \
--to=echoline@gmail.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).