git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: Thomas Singer <thomas.singer@syntevo.com>
Cc: git@vger.kernel.org
Subject: Re: OS X and umlauts in file names
Date: Thu, 26 Nov 2009 12:23:19 -0500	[thread overview]
Message-ID: <76718490911260923l1d22012cyf62904d14cde4198@mail.gmail.com> (raw)
In-Reply-To: <4B0ABA42.1060103@syntevo.com>

On Mon, Nov 23, 2009 at 11:37 AM, Thomas Singer
<thomas.singer@syntevo.com> wrote:
> I'm on an English OS X 10.6.2 and I created a sample file with umlauts in
> its name (Überlänge.txt). When I try to stage the file in the terminal, I
> can't complete the file name by typing the Ü and hitting the tab key, but I
> can complete it by typing an U and hitting the tab key. Unfortunately, after
> executing
>
>  git stage Überlänge.txt
>
> I invoked
>
>  git status
>
> and it still shows the file as new file. Should I set some environment
> variable to be able to work with files containing umlauts in the name?

Works for me on 10.6.2:

kore:~/foo (master)$ echo Überlänge.txt > Überlänge.txt
kore:~/foo (master)$ git stage Überlänge.txt
kore:~/foo (master)$ git st
# On branch master
#
# Initial commit
#
# Changes to be committed:
#   (use "git rm --cached <file>..." to unstage)
#
#	new file:   "U\314\210berla\314\210nge.txt"
#
kore:~/foo (master)$ git commit -m initial
[master (root-commit) f23e23f] initial
 1 files changed, 1 insertions(+), 0 deletions(-)
 create mode 100644 "U\314\210berla\314\210nge.txt"
kore:~/foo (master)$ git st
# On branch master
nothing to commit (working directory clean)

Doesn't matter whether LANG and/or LC_* are set or not for me.

j.

      parent reply	other threads:[~2009-11-26 17:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23 16:37 OS X and umlauts in file names Thomas Singer
2009-11-23 17:45 ` Thomas Rast
2009-11-23 18:10   ` Thomas Singer
2009-11-23 18:23     ` Johannes Schindelin
2009-11-23 20:31       ` Thomas Singer
2009-11-23 23:31       ` Jakub Narebski
2009-11-23 18:29     ` Martin Langhoff
2009-11-23 20:26 ` Daniel Barkalow
2009-11-25  8:50   ` Thomas Singer
2009-11-25  9:51     ` B Smith-Mannschott
2009-11-25 10:07     ` Martin Langhoff
2009-11-25 10:19       ` Martin Langhoff
2009-11-25 22:43     ` Andreas Schwab
2009-11-26  8:28       ` Thomas Singer
2009-11-26 17:27     ` Jay Soffian
2009-11-27 10:01       ` Thomas Singer
2009-11-27 10:20         ` Thomas Singer
2009-11-27 10:56           ` Martin Langhoff
2009-11-27 18:35             ` Thomas Singer
2009-11-26 17:23 ` Jay Soffian [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=76718490911260923l1d22012cyf62904d14cde4198@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=thomas.singer@syntevo.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.
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 NNTP newsgroup(s).