<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 12: Powershell doesn't set the TERM environment variable</title><link>https://sourceforge.net/p/powershell/bugs/12/</link><description>Recent changes to 12: Powershell doesn't set the TERM environment variable</description><atom:link href="https://sourceforge.net/p/powershell/bugs/12/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 16 Apr 2004 16:20:55 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/powershell/bugs/12/feed.rss" rel="self" type="application/rss+xml"/><item><title>Powershell doesn't set the TERM environment variable</title><link>https://sourceforge.net/p/powershell/bugs/12/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Powershell doesn't set the TERM environment variable&lt;br /&gt;
when starting a shell. This means that many programs&lt;br /&gt;
including man, emacs and mutt don't work correctly. To&lt;br /&gt;
solve the problem, you might set the TERM environment&lt;br /&gt;
variable to xterm before starting a shell. When I do&lt;br /&gt;
this manually, everything works fine.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 16 Apr 2004 16:20:55 -0000</pubDate><guid>https://sourceforge.net092d94e9a486221b1ae14d9871d398e1dc6ba014</guid></item></channel></rss>