-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, Sep 3, 2008 at 8:42 PM, Aaron Davies wrote: >> If you have your COLUMNS and LINES environment variables populated, >> screen honors them. >> >> I tried this in my .tcshrc file (which would be much much simpler to >> express in your .bashrc file) and it seems to solve that annoyance >> just fine. > > hmm. before i can see if that works for me, i think i need to solve a > possibly related problem: my LINES and COLUMNS vars don't even make it > into screen. i have `eval resize` near the end of my .bash_profile, > which sets and exports them, so they should show up in any subprocess, > right? i don't have any shell setting in my .screenrc, so screen > should run non-login instances of my regular shell, i.e. bash w/the > .bashrc executed, but not the .bash_profile. nonetheless, after login > but before starting screen, i find that LINES and COLUMNS are set; > after starting screen and checking from inside, i find that they're > not. why are they not getting passed down? Sorry, this important tidbit slipped my mind. It's not screen that honors COLUMNS and LINES, it's the shell itself. So you need to make sure the snippet of code that determines LINES and COLUMNS is in your shell's rc file on the remote host as well. I tested it to make sure and doing it this way works fine for me. I didn't test bash, just tcsh (including a very very old tcsh version 6.11.0 on one of my boxes) and the annoyance vanishes. - -- Andy Harrison public key: 0x67518262 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: http://getfiregpg.org iD8DBQFIv+b5NTm8fWdRgmIRAuwSAKCobDjk8ShqsifVSwd2aSd87AvA5gCfZkFA zMIeJn4J5P/L7h8y7eT2bPg= =L1b+ -----END PGP SIGNATURE----- _______________________________________________ screen-users mailing list screen-users@gnu.org http://lists.gnu.org/mailman/listinfo/screen-users
