rouble@gmail.com wrote:
> Hi All,

> My mousewheel works fine in local xterms.

> But when I lauch a remote xterm using something like:
> "ssh -X rouble@example.com xterm -j -sb -sl 7000 -geometry 80x24",

> the mousewheel does not work. The xterm just beeps when the mousewheel
> is used to scroll.

> I have these magical lines that I got from
> http://colas.nahaboo.net/mouse-wheel-scroll/#xterm in my .Xdefaults on
> example.com:

It sounds as if your remote xterm isn't using the information from the
..Xdefaults (offhand I'm not sure what). XFree86 xterm has had those
translations as part of its default for some time, so you can actually
have the same problem on local systems too, e.g., if you're using an
old xterm (such as the vendor's on Solaris) vs Linux/FreeBSD/etc.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Thomas Dickey writes:

>It sounds as if your remote xterm isn't using the information from the
>.Xdefaults (offhand I'm not sure what). XFree86 xterm has had those
>translations as part of its default for some time, so you can actually
>have the same problem on local systems too, e.g., if you're using an
>old xterm (such as the vendor's on Solaris) vs Linux/FreeBSD/etc.

It's not a function of the XTerm, only if its configuration.o

(Also, Solaris xterm understand scroll wheels just fine)

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Thomas Dickey writes in comp.windows.x:
|It sounds as if your remote xterm isn't using the information from the
|.Xdefaults (offhand I'm not sure what). XFree86 xterm has had those
|translations as part of its default for some time, so you can actually
|have the same problem on local systems too, e.g., if you're using an
|old xterm (such as the vendor's on Solaris) vs Linux/FreeBSD/etc.

The xterm app-defaults shipped with Solaris 10 or Solaris 9 with the
Xsun wheel mouse update also include the button 4 & 5 translations by
default.

--
__________________________________________________ ______________________
Alan Coopersmith * alanc@alum.calberkeley.org * Alan.Coopersmith@Sun.COM
http://www.csua.berkeley.edu/~alanc/ * http://blogs.sun.com/alanc/
Working for, but definitely not speaking for, Sun Microsystems, Inc.

Alan Coopersmith wrote:
> Thomas Dickey writes in comp.windows.x:
> |It sounds as if your remote xterm isn't using the information from the
> |.Xdefaults (offhand I'm not sure what). XFree86 xterm has had those
> |translations as part of its default for some time, so you can actually
> |have the same problem on local systems too, e.g., if you're using an
> |old xterm (such as the vendor's on Solaris) vs Linux/FreeBSD/etc.

> The xterm app-defaults shipped with Solaris 10 or Solaris 9 with the
> Xsun wheel mouse update also include the button 4 & 5 translations by
> default.

ok - then it's relatively unlikely that it would be omitted in that case.

What I had in mind regarding the beep was this fragment at the end of the
default translations:

!Lock Ctrl opup-menu(fontMenu) \n\
!Lock Ctrl @Num_Lock opup-menu(fontMenu) \n\
! @Num_Lock Ctrl opup-menu(fontMenu) \n\
~Ctrl ~Meta :start-extend() \n\
~Meta :select-extend() \n\
:select-end(PRIMARY, CUT_BUFFER0) \n\
:bell(0)
^^^^^^^^^^^^^^^^^

which is essentially saying that the unrecognized button 4/5 from the
wheel mouse could do that.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Casper H.S. Dik wrote:
> Thomas Dickey writes:

>>It sounds as if your remote xterm isn't using the information from the
>>.Xdefaults (offhand I'm not sure what). XFree86 xterm has had those
>>translations as part of its default for some time, so you can actually
>>have the same problem on local systems too, e.g., if you're using an
>>old xterm (such as the vendor's on Solaris) vs Linux/FreeBSD/etc.

> It's not a function of the XTerm, only if its configuration.o

Actually it's both. The beeps would be from an unrecognized event.

But to make it useful (other than mapping the wheel to one of the
predefined actions - which is only half a solution), it really should
be able to send escape sequences to the application.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Thanks for all the responses guys.

I am not sure I follow what I am doing wrong, or what I should do to
rectify the situation.

How do I get the xterm to honor the settings in the .Xdefaults file ?

fyi, from my earlier example, the server that the xterm is being
launched on is a SunOS 5.6 box.

cheers
rouble

rouble@gmail.com writes:

>Thanks for all the responses guys.

>I am not sure I follow what I am doing wrong, or what I should do to
>rectify the situation.

>How do I get the xterm to honor the settings in the .Xdefaults file ?

>fyi, from my earlier example, the server that the xterm is being
>launched on is a SunOS 5.6 box.

Ah yes, not sure if that can be made to work. Does
xev when launch on the same system report these buttons.

Casper