9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] drawterm mouse settings
Date: Wed, 13 Jul 2016 11:56:01 +0200	[thread overview]
Message-ID: <CAFSF3XPNrnjw3Mnc6Tkzh9beTeo64+e4og3uh-CFUk5KZijFdA@mail.gmail.com> (raw)
In-Reply-To: <82ce0e72-31d0-4c6e-88f4-8e89590a64ca@email.android.com>

If I understand correctly this is how the mouse works:

        case MotionNotify:
                me = (XMotionEvent *)e;
                s = me->state;
                ms.xy.x = me->x;
                ms.xy.y = me->y;
                ms.msec = me->time;
                break;



On 7/13/16, stanley lieber <sl@stanleylieber.com> wrote:
> Dave MacFarlane <driusan@gmail.com> wrote:
>
>>On Tue, Jul 12, 2016 at 8:22 PM, stanley lieber <sl@stanleylieber.com>
>>wrote:
>>> hiro <23hiro@gmail.com> wrote:
>>>
>>>>I was under the impression this is handled by your OS (Xorg for
>>>>example), not inside drawterm.
>>>
>>> So, mousectl is simply not implemented?
>>>
>>> sl
>>>
>>
>>What would it do? Change the settings on the 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 currently implemented
> facilitate the current behavior of the mouse inside the drawer term session.
> If I understand correctly, all that is missing here is implementing those
> bits (namely, ctl messages).
>
> Maybe I'm misunderstanding and this is impossible, but if so, how can the
> mouse work at all? Drawterm already intercepts and interprets the mouse,
> right?
>
> sl
>
>


  reply	other threads:[~2016-07-13  9:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12  4:33 sl
2016-07-12 10:11 ` [9front] " hiro
2016-07-13  0:22   ` stanley lieber
2016-07-13  0:58     ` Dave MacFarlane
2016-07-13  1:34       ` stanley lieber
2016-07-13  9:56         ` hiro [this message]
2016-07-17 21:42           ` Adam Mrówka
2016-07-18  9:09             ` cinap_lenrek

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=CAFSF3XPNrnjw3Mnc6Tkzh9beTeo64+e4og3uh-CFUk5KZijFdA@mail.gmail.com \
    --to=23hiro@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).