mwtex

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by mwtex

  1. That worked - BOTH Methods!  The mouse is actually working in midnight commander thru screen now!  Thank you very much.  

     

     

    Solution 1: (Spectrum)

    type: screen

    type: export TERM=xterm

    then: mc

     

    The export command allows mouse support in the putty terminal.

     

    Solution 2: (Beckp) Seems to combine this into the screen command, so just start screen by

    type: screen -T xterm

    then: mc

     

    It is so easy just to do one of the above, I have not tried to integrate it into a .screenrc file either.

    Thank you both!

  2. ---------------------------------------------------------------

    Solution added to first post - thanks to Beckp & Spectrum

    ---------------------------------------------------------------

    Problem: Lack of mouse support in putty using screen (especially usefully for midnight commander)

    Solution: Instead of invoking screen by just typing: 'screen'  use: 'screen -T xterm'

                Then when you type 'mc' to run midnight commander mouse support works great!  Very useful!

    ----------------------------------------------------------------

     

     

    When using putty to telnet into my unraid box - if I run midnight commander (mc), I have full mouse support.  If I run screen first, then run mc, mouse support is lost.

     

    Can anyone tell me how to fix this - how to make mc mouse support work when mc is launched after screen?

     

    I searched around and found this info elsewhere:

    I've found that this problem can be fixed by adding a line like this to your .screenrc: 
    termcapinfo linux|xterm|rxvt|xterm-color ti@:te@:XT 
    The XT part tells screen that the 'real' terminal understands XTerm specific stuff like mouse reporting. 
    This works for me with PuTTY on Windows connected to Ubuntu GNU/Linux using the "linux" style terminal. 
    Note that you can override the application's use of the mouse by holding down shift, assuming the appropriate PuTTY option is checked. This is useful when e.g. copying some text out of a console Emacs session into a Window application. 
    

     

     

    I gave it a shot by doing the following:

    I found the .screenrc in /etc/skel   and copied it to my /home directory

    (I also tried adding the line to the version in /etc)

    I then edited the file by adding: termcapinfo linux|xterm|rxvt|xterm-color ti@:te@:XT

    no joy.

     

    I'm not sure if my new config file is even being loaded by the screen setup installed by the unmenu package manager.  Also not sure if the added line still applies to the version of screen i'm using...

    Obviously, i'm pushing at the limits (past them) of my nix knowledge.  ANY HELP would be appreciated!

    Thanks!