Fun with screen / commentary

Comment on "Fun with screen"

2007-06-04T22:06:07-04:00

I'm not sure I follow enough of the .screenrc wackery to know what of this you have or may have interest in, but somewhere along the way I picked up a great line:

#change the     hardstatus settings to give an window list at the bottom of the
#screen, with the server name, time and date and with the current window highlighted
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}]'

Comment on "Fun with screen"

2007-06-04T22:08:08-04:00

Hm, maybe I should've read the markdown link before posting code.

The huge text is that which was commented out; I'm super savvy.

Comment on "Fun with screen"

2007-06-05T11:43:15-04:00

I really need to add comment preview one of these days... Fixed, with the horrifically long line indicating that I also need to work on my CSS stylesheet. Oh, and nice to see you, Marilyn. :-)

Comment on "Fun with screen"

2007-10-09T00:43:54-04:00

I was looking for this trick to add hostname to the screen name - thanks a lot.

Comment on "Fun with screen"

2007-10-18T15:49:23-04:00

Thanks for this great tip.

Have you noticed that your command begins overwriting the prompt and not go to the next line if you type off the right edge of the screen after setting this up?

Any idea how to get around it?

Comment on "Fun with screen"

2007-10-18T19:12:35-04:00

@Seth -- Actually, a buddy of mine noticed that when he tried to set this up too. We eventually figured out that I wasn't seeing it because my prompt is multi-line, like:

[llasram@seneca]=[i686-pc-linux-gnu]
[Thu Oct 18 19:09:49]=[ls]
[3]=[~/.rcfiles/basic/bashrc.d]
$

If this is just too hardcore for you :-), my friend managed to sort it out by futzing with his TERM settings, although I'll need to ping him again to retrieve the details.

Comment on "Fun with screen"

2007-10-18T22:01:04-04:00

Heh...that is quite the EXTREME(tm) prompt.

I should probably move to a multi-line prompt. I've been hanging around in some buried directories too much lately.

But if it's not too much a problem, I'd love to see how it's fixed via TERM settings. Otherwise, I can dig around on my own.

BTW, nice emacs/rails screencast. I'm sure you hear that a lot.

Comment on "Fun with screen"

2007-10-19T10:23:12-04:00

@Seth -- Actually, my memory was totally off. The solution is to wrap the non-printing parts of the prompt in the \[ and \] sequences which inform bash that part of the prompt contains non-printing characters. E.g.:

PS1='\[\033[s\033k\033\134\]@\h\n\[\033[u\]\u \w \$ '

Depending on the length of your hostnames, you might want to try sticking the 'clear current line' terminal escape sequence in there too.

Hope that helps, and thanks about the screencast!

Comment on "Fun with screen"

2007-10-19T11:18:10-04:00

Of course, it also helps if I include an example based on the technique I described instead of the save/restore cursor position escape sequences:

PS1='\[\033k\033\134\]@\h\n\[\033[1A\]\u \w \$ '

Lots of options.