<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 12: Powershell doesn't set the TERM environment variable</title><link href="https://sourceforge.net/p/powershell/bugs/12/" rel="alternate"/><link href="https://sourceforge.net/p/powershell/bugs/12/feed.atom" rel="self"/><id>https://sourceforge.net/p/powershell/bugs/12/</id><updated>2004-04-16T16:20:55Z</updated><subtitle>Recent changes to 12: Powershell doesn't set the TERM environment variable</subtitle><entry><title>Powershell doesn't set the TERM environment variable</title><link href="https://sourceforge.net/p/powershell/bugs/12/" rel="alternate"/><published>2004-04-16T16:20:55Z</published><updated>2004-04-16T16:20:55Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net092d94e9a486221b1ae14d9871d398e1dc6ba014</id><summary type="html">&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;</summary></entry></feed>