Hello Martin
> As i am someone who's regularily working remotely on several machines,
> connecting from a local screen session via ssh to those remote
> maschines. Not all of those offer me the possibilty to run another
> screen there. It'd be really helpful for me i could put an
> identification
Hello Martin,
Martin Hauser wrote:
[...]
> > Or even better:
> > Use
> >ssh [EMAIL PROTECTED] -all -other -options
> > and
> > function ssh() {
> >echo -n -e "\033k$1\033\\"
> >/usr/bin/ssh "$@"
Of course, changing that line to
command ssh "$@"
also works when ssh is elsewhere in
Hello Thomas,
[...]
> Just set the current window's title to "remotehost"?
>
> ctrl-a A
>
the thing was that i didn't want to do it by hand, but thanks anyway.
> Or even better:
> Use
>ssh [EMAIL PROTECTED] -all -other -options
> and
> function ssh() {
>echo -n -e "\033k$1\033\\"
>
Hi Martin,
Martin Hauser wrote:
> Good day,
>
> As i am someone who's regularily working remotely on several machines,
> connecting from a local screen session via ssh to those remote
> maschines. Not all of those offer me the possibilty to run another
> screen there. It'd be really helpful for m
Good day,
As i am someone who's regularily working remotely on several machines,
connecting from a local screen session via ssh to those remote
maschines. Not all of those offer me the possibilty to run another
screen there. It'd be really helpful for me i could put an
identification into the loca
