From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: 23076@debbugs.gnu.org
Subject: bug#23076: 24.5; vc-git: add a new variable for log output coding system
Date: Mon, 21 Mar 2016 22:01:59 +0300 [thread overview]
Message-ID: <56F04527.6010901@gmail.com> (raw)
In-Reply-To: <56EFE033.7080900@gmail.com>
Since I did this for the other one, here are more detailed steps on how
to repeat this:
1. (setq vc-git-commits-coding-system 'windows-1251)
2. Clone https://github.com/sg2002/vc-git-bugs
3. Run vc-log on it. This would give you broken output.
4. Evaluate the whole fix.el file from the repo.
5. Run vc-log again. Now you would get the proper "Русскоязычный
коммит." in it.
Adding a new variable is the only way to setup git with Russian commit
logs on Windows, while fulfilling all three of the following requirements:
1. Committing from Emacs in Russian should work.
2. vc-log should work in Emacs.
3. git log should work outside of Emacs.
The same should be true for other non-latin alphabets.
--
Best Regards,
Nikolay Kudryavtsev
next prev parent reply other threads:[~2016-03-21 19:01 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56F04527.6010901@gmail.com \
--to=nikolay.kudryavtsev@gmail.com \
--cc=23076@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.