From: Eli Zaretskii <eliz@gnu.org>
To: "Laimonas Vėbra" <laimonas.vebra@gmail.com>
Cc: 6546@debbugs.gnu.org
Subject: bug#6546: win32 grep/shell utf-8 encoding
Date: Thu, 01 Jul 2010 20:26:26 +0300 [thread overview]
Message-ID: <83hbkj9kql.fsf@gnu.org> (raw)
In-Reply-To: <4C2C55ED.3020207@gmail.com>
> Date: Thu, 01 Jul 2010 11:46:37 +0300
> From: Laimonas Vėbra <laimonas.vebra@gmail.com>
> Cc:
>
> Maybe it's actually not the bug (but missing functionality), but how do
> one should/could setup ones emacs && .emacs to grep files in utf-8
> encoding?
>
> grep 2.6.3 (cygwin) at last works correctly (coloring multibyte matches)
> from win32 console (according to LANG environment settings), but no
> matter how i've tried to push emacs (set-language-environment,
> coding-system-for-(read|write), set-env in grep-setup-hook), it just
> don't work, because somewhere inside the Emacs win32 stuff it sticks to
> windows locale codepage and tries hard to convert to this
> codepage/encoding before it passes arguments to shell. No wonder -- it
> fails when it comes to unicode.
Did you try set-process-coding-system?
next prev parent reply other threads:[~2010-07-01 17:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 8:46 bug#6546: win32 grep/shell utf-8 encoding Laimonas Vėbra
2010-07-01 17:26 ` Eli Zaretskii [this message]
2010-07-01 18:05 ` Laimonas Vėbra
2010-07-22 12:50 ` Juanma Barranquero
2010-07-22 14:11 ` Laimonas Vėbra
2010-07-22 15:02 ` Juanma Barranquero
2010-07-22 18:24 ` Laimonas Vėbra
2010-07-22 19:53 ` Eli Zaretskii
2010-07-22 21:48 ` Laimonas Vėbra
2010-07-22 23:00 ` Juanma Barranquero
2010-07-23 10:24 ` Eli Zaretskii
2010-07-23 12:54 ` Laimonas Vėbra
2010-07-23 14:23 ` Eli Zaretskii
2010-07-23 15:50 ` Laimonas Vėbra
2010-07-23 18:09 ` Eli Zaretskii
2010-07-23 19:07 ` Laimonas Vėbra
2022-04-24 12:01 ` bug#6546: bug#6705: w32 cmdproxy.c pass args to cygwin; erroneous charset conversion (problem description, solution/suggestion) Lars Ingebrigtsen
2022-04-24 12:31 ` Eli Zaretskii
2022-04-24 13:25 ` Lars Ingebrigtsen
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=83hbkj9kql.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6546@debbugs.gnu.org \
--cc=laimonas.vebra@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).