Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?
- From: Ed Schouten <ed@xxxxxxxx>
- Date: Fri, 21 Oct 2011 08:59:12 +0200
Hi Garrett,
* Garrett Cooper <yanegomi@xxxxxxxxx>, 20111021 08:40:
If I fire up an xterm without setting TERM={ansi,vt100,xterm},
[...]
So what's the idea behind this? Why not just set TERM properly?
--
Ed Schouten <ed@xxxxxxxx>
WWW: http://80386.nl/
Attachment:
pgp7VX2rVVkuN.pgp
Description: PGP signature
- Follow-Ups:
- References:
- Prev by Date: Re: sys/conf/newvers.sh vs. subversion-1.7
- Next by Date: Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?
- Previous by thread: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?
- Next by thread: Re: Not setting TERM explicitly wraps commands at 80 columns with nested shells in xterms using sh + bash?
- Index(es):
