From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Cyrillic VC Git commit messages
Date: Fri, 21 Nov 2014 19:48:47 +0300 [thread overview]
Message-ID: <546F6CEF.1090700@gmail.com> (raw)
In-Reply-To: <83y4r4374x.fsf@gnu.org>
> Can you tell how you decided that, or where did you see that described?
That part implies that there is some new functionality in msysgit that
does the recoding for windows cmd.exe.
> And it sends codepage 1252 (not 1251) to the cmd.exe window?
It first decodes the message with logoutputencoding, then recodes it
with windows-1252. If you set logoutputencoding to windows-1251, like I
do, it breaks cmd.exe output.
> Moreover, you seem to say that Git outputs in UTF-8 even though you
> customized i18n.logoutputencoding to be windows-1251?
For vc log the second encoding with windows-1252 does not happen.
For the commit message, git first recodes from windows-1251 to utf-8
and then recodes to commitencoding. This behavior is shared when called
from VC and cmd.exe.
> First, vc-git-commits-coding-system is used only in 2 commands in vc-git
Yeah, but that's exactly the two commands we care about here. It sets
coding-system-for-read for log and coding-system-for-write for commit
message
> modify vc-git.el to use 2 variables
Thought about doing this, but first decided to see if I can get any
help. Those git "hooks" do weird things to say the least.
--
Best Regards,
Nikolay Kudryavtsev
next prev parent reply other threads:[~2014-11-21 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 4:30 Cyrillic VC Git commit messages Nikolay Kudryavtsev
2014-11-21 8:41 ` Eli Zaretskii
2014-11-21 13:21 ` Nikolay Kudryavtsev
2014-11-21 14:06 ` Eli Zaretskii
2014-11-21 14:38 ` Nikolay Kudryavtsev
2014-11-21 15:28 ` Eli Zaretskii
2014-11-21 16:48 ` Nikolay Kudryavtsev [this message]
2014-11-22 13:42 ` Eli Zaretskii
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=546F6CEF.1090700@gmail.com \
--to=nikolay.kudryavtsev@gmail.com \
--cc=help-gnu-emacs@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.