This is the point of the conversation where I butt my head in and
look stupid. :-)
----- Original Message ----
Micah Cowan wrote:
> >> Wait, where are you running screen? My assumption was that you be
> >> running it ON prime.gushi.org
, not before you ssh in.
> Right. I'm doing both.
> >> When I ssh from my mac to prime, nano -m works.
> >> When I ssh from my mac to prime and start screen -q, nano -m doesn't.
> When you set TERM=xterm? (That was what we were talking about)
> Within screen running on gushi, "TERM=xterm nano -m" gives me mouse
> capabilities (but isn't a great idea long-term, as it may well screw up
> other things subtly).
This may be a silly question, but how does "screen" decide that the
attaching terminal supports capturing mouse events? It could be that
nano says it's interested, but screen thinks they're not available.
I'm no expert in the screen code base, but is this where?
if (InStr(D_termname, "xterm") || InStr(D_termname, "rxvt"))
D_CXT = 1;
What do you have TERM set to when you launch screen? If you say
"TERM=xterm screen" to start screen, does that change things?
We sell spatulas, and that's all!http://spatula-city.org/~im14u2c/http://spacepatrol.info/