Re: New release

2012-07-31 Thread Brian Kroth

Carsten Mattner carstenmatt...@gmail.com 2012-07-21 14:52:

I've been using screen for many years and it has been almost
4 years since the last official release.

Are there any plans for a new release?
Or should I just use screen from the master branch to get
a recent version?


I completely agree with the sentiment.  I think it's (perhaps 
artificially) holding up inclusion in the major linux distros of a 
modern screen, which really has some nice new features to offer.


Debian's experimental branch at least has a git based package now, 
adapted from a recent fedora package, which, from a quick glance, is the 
only major distro out there to have one.


Thanks,
Brian


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
https://lists.gnu.org/mailman/listinfo/screen-users


Re: New release

2012-07-31 Thread Brian Kroth

Axel Beckert a...@deuxchevaux.org 2012-07-31 16:45:

Hi,

On Tue, Jul 31, 2012 at 08:43:25AM -0500, Brian Kroth wrote:

Debian's experimental branch at least has a git based package now,


It's in Debian Unstable for about 1.5 months now and in Debian Testing
for about three weeks. :-)


from a quick glance, is the only major distro out there to have one.


Ubuntu will likely adopt the package from Debian, but maybe not for
their upcoming 12.10 release anymore.

Thanks to Julien Cristau there is now a patch for the 4.0.3
interoperability issue:

http://anonscm.debian.org/gitweb/?p=collab-maint/screen.git;a=commitdiff;h=8700b331b4071c8158be4d6891cb7909859165a9

It looks fine after some initial testing and I'll soon upload a
package to Debian Unstable including this patch. The package will
likely make it in the next Debian Stable release.

While testing that patch, I though noticed a few unexpected things
with regards to locking screen which also happen without the patch.
More details later though as I'm currently busy with other things.


That's great news!  The upgrade interoperability issue was holding me up 
from pushing that everywhere as well.  I will definitely test that out 
later in August once I have a chance.


We have hundreds of machines that we use screen on, so for ease of 
maintenance purposes we tend to roll with whatever the distro has in 
their package system, rather than either trying to maintain our own 
package or keeping a git copy around everywhere.  For me, that's the 
main reason in wanting a stable release.  I know at least some, if not 
many, others are in a similar boat.  So yes, in that sense, it is a 
little like the OS X issue someone described earlier.


Anyways, thanks a lot,
Brian


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
https://lists.gnu.org/mailman/listinfo/screen-users


Re: Beginner Question: Is GNU Screen still in active development? Will there be future releases?

2011-10-13 Thread Brian Kroth

Andrew Schulman and...@alumni.utexas.net 2011-10-13 09:46:

Regarding the subject, just wanted to know this because I am trying to
decide whether to go with Screen or Tmux.   So far in my experience,
Screen seems more mature (but I might not be qualified enough to say
this :-) ) .


I admit a release has been slow in coming, and because of that I have 
also been considering a switch to tmux for a handful of features I've 
been waiting for.  However, screen is mature and I know it well and 
haven't had enough time to switch yet.  I also don't know if I could get 
tmux for some of the Solaris machines I have to deal with.  Also, most 
of the features I wanted have been in the git version of screen for a 
while so development on screen does continue to progress albeit slowly.
In an effort to move things along some of us have started work to try 
and package a git version for distros like Debian:

http://noone.org/blog/English/Computer/Debian/Git%20Snapshot%20of%20GNU%20Screen%20in%20Debian%20Experimental.html
http://packages.debian.org/experimental/screen

I'm using it (backported for squeeze) on a large lab setup already.

Brian


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
https://lists.gnu.org/mailman/listinfo/screen-users


Re: multiple screen categories

2010-07-02 Thread Brian Kroth
Wolfgang Hennerbichler wo...@wogri.com 2010-06-29 10:16:
 Hi List, 
 
 I do manage a huge bunch of devices, and I would like to have
 something like a category or group within screen. currenty I run 3
 screen sessions with multiple terminal sessions within each screen -
 one connects to all our routers and switches, one to all our servers
 and one is my development environment. unfortunately the only
 comfortable way to switch between those screens is to use tabs in my
 terminal. I would also like to get rid of those tabs, so is there a
 way to somehow group the terminal sessions to specific screen
 domains and not leave screen but switch to the other group?

