Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!hplabs!hplabsc!mayer
From: mayer@hplabsc.UUCP
Newsgroups: comp.emacs
Subject: Re: X and gnu emacs problem
Message-ID: <1462@hplabsc.UUCP>
Date: Fri, 20-Mar-87 13:07:53 EST
Article-I.D.: hplabsc.1462
Posted: Fri Mar 20 13:07:53 1987
Date-Received: Sun, 22-Mar-87 17:17:48 EST
References: <349@bacchus.MIT.EDU>
Reply-To: mayer@hplabsc.UUCP (Niels Mayer)
Organization: Hewlett-Packard Labs, Palo Alto, CA
Lines: 17
Summary: yeah, but....

In article <349@bacchus.MIT.EDU> rlk@athena.MIT.EDU writes:
> [... a bunch of stuff about "setenv TERM xterm" ...]
> V18 does do the right thing however.

Except that it doesn't set the environment $TERM based on the size of
the initial startup screen.  So  if your  login console  $TERM is set
for some 132 column screen, subprograms  run by  gnuemacs will format
their outputs for 132 column displays...  A  good example  of this is
the mh scan program for  mhe:   the mail  folder browser  will end up
presenting wrapped 132 column lines if you start gnuemacs as an 80x24
X window.

Perhaps  gnuemacs  should  explicitly set  TERM to  the correct width
before  executing  programs  in  subshells?   MHE should probably set
the screenwidth in $TERM before calling scan.

		-- Niels.