From: Simon Peyton Jones <simonpj@microsoft.com>
To: jwiegley@gmail.com, 24741@debbugs.gnu.org
Subject: bug#24741: 25.1.50; Buffer encoding corrupted up by 'make' in shell-mode
Date: Wed, 19 Oct 2016 19:07:44 +0000 [thread overview]
Message-ID: <BN6PR21MB064442C435310DAF24CF510BADD20@BN6PR21MB0644.namprd21.prod.outlook.com> (raw)
In-Reply-To: <m2shrsnt1n.fsf@newartisans.com>
Thanks John.
It's emacs 24.5.1 (686-pc-mingw32)
It's not 'make' per se; for example 'make --version' or 'make boot' (which does nothing) is fine. The invocation of make that causes the funny quotes to appear invokes Python, if that helps.
Deeply mysterious.
If I start a new shell, I get quotes looking nice again. Could something in the shell environment be affected by invoking python?
Simon
| -----Original Message-----
| From: John Wiegley [mailto:jwiegley@gmail.com]
| Sent: 19 October 2016 18:33
| To: bug-gnu-emacs@gnu.org
| Cc: Simon Peyton Jones <simonpj@microsoft.com>
| Subject: 25.1.50; Buffer encoding corrupted up by 'make' in shell-mode
|
| I have a friend who is using Emacs 24.5 on Windows, and who is
| experiencing a strange behavior: Unicode quotes display properly, but
| after *invoking* a 'make' command -- even with its output fully
| redirected to a file -- buffer decoding begins to fail, causing later
| quotes to be display as escape codes.
|
| I'm attaching a screenshot from his machine, to show the behavior:
next prev parent reply other threads:[~2016-10-19 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 17:32 bug#24741: 25.1.50; Buffer encoding corrupted up by 'make' in shell-mode John Wiegley
2016-10-19 19:07 ` Simon Peyton Jones [this message]
2016-10-20 7:14 ` Eli Zaretskii
2016-10-20 19:19 ` John Wiegley
2016-10-21 6:42 ` Eli Zaretskii
2016-10-21 21:20 ` Simon Peyton Jones
2016-10-22 7:17 ` Eli Zaretskii
2016-12-07 20:29 ` Glenn Morris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BN6PR21MB064442C435310DAF24CF510BADD20@BN6PR21MB0644.namprd21.prod.outlook.com \
--to=simonpj@microsoft.com \
--cc=24741@debbugs.gnu.org \
--cc=jwiegley@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.