From: Jason Rumney <jasonr@gnu.org>
To: "Laimonas Vėbra" <laimonas.vebra@gmail.com>
Cc: 6705@debbugs.gnu.org
Subject: bug#6705: w32 cmdproxy.c pass args to cygwin; erroneous charset conversion (problem description, solution/suggestion)
Date: Thu, 22 Jul 2010 22:33:21 +0800 [thread overview]
Message-ID: <87bp9zzivi.fsf@home.jasonrumney.net> (raw)
In-Reply-To: <4C483A30.9010804@gmail.com> ("Laimonas Vėbra"'s message of "Thu, 22 Jul 2010 15:31:44 +0300")
Laimonas Vėbra <laimonas.vebra@gmail.com> writes:
> This problem certainly needs some discussion (how best to solve it) because it addresses unicode communication aspects/issues. If some won't bother reading all the description, then here is a simple question --
> how do one can/should (clearly) pass utf-8 arguments to an external
> (cygwin) app on windows? I suppose, now it's not possible.
Don't use cmdproxy with Cygwin programs. If you need a shell in between,
use Cygwin bash. cmdproxy is a wrapper to get around some problems with
various versions of the Windows native cmd.exe and command.com shell
programs. Mixing Cygwin and native Windows is not advised.
next prev parent reply other threads:[~2010-07-22 14:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 12:31 bug#6705: w32 cmdproxy.c pass args to cygwin; erroneous charset conversion (problem description, solution/suggestion) Laimonas Vėbra
2010-07-22 14:33 ` Jason Rumney [this message]
2010-07-22 18:14 ` bug#6546: " Laimonas Vėbra
2010-07-22 19:50 ` Eli Zaretskii
2010-07-22 20:59 ` Laimonas Vėbra
2010-07-23 10:21 ` Eli Zaretskii
2010-07-23 12:57 ` Laimonas Vėbra
2010-07-23 14:35 ` Eli Zaretskii
2010-07-23 15:35 ` Laimonas Vėbra
2010-07-23 18:06 ` Eli Zaretskii
2010-07-23 18:53 ` Laimonas Vėbra
2010-07-23 21:25 ` Eli Zaretskii
2010-07-23 21:53 ` Laimonas Vėbra
2010-07-24 20:33 ` Eli Zaretskii
2010-07-25 10:10 ` Laimonas Vėbra
2010-07-23 19:07 ` Juanma Barranquero
2010-07-23 19:51 ` Laimonas Vėbra
2010-07-23 19:59 ` Juanma Barranquero
2010-07-22 22:56 ` Juanma Barranquero
2010-07-23 10:26 ` Eli Zaretskii
2010-07-23 10:45 ` Juanma Barranquero
2010-07-23 14:16 ` Eli Zaretskii
2010-07-25 23:38 ` Stefan Monnier
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=87bp9zzivi.fsf@home.jasonrumney.net \
--to=jasonr@gnu.org \
--cc=6705@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).