From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ds.inri.net ([107.191.103.21]) by ur; Tue Jul 12 21:34:16 EDT 2016 Received: from [10.168.221.177] ([166.170.222.69]) by ds; Tue Jul 12 21:34:15 EDT 2016 User-Agent: K-9 Mail for Android In-Reply-To: References: <53e1050bb6a13f58ad4026ea6814b8dd@dl.attlocal.net> <9eacbf8e-72f0-41f7-b7a5-b8c119a1b1b4@email.android.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Subject: Re: [9front] drawterm mouse settings From: stanley lieber Date: Tue, 12 Jul 2016 21:34:12 -0400 To: 9front@9front.org Message-ID: <82ce0e72-31d0-4c6e-88f4-8e89590a64ca@email.android.com> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: lossless non-blocking information deep-learning database Dave MacFarlane wrote: >On Tue, Jul 12, 2016 at 8:22= PM, stanley lieber >wrote: >> hiro <23hiro@gmail= =2Ecom> wrote: >> >>>I was under the impression this is handled by your OS = (Xorg for >>>example), not inside drawterm=2E >> >> So, mousectl is simply = not implemented? >> >> sl >> > >What would it do? Change the settings on th= e OS of the machine that >you're connecting >from? > >- Dave No, why would= anyone expect activity inside the drawterm session to change the behavior = of the host OS? The expected result would be to change the behavior of the= mouse inside the drawterm session, just as the mouse(3) bits that are curr= ently implemented facilitate the current behavior of the mouse inside the d= rawer term session=2E If I understand correctly, all that is missing here i= s implementing those bits (namely, ctl messages)=2E Maybe I'm misunderstan= ding and this is impossible, but if so, how can the mouse work at all? Draw= term already intercepts and interprets the mouse, right? sl