Received: by 10.66.79.233 with SMTP id m9mr1229507pax.37.1349329301428; Wed, 03 Oct 2012 22:41:41 -0700 (PDT) Path: g9ni21211pbh.1!nntp.google.com!news.glorb.com!usenet.stanford.edu!not-for-mail From: =?ISO-8859-15?Q?Andreas_R=F6hler?= Newsgroups: gnu.emacs.help Subject: Re: problems displaying utf-8-characters after reload Date: Thu, 04 Oct 2012 07:41:34 +0200 Lines: 18 Approved: help-gnu-em...@gnu.org Message-ID: References: <07623f85-1f66-41c3-b729-9fec83597fa1@googlegroups.com> <83k3v89pvk.fsf@gnu.org> <506BE4C4.6020004@easy-emacs.de> <83bogja2sa.fsf@gnu.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 X-Trace: usenet.stanford.edu 1349329301 20542 208.118.235.17 (4 Oct 2012 05:41:41 GMT) X-Complaints-To: action@cs.stanford.edu To: help-gnu-em...@gnu.org Envelope-to: help-gnu-em...@gnu.org User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120825 Thunderbird/15.0 In-Reply-To: <83bogja2sa.fsf@gnu.org> X-Provags-ID: V02:K0:j9yIy3LgcXgBac+lRTGP+wV2yNJ7gsM5rL7MMK5FUKG lKfgQIasjM3WdBk+mCfIkPNLxnOBAOQiYp10QHTARo7r8PNGiE RsMxqwjwp5Thgsf0cFhK1dn/pJ+uSLkAljmkLaQ4YpEtXW1c2c 1zHgzwwjmyQsDXNOva/IsM74OeTAM3PcOjkATolrj0gYRH365f KYWOAMs+Ku/BZdSijzMm5qZbyGA6Ir4RQtm3Arnu7yPHLNbhb4 xTCeHSJxvM6zU35+FBDS+Bbzx2M0YPkDnW566dVqPdmGeAe6+n MzrEeq3Ffvr2Uz3vfRIGyD7GS+A4u6J3dP7M7OleVE7NSJbBca b4EoCI9hFJjFBO7IgJ10A+b1Yv1fyX1jxQ/yAendg X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 212.227.17.8 X-BeenThere: help-gnu-em...@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Am 03.10.2012 19:22, schrieb Eli Zaretskii: >> Date: Wed, 03 Oct 2012 09:09:56 +0200 >> From: Andreas Röhler >> >> a related bug seems visible with emacs -Q Python-shell - png attached. > > I'm quite sure it's because Python-shell, whatever that is, sets up an > incorrect coding-systems for decoding output from Python. > > > my mistake: this form needs a Python3, while reported when Python2 was used. Sorry, Andreas