All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Giulio Cesare Solaroli <giulio.cesare@solaroli.it>, git@vger.kernel.org
Subject: Re: Issue with 'git diff' and non ascii characters
Date: Fri, 12 Sep 2014 21:34:52 +0200	[thread overview]
Message-ID: <54134ADC.6000504@web.de> (raw)
In-Reply-To: <5DEE05EE-B302-44D1-9B1D-0B475EF4E96B@solaroli.it>

On 2014-09-12 08.53, Giulio Cesare Solaroli wrote:
> Hello,
> 
> I have spotted a problem using 'git diff' when non ascii characters are involved.
> Not sure if the problem is due to the name of the file, or its content.
> 
> Cheers,
> 
> Giulio Cesare
> 
> Steps to reproduce the problem:
> 
> $ sw_vers
> ProductName:	Mac OS X
> ProductVersion:	10.9.4
> BuildVersion:	13E28
> $ git --version
> git version 1.8.5.2 (Apple Git-48)
> $ mkdir test
> $ cd test
> $ echo prova > tèst.md
> $ git init
> Initialized empty Git repository in /private/tmp/test/.git/
> $ git add *
> $ git commit -m "first commit"
> [master (root-commit) ebbe2a3] first commit
>  1 file changed, 1 insertion(+)
>  create mode 100644 "t\303\250st.md"
> $ echo provà > tèst.md 
> $ git status
> On branch master
> Changes not staged for commit:
>   (use "git add <file>..." to update what will be committed)
>   (use "git checkout -- <file>..." to discard changes in working directory)
> 
> 	modified:   "t\303\250st.md"
> 
> no changes added to commit (use "git add" and/or "git commit -a")
> $ git diff tèst.md 
> $ 
The problem is not the contents of the file, but the file name.

The following should help:

git config core.quotepath false

      reply	other threads:[~2014-09-12 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12  6:53 Issue with 'git diff' and non ascii characters Giulio Cesare Solaroli
2014-09-12 19:34 ` Torsten Bögershausen [this message]

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=54134ADC.6000504@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=giulio.cesare@solaroli.it \
    /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.
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.