From: Eli Zaretskii <eliz@gnu.org>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: 23076@debbugs.gnu.org
Subject: bug#23076: 24.5; vc-git: add a new variable for log output coding system
Date: Sat, 09 Apr 2016 17:48:13 +0300 [thread overview]
Message-ID: <83bn5ij0sy.fsf@gnu.org> (raw)
In-Reply-To: <57090E2F.4020702@gmail.com> (message from Nikolay Kudryavtsev on Sat, 9 Apr 2016 17:14:07 +0300)
> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Cc: 23076@debbugs.gnu.org
> Date: Sat, 9 Apr 2016 17:14:07 +0300
>
> > How can it break someone's setup, if using the current system codepage
> > is the_only_ way of invoking programs from Emacs on MS-Windows?
> Download this:
> https://github.com/msysgit/msysgit/releases/download/Git-1.7.9-preview20120201/PortableGit-1.7.9-preview20120201.7z
> Then, from emacs -Q:
> (setq vc-git-program "d:/Downloads/PortableGit/bin/git.exe")
> Note that the git is used from bin, and not from cmd. Russian commits do
> work with this version, when vc-git-commits-coding system is utf-8.
This cannot work except by accident, and/or for only some specific
characters. Windows attempts to translate non-ASCII characters passed
to programs to the current codepage, so a byte that is not possible in
the codepage will be mangled. For example, try a log message that
uses a UTF-8 string which has a 0x98 byte in it -- the only byte that
is not a valid cp1251 character -- you will see it mangled on the Git
side.
> So we can define breaking someone's setup - if that someone uses this
> old git version, forcing windows-1251 would break his setup.
> 1.7.9 is the last working version.
Even if I'm wrong about this, v1.7.9 is too old to care about. It's
too easy to upgrade.
> In the end, of course I like solution #2.
Thanks, I will work on implementing it.
next prev parent reply other threads:[~2016-04-09 14:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 11:51 bug#23076: 24.5; vc-git: add a new variable for log output coding system Nikolay Kudryavtsev
2016-03-21 19:01 ` Nikolay Kudryavtsev
2016-04-02 10:16 ` Eli Zaretskii
2016-04-03 20:34 ` Nikolay Kudryavtsev
2016-04-04 15:22 ` Eli Zaretskii
2016-04-08 8:23 ` Eli Zaretskii
2016-04-09 12:30 ` Nikolay Kudryavtsev
2016-04-09 12:50 ` Eli Zaretskii
2016-04-09 14:14 ` Nikolay Kudryavtsev
2016-04-09 14:48 ` Eli Zaretskii [this message]
2016-04-10 16:10 ` Eli Zaretskii
2016-04-11 22:12 ` Nikolay Kudryavtsev
2016-04-12 15:07 ` Nikolay Kudryavtsev
2016-04-12 15:22 ` Eli Zaretskii
[not found] <acdfa136-1d37-a920-b572-fdd0f6e11257@gmail.com>
[not found] ` <837fch1vmw.fsf@gnu.org>
2016-07-25 18:46 ` Nikolay Kudryavtsev
2016-07-25 19:10 ` Eli Zaretskii
2016-07-26 19:01 ` Michael Albinus
2016-07-27 2:36 ` Eli Zaretskii
2016-08-07 12:08 ` Michael Albinus
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=83bn5ij0sy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23076@debbugs.gnu.org \
--cc=nikolay.kudryavtsev@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).