From: Glenn Morris <rgm@gnu.org>
To: 24741-done@debbugs.gnu.org
Subject: bug#24741: 25.1.50; Buffer encoding corrupted up by 'make' in shell-mode
Date: Wed, 07 Dec 2016 15:29:42 -0500 [thread overview]
Message-ID: <bp37hzfpop.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83oa2crgwz.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 Oct 2016 10:17:48 +0300")
Eli Zaretskii wrote:
> Start Emacs with "emacs -Q", then try reproducing the problem by doing
> whatever you do when the problem normally happens.
>
> If "emacs -Q" lacks some optional features and custom settings of
> certain variables, load those features and customize those variables
> as part of the recipe (i.e. record everything you need to do starting
> from "emacs -Q" until you are able to run the commands that produce
> the problematic output).
>
> Then post here the full recipe for reproducing the problem, including
> everything you have recorded on the way.
[...]
> This is already dead wrong on Windows, especially setting the default
> encodings to UTF-8. It cannot possibly work well on Windows. And you
> shouldn't need this.
>
> What happens if you remove these and try again -- does the problem
> still appear?
>
> Where did you get your Bash, your make.exe, and your Python? If they
> are from the MSYS2 project, the only customization of coding-systems
> you may need is of process-coding-system-alist. If you do that, make
> sure the encoding is still your system codepage, and only the decoding
> part is UTF-8. That's because the encoding is used to encode the
> command-line arguments, and you certainly don't want them to be
> encoded in UTF-8 on Windows, because this is unsupported.
No further reponse, closing.
Possibly a bit soon, so feel free to reopen.
prev parent reply other threads:[~2016-12-07 20:29 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
2016-10-22 7:17 ` Eli Zaretskii
2016-12-07 20:29 ` Glenn Morris [this message]
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=bp37hzfpop.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=24741-done@debbugs.gnu.org \
/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.