[newbie] Re: Powershell and $TERM

2005-01-28 Thread J. David Boyd
Miark [EMAIL PROTECTED] writes: When I try to run MicroEMACS in Powershell, I get Environment variable TERM not defined! So if I TERM=vt100 and then export TERM all is well. Unless I close and open it again, that is. How do I make this change permanent without affecting other working

Re: [newbie] Re: Powershell and $TERM

2005-01-28 Thread Miark
On 28 Jan 2005 12:23:38 -0500, J. wrote: Miark [EMAIL PROTECTED] writes: When I try to run MicroEMACS in Powershell, I get Environment variable TERM not defined! So if I TERM=vt100 and then export TERM all is well. Unless I close and open it again, that is. How do I make this

Re: [newbie] Re: Powershell and $TERM

2005-01-28 Thread Mikkel L. Ellertson
Miark wrote: On 28 Jan 2005 12:23:38 -0500, J. wrote: Miark [EMAIL PROTECTED] writes: When I try to run MicroEMACS in Powershell, I get Environment variable TERM not defined! So if I TERM=vt100 and then export TERM all is well. Unless I close and open it again, that is. How do I make this

Re: [newbie] Re: Powershell and $TERM -- SUCCESS!

2005-01-28 Thread Miark
On Fri, 28 Jan 2005 17:17:57 -0600, Mikkel wrote: Miark wrote: Does Powershell set TERM to any value? If it sets it to a terminal type that isn't defined, there is hope... If TERM isn't defined, you may be able to add something to .bashrc - something like (untested) if [ ! $TERM ] ;

Re: [newbie] Re: Powershell and $TERM -- SPOKE TOO SOON

2005-01-28 Thread Miark
On Fri, 28 Jan 2005 21:25:14 -0500, Miark wrote: On Fri, 28 Jan 2005 17:17:57 -0600, Mikkel wrote: Miark wrote: Does Powershell set TERM to any value? If it sets it to a terminal type that isn't defined, there is hope... If TERM isn't defined, you may be able to add something to

Re: [newbie] Re: Powershell and $TERM -- SPOKE TOO SOON

2005-01-28 Thread Charles A Edwards
On Fri, 28 Jan 2005 21:29:44 -0500 Miark wrote: When I opened powershell from the XFCE launch bar directly, Try using this as the command in the Xfce entry powershell TERM=vt100 export TERM Charles -- : - cut in regexps I don't think we reached consensus on that. We're still

Re: [newbie] Re: Powershell and $TERM -- SPOKE TOO SOON

2005-01-28 Thread Miark
On Fri, 28 Jan 2005 22:23:46 -0500, Charles wrote: When I opened powershell from the XFCE launch bar directly, Try using this as the command in the Xfce entry powershell TERM=vt100 export TERM Promising, but no. :-/ Miark Want to

Re: [newbie] Re: Powershell and $TERM -- SPOKE TOO SOON

2005-01-28 Thread Mikkel L. Ellertson
Miark wrote: On Fri, 28 Jan 2005 21:25:14 -0500, Miark wrote: On Fri, 28 Jan 2005 17:17:57 -0600, Mikkel wrote: Miark wrote: Does Powershell set TERM to any value? If it sets it to a terminal type that isn't defined, there is hope... If TERM isn't defined, you may be able to add something to

Re: [newbie] Re: Powershell and $TERM -- REALLY SOLVED!

2005-01-28 Thread Miark
Well, that is easy to fix. Change it to: if [ $TERM = dumb ] ; then export TERM=xterm ; fi _THAT_ did it!! Hurray! One thing to keep in mind - if Powerterm is setting TERM to dumb, then it probably does not support some of the terminal functions of xterm. So some programs may not work

Re: [newbie] Re: Powershell and $TERM -- SPOKE TOO SOON

2005-01-28 Thread Mikkel L. Ellertson
Mikkel L. Ellertson wrote: Miark wrote: On Fri, 28 Jan 2005 21:25:14 -0500, Miark wrote: On Fri, 28 Jan 2005 17:17:57 -0600, Mikkel wrote: Miark wrote: Does Powershell set TERM to any value? If it sets it to a terminal type that isn't defined, there is hope... If TERM isn't defined, you may be