unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 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: Fri, 08 Apr 2016 11:23:43 +0300	[thread overview]
Message-ID: <83mvp4jypc.fsf@gnu.org> (raw)
In-Reply-To: <83pou5o0uh.fsf@gnu.org> (message from Eli Zaretskii on Mon, 04 Apr 2016 18:22:30 +0300)

> Date: Mon, 04 Apr 2016 18:22:30 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 23076@debbugs.gnu.org
> 
> So instead, I can suggest one of the following alternatives, to be
> done only when invoking Git to commit on MS-Windows:
> 
>  1) ignore vc-git-commits-coding-system and always encode the
>     command-line arguments using the system locale (in your case,
>     codepage 1251); or
> 
>  2) put the log message in a temporary file, encoded in
>     vc-git-commits-coding-system, then use -F instead of -m; the rest
>     of command-line arguments will be encoded in the system locale's
>     codepage
> 
> The 1st solution is essentially what you wanted, but without the need
> to introduce an additional variable or ask the users to configure it.
> 
> The 2nd solution is somewhat slower, but it is better, because it will
> allow to write log messages using any characters, not just those
> representable in the current codepage.  Note that it still doesn't
> solve all the problems with non-ASCII characters, because those could
> be in the "author" or any of the other arguments with which we call
> Git, such as the names of the files whose changes are to be committed
> (as Emacs does support arbitrary characters in file names).
> 
> Comments?

Ping!





  reply	other threads:[~2016-04-08  8:23 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 [this message]
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

  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=83mvp4jypc.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).