What about nested screens?

Also, there was a feature called window-groups in one of the development
releases (I believe it's also been included in the Ubuntu/Debian
packages).  I can't seem to find any docs on it now though other than
the list archives.

Search for the :group command and hopefully you'll find the rest of it.

 thanks for any hints
 wogri
 -- 
 http://www.wogri.com
 
 
 ___
 screen-users mailing list
 screen-users@gnu.org
 http://lists.gnu.org/mailman/listinfo/screen-users


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: Page-up feature in screen

2010-05-14 Thread Brian Kroth
VIGNESH PRABHU stove311...@gmail.com 2010-05-14 09:53:
On Thu, May 13, 2010 at 11:00 PM, Jostein Berntsen
[1]jber...@broadpark.no wrote:
 
  On 12.05.10,20:18, VIGNESH PRABHU wrote:
   Hi friends,
  
   Since I came to know of Screen utility I have been regularly using it
  in my
   desktop and also on servers on which I need to login. I would like to
  know
   how I can browse output of any command which has increased more than
  the
   length of a normal screen(something similar to using shift-up in
  normal
   terminals.).
 
  You can enter the scrollback mode with Ctrl-a-Esc or Ctrl-a-[. There you
  can move around with the usual navigation keys.
 
Great. Just tried it out. This is very useful to me. Thanks.
 
  
   Also one more doubt I have is how I can attach to two screens
  together. For
   example, if I was working on a screen and my friend comes and start
  his own
   screen, next time when I login how can I attach both these screens
  together.
  
   I hope my questions are clear.
 
  I don't think you can merge running screen sessions, but you can list
  active sessions by 'screen -ls', and then start each session with
  'screen -r nameofsession'.

You could also attach each of your relevant sessions under a parent
session (eg: nested screens) which could give a somewhat shoddy illusion
of merging them.

Is this present in the TODO list for the future versions of screen or is
this something very trivial and not necessary?

I have also wondered about that in the past.  I typically make a screen
session for one particular purpose, but later find myself adding windows
to others for straying purposes.  It would be cool to move those around
to reorganize them.  At the very least I know I can rename sessions.

Having lurked on this list for a while now, I can almost hear the devs
now saying, you should use the window group feature to (re)organize
your windows within a single session.  As soon as a new release happens
I'll probably do that.  I haven't yet had time to maintain my own
package for all of the systems I manage to try that out :(

Vignesh, perhaps that, combined with a multiuser screen session with
ACLs is an option for you.

Cheers,
Brian


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: inteface screen

2010-05-13 Thread Brian Kroth
Jostein Berntsen jber...@broadpark.no 2010-05-13 18:49:
 On 12.05.10,08:35, Bruno Lessa wrote:
  Recently i learned how to work with screen program
  
  but in my first utilization, it questioned  me about their interface (dark,
  black and etc..)
  
  I selected dark. And now, I want to change this feature, but can`t find it
  
  Could you help-me?
  
   
 
 Are you sure it was screen that questioned you about this, and not the 
 editor? Screen is configured by settings in ~/.screenrc, and then follow 
 the editor settings regarding background color and more.

Actually, I was thinking that that sounded like an Ubuntu thing.
Perhaps from the screen-profiles package?

Brian


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: turn of control characters in screen

2010-04-21 Thread Brian Kroth
Eric S. Johansson e...@harvee.org 2010-04-19 16:52:
snip/
 A better solution may be dtach. I like it better than screen because I 
 use Emacs and I don't care about multiple screens a single terminal 
 session. The reason I don't use it is because I can't invoke it with the 
 logic use the first unattached session or create a new session.  I want 
 this capability because it would let me stick the head end invocation 
 inside of a login script and solve 90% of my reconnection problems very 
 very simply.

Just to contest the point, that's easily done with screen too.  I source
the attached file from my ~/.bashrc.  It includes some special cases for
local vs. remote vs. cssh sessions, but the idea should be clear enough.

Brian
#!/bin/bash
# ~/.bashrc.d/screen
# 2009-12-21
# bpkroth
#
# Auto launch screen on SSH connections
# Sometimes a pain to deal with SSH screen sessions.
# Can be done with C-a a* though.
# Also a good idea to always use a hardstatus or caption line in .screenrc

if [ $EUID != 0 ]  [[ $TERM != screen* ]]  bin_in_path screen; then
if [ -n $LC_CSSH ]; then
# This special variable was set to denote this
# connection as a member of a CSSH session.  Use the
# value of the variable to select or create a screen
# session with that name.
if screen -list | grep [0-9]\+\.$LC_CSSH[ ]*  /dev/null; then
screen -x $LC_CSSH
else
screen -S $LC_CSSH
fi
elif [ -n $SSH_TTY ]; then
# This is a remote session.
# Connect to the singular screen instance if it is
# available, else list if there are multiple, else
# start a new one.
N=`screen -list | grep -c '[0-9].*tached'`
if [ $N == 1 ]; then
screen -x
elif [ $N == 0 ]; then
#exec screen # no, i want to be able to detach
screen
else
echo
screen -list
fi
#else # local connection, don't open a screen session
#   #exec screen
#   screen
fi
fi


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: turn of control characters in screen

2010-04-21 Thread Brian Kroth
Misha Koshelev misha...@gmail.com 2010-04-19 14:29:
 Dear Sirs or Madams:
 
 I am trying to use GNU screen as a backend for resumable NX sessions.
 
 I was wondering if there exists a solution to turn off _all_ control 
 characters in a screen session?
 
 Thank you
 Misha

BTW, perhaps defutf8 or defc1 can help.

Cheers,
Brian


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: How to keep windows split after detaching/reattaching

2010-03-16 Thread Brian Kroth
I think this may be what you're looking for:
http://lists.gnu.org/archive/html/screen-users/2007-02/msg0.html

Yuki (aka Rubén Gómez) rug...@gmail.com 2010-03-16 09:02:
 I have been looking how to keep my splited windows in screen after
 detaching but all the answers is that I can't do it, but I can fake it
 using nested screen session. Is there another option to get this
 feature?
 
 I have seen that the fork tscreen saves the splited screens :-(
 
 Thanks!
 
 
 ___
 screen-users mailing list
 screen-users@gnu.org
 http://lists.gnu.org/mailman/listinfo/screen-users


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: How to test if screen has a specified window?

2010-02-19 Thread Brian Kroth
Wu, Yue vano...@gmail.com 2010-02-19 23:35:
 On Wed, 17 Feb 2010 05:44:15 +0800, Sadrul Habib Chowdhury  
 ima...@gmail.com wrote:

 * Yue Wu had this to say on [11 Feb 2010, 09:45:12 +0800]:
 Hi list,

 I want do some script with screen, but I don't know how to know if  
 screen has
 a window titled with foo, if has, then do some thing, otherwise, do 
 other
 thing, is it possible in a sh script?

 In the latest git version, you can do something like the following:

  screen -p foo -Q echo 

 If the window 'foo' does not exist, then it will terminate with a
 non-zero status. More at:
 http://lists.gnu.org/archive/html/screen-users/2010-02/msg00031.html

 Thanks, I'm using the latest released version, I'll try when this version 
 is released.

Speaking of which, any thoughts on when a new release might be?

Thanks,
Brian


signature.asc
Description: Digital signature
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: How to set screenname automatically to hostname.

2010-01-25 Thread Brian Kroth
I'm sure I've made this comment before, but this thing is worth looking
at if you're using bash, else zsh natively has the ability to do it.
Basically it allows you to run a command just before every command you
run whereas the PROMPT_COMMAND gets run just before it prints a new
prompt (ie: after you've run the command).

http://www.twistedmatrix.com/users/glyph/preexec.bash.txt
http://glyf.livejournal.com/63106.html?thread=210818

I've used some variant of this for a long time and am quite happy with
it.  With it and some other environment variables in place on the
machines you're using (easier if you've got shared remote home dirs of
some sort) you can have the screen title set to whatever long running
program you last executed on the host in question and include some other
information like what machine you're on as which user and what directory
you're in.

The exact output can be customized, but here's an example window list:

1 @tux-63:~ $ vim foo.txt
2 ~ $ vim bar.txt
3 r...@tux-64:/tmp # 
4 ~ $ ssh somehost

1) Is my user on a different machine running vim of some file.
2) Is my user on the local machine running vim of another file.
3) Is a bash session in /tmp as root on a different machine.
4) Would be an ssh session to some host that doesn't have your
bash.preexec setup on it.  Basically the title stays the same until the
command finishes so it would still be possible to identify the host
you're ssh'd to, though in this case it would only go one level deep
whereas having things setup everywhere means it will always reset your
window title no matter how many machines you ssh through.

As another example here's my current caption line:
1$ ~ $ mutt  2-!$ ~ $ irssi ...

Now if only I could search the window list on the title :)

Cheers,
Brian

halonothing zachary.hat...@gmail.com 2010-01-23 12:39:
 
 
 Jostein Berntsen wrote:
  
  This blog post discusses how to achieve that:
  
  http://platypope.org/blog/2007/3/10/fun-with-screen
  
  - Jostein
  
 
 
 Almost have it working... The only thing i'm noticing is that when I (Ctrl+a
 c) to make a new screen, it seems to be parsing the hostname of the box
 screen is running on, rather than parsing the hostname of the server I ssh
 to shortly after making the screen. Does that make sense?  In other words,
 all of the screen title names are the name of the local hostname.  I want to
 be able to ssh to another server and have it change my screen title to the
 host I've connected to. Any input? 
 
  
 
 p.s. here's the relevant parts of my screenrc, and my PS1 in .bashrc
 
 export PS1='\[\033[s\033k\033\13...@\h\n\[\033[u\]\u \w \$ '
 
 # TERMINAL SETTINGS
 #
 --
 
 # The vt100 description does not mention dl. *sigh*
 termcapinfo vt100 dl=5\E[M
 
 # turn sending of screen messages to hardstatus off
 hardstatus off
 # Set the hardstatus prop on gui terms to set the titlebar/icon title
 termcapinfo xterm*|rxvt*|kterm*|Eterm* hs:ts=\E]0;:fs=\007:ds=\E]0;\007
 # use this for the hard status string
 #hardstatus string %h%? users: %u%?
 shelltitle '@|'
 hardstatus alwayslastline
 hardstatus string '%{= kG}[ %{G}%H %{g}][%= %{= kw}%?%-Lw%?%{r}(%{W}%n*%f
 %t%?(%u)%?%{r})%{w}%?%+Lw%?%?%= %{g}][%{B} %d/%m %{W}%c %{g}]'
 
 # set these terminals up to be 'optimal' instead of vt100
 termcapinfo xterm*|linux*|rxvt*|Eterm* OP
 
 # Change the xterm initialization string from is2=\E[!p\E[?3;4l\E[4l\E
 # (This fixes the Aborted because of window size change konsole symptoms
 found
 #  in bug #134198)
 termcapinfo xterm 'is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;4;6l'
 
 # To get screen to add lines to xterm's scrollback buffer, uncomment the
 # following termcapinfo line which tells xterm to use the normal screen
 buffer
 # (which has scrollback), not the alternate screen buffer.
 #
 #termcapinfo xterm|xterms|xs|rxvt ti@:te@
 
 #
 --
 # STARTUP SCREENS
 #
 --
 
 # Example of automatically running some programs in windows on screen
 startup.
 #
 #   The following will open top in the first window, an ssh session to
 monkey
 #   in the next window, and then open mutt and tail in windows 8 and 9
 #   respectively.
 #
 # caption always %?%F%{-b bc}%:%{-b bb}%?%C|%D|%M %d|%H%?%F%{+u wb}%?
 %L=%-Lw%45%{+b by}%n%f*%t%{-}%+Lw%-0
 # caption always %?%F%{-b kr}%:%{-b rr}%?%C|%D|%M %d|%H%?%F%{+u wk}%?
 %L=%-Lw%45%{+b wr}%n%f*%t%{-}%+Lw%-0
 
 
 -- 
 View this message in context: 
 http://old.nabble.com/How-to-set-screenname-automatically-to-hostname.-tp27026674p27289702.html
 Sent from the Gnu - Screen mailing list archive at Nabble.com.
 
 
 
 ___
 screen-users mailing list
 screen-users@gnu.org
 http://lists.gnu.org/mailman/listinfo/screen-users


signature.asc
Description: Digital signature

Re: use the windows key as the escape key

2009-12-29 Thread Brian Kroth
Erik Falor ewfa...@gmail.com 2009-12-29 11:47:
 On Mon, Dec 28, 2009 at 09:03:50AM -0600, Dustin Kirkland wrote:
  I have been asked this several times and I haven't been able to find
  the answer myself.
  
  Is it possible to use the Windows key (Super_L) (between Ctrl and
  Alt) as the screen escape key?  If so, how do you set this in your
  .screenrc?
 
 I'll take a stab at this.
 
 Assuming you're running Linux, there are two cases to consider:
 

...

 2. Running a virtual terminal from X (such as xterm or rxvt)
 
 I think it is not possible in this case because the terminal never
 sees the keycode Super_L generates.  It is usually intercepted by your
 window manager before being passed to an application.  However, you
 might be able to hack your X keyboard map to re-map Super_L into
 something that would be passed onto your application by your window
 manager.  But, that may also cause Super_L to lose its super meaning
 for any other apps that may wish to use it.

Actually, using urxvt (and possibly xterm) you can have it interpret
various keys (and buttons) as arbitrary escape sequences or keys.  You
might be right that the desktop environment may get in the way.  I'm
personally using fluxbox because I like to have lots of control over my
key bindings, but something like gnome might gobble them up depending
upon how they are mapped (eg: .Xmodmap or other keyboard shortcuts).

Though not entirely related to the original question, here's a set of
info that I just recently cooked up that shows how to bind the mouse
buttons to escape sequences for the purposes of getting mouse scrolling
to work inside various console apps that may or may not support it
directly like less, vim, mutt, irssi, screen, any of these inside
screen, etc.

The principals for binding other keys should be basically the same.

http://homepages.cae.wisc.edu/~bpkroth/src/terminal-mouse-scrolling/README
http://homepages.cae.wisc.edu/~bpkroth/src/terminal-mouse-scrolling.tar.bz2

Cheers,
Brian

...


___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: Ping Packagers

2009-12-11 Thread Brian Kroth
To Dustin/Sadrul:

So long as we're considering some changes, can I petition to have the
default MAXWIN increased from 40 to 99 (or higher)?

We have a screenrc for our ssh bastion host that sets up 40 ssh
sessions by default and we always end up recompiling screen to support
this.

Thanks,
Brian

Sadrul Habib Chowdhury ima...@gmail.com 2009-12-09 14:28:
 * Dustin Kirkland had this to say on [09 Dec 2009, 10:37:17 -0800]:
  On Wed, Dec 9, 2009 at 10:23 AM, Dustin Kirkland kirkl...@canonical.com 
  wrote:
   On Wed, Dec 9, 2009 at 10:19 AM, Sadrul Habib Chowdhury
   ima...@gmail.com wrote:
   Hello everyone. Are there any screen packagers on this list? I am
   contemplating a sort of a beta-release somewhat soon-ish (still
   non-trivial amount of work to do, though, so no ETA yet), and was
   thinking if this list is the best place to reach the packagers.
  
   Hello-
  
   I maintain (along with some others) the screen package in Ubuntu, and
   I do follow this list.
  
   We (Ubuntu) as well as Debian are carrying a stack of patches against
   Screen.  Could we see about getting as many of these as possible into
   your next upstream release?
  
  FYI, you can see the patches we're carrying at:
  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/karmic/screen/karmic/files/head%3A/debian/patches/
 
 Great! Thanks (I was about to request for the link)
 
  The vast majority of these patches predate my involvement and are
  merely inherited from Debian.
  
  The one that I most importantly want to get upstream is the trivial
  33increase_max_winmsg_renditions.dpatch:
  http://bazaar.launchpad.net/%7Eubuntu-branches/ubuntu/karmic/screen/karmic/annotate/head%3A/debian/patches/33increase_max_winmsg_renditions.dpatch
  
  How would you like to proceed?  Should I repost each and every one of
  these individually to the list?  Or can you take a look at each of
  them, and cherry pick the ones that are immediately acceptable, and we
  can debate the rest?
 
 It's not necessary to post them in the Savannah tracker for now. I will
 take a look at the patches (hopefully during this weekend) and let you
 know if I have any questions about any of them. Thanks.
 
  :-Dustin
 
 Cheers,
 Sadrul
 
 
 ___
 screen-users mailing list
 screen-users@gnu.org
 http://lists.gnu.org/mailman/listinfo/screen-users


___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


search for window list?

2009-07-16 Thread Brian Kroth
So I have a machine that I use with screen to SSH to a whole bunch of
other machines.  Often times I have pages and pages of windows in the
window list, each one with the name of the machine I'm SSH'd to
contained in the window title.  Is there a way to search on that list?
Else, feature request?

Thanks,
Brian


___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: Keeping right aligned text in caption always visible

2009-05-31 Thread Brian Kroth
Alex Jurkiewicz a...@bluebottle.net.au 2009-05-30 23:11:
 Hi all,
 
 I'm playing with my screen caption. Currently my caption looks like this:
 caption always %{= Kw} [%0c]%{= Kw} %-Lw%{= KW}[%50%n%f* %t]%{=
 Kw}%+Lw%=| %l | ${FULLHOST}
 
 The output normally looks like this:
  [23:06] 0$ tail:~  1-$ vi:~  [2$* top:~]   |
 0.36 0.60 0.36 | abraxo.bluebottle.net.au
 
 But if there are too many windows open it the right hand info gets truncated:
  [23:07] 0$ tail:~  1$ vi:~  2$ top:~  3$ ~  4$ ~  5$ ~  6$ ~  7-$ ~
 [8$* ~] | 0.20 0.53 0.34 | abraxo.bluebot
 
 How can I tell screen to always keep the full right hand segment on screen?
 
 Thanks,
 Alex Jurkiewicz

I spent a lot of time experimenting with my caption to get something
like that going, though now that I have it (and haven't touched it in a
while) I don't remember exactly what the trick was.  I think I guessed
that the right section would always be about 48 characters and that's
what the %-48= bit is about.

Here's the .screenrc section:

# This adds a statusbar:
# - windows and their flags before the active one are listed in white and 
truncated with ...
# - the active window and it's flags are in bold cyan and aligned slightly to 
the left 
# - the rest of the windows are printed and truncated so that
# - a string describing the current machine, load, and date/time are right 
aligned
caption always %{= .w}%-Lw%20L%{=b .c}%n%f %t%{-}%+Lw %-048= @%H - %l - %D %d 
%M - %c

Here's what it looks like on a small terminal window:

...~ #   2$ ~ $  3$ bpkr...@benji:~ # zl  4$ b... @rolo - 0.00 0.00 0.00 - Sun 
31 May - 17:39

Brian


___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users


Re: window screen title in ssh connection

2009-04-27 Thread Brian Kroth
JuanPablo jabar...@gmail.com 2009-04-25 19:37:
 hi,
   for change the title of my windows screen in the ssh connections add
 in the file ~/.ssh/config
 host remoteHost
 user remoteUser
 port 22
 hostname remoteIp
 ForwardX11 yes
 LocalCommand echo -ne '\ekremoteHost\e\\'
 
 now, the title of window connection is correct, ok
 
 you know  how change the title when the connetion finish ?

I'm assuming you want it to change back automatically when you close the
ssh connection.  There's some documentation in man screen about
dynamic window titles that are based off of your shell prompt.  Search
for TITLES.

If you're using bash, I've also had good luck with this script:
http://www.twistedmatrix.com/users/glyph/preexec.bash.txt

It emulates a feature in zsh called preexec, where you can configure a
command to run just before the shell execs your input.  This is
different from precmd (bash's PROMPT_COMMAND), which only executes just
before the shell prints the prompt (ie: after your input returns).

Then, include this in your .screenrc

# Export a variable denoting the original host screen was started on.
# This is used by the bash.preexec stuff:
# http://glyf.livejournal.com/63106.html?thread=210818
setenv SCREEN_RUN_HOST $SCREEN_HOST
setenv SCREEN_RUN_USER $USER
setenv LC_SCREEN_RUN_HOST $SCREEN_HOST
setenv LC_SCREEN_RUN_USER $USER

The bash.preexec script can make use of these variables to change your
prompt based on the machine you're connected to and where the screen
session is running.  It also depends on SendEnv LC_* in your
.ssh/config and AcceptEnv LC_* in the remote sshd_config.  I think
Debian has that by default.  I've done much more fiddling with the
original to make it display how I like it, but the hard work has been
done for you already.

Brian


___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users