unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Peyton Jones <simonpj@microsoft.com>
To: Eli Zaretskii <eliz@gnu.org>, John Wiegley <jwiegley@gmail.com>
Cc: "24741@debbugs.gnu.org" <24741@debbugs.gnu.org>,
	Simon Peyton Jones <simonpj@microsoft.com>
Subject: bug#24741: 25.1.50; Buffer encoding corrupted up by 'make' in shell-mode
Date: Fri, 21 Oct 2016 21:20:34 +0000	[thread overview]
Message-ID: <DM2PR21MB0028EEBAA18E7965C1433184ADD40@DM2PR21MB0028.namprd21.prod.outlook.com> (raw)
In-Reply-To: <83wph2rymu.fsf@gnu.org>

Thanks everyone.  It's a bizarre bug!  But it's one that does make my life a lot worse, because my compiler's error messages are littered with quotes, each of which turns into 12 characters of encoding, as you can see.

If you want me to try emacs -Q, just let me know how to do that and what info to collect.  I've never done that before.

Customisations. In my .emacs I have the following, which John Wiegley gave to me in the first place

(setq-default locale-coding-system 'utf-8-unix)
(setq-default buffer-file-coding-system 'utf-8-unix)
(set-default-coding-systems 'utf-8-unix)
(set-terminal-coding-system 'utf-8-unix)
(set-keyboard-coding-system 'utf-8-unix)
(set-selection-coding-system 'utf-8-unix)
(prefer-coding-system 'utf-8-unix)

(defun utf8-shell ()
  (interactive)
  (set-default-coding-systems 'utf-8-unix)
  (shell))

(setq w32-get-true-file-attributes nil)

Simon


|  -----Original Message-----
|  From: Eli Zaretskii [mailto:eliz@gnu.org]
|  Sent: 21 October 2016 07:43
|  To: John Wiegley <jwiegley@gmail.com>
|  Cc: Simon Peyton Jones <simonpj@microsoft.com>; 24741@debbugs.gnu.org
|  Subject: Re: bug#24741: 25.1.50; Buffer encoding corrupted up by
|  'make' in shell-mode
|  
|  > From: John Wiegley <jwiegley@gmail.com>
|  > Cc: Simon Peyton Jones <simonpj@microsoft.com>,
|  24741@debbugs.gnu.org
|  > Date: Thu, 20 Oct 2016 12:19:30 -0700
|  >
|  > Eli makes an excellent point: We should try starting Emacs with the
|  -Q
|  > flag next, and attempt a reproduction following the same steps.
|  
|  Actually, posting here the relevant parts of Simon's customizations
|  (the ones that are related to coding-systems and to running shells)
|  might also help identify the probable causes.





  reply	other threads:[~2016-10-21 21:20 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM2PR21MB0028EEBAA18E7965C1433184ADD40@DM2PR21MB0028.namprd21.prod.outlook.com \
    --to=simonpj@microsoft.com \
    --cc=24741@debbugs.gnu.org \
    --cc=eliz@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).