git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: git@vger.kernel.org
Subject: BUG: "git add --interactive" does not work with UTF-8 filenames
Date: Tue, 1 Apr 2008 22:32:03 +0300	[thread overview]
Message-ID: <200804012232.03559.tlikonen@iki.fi> (raw)

I just learnt that "git add --interactive" does not work with UTF-8 
encoded filenames. Maybe it's about all 8-bit characters.

The menu invoked with command

  git add -i <file>

does not even show this <file> if the name contains UTF-8 characters. 
Command and menu

  git add -i

shows the file but nothing can be done with it. Neither "patch" 
nor "update" does work, for example.


As a side note/rant: Git tends to show non-Ascii characters in filenames 
as \xxx escape sequences. It's not a big problem but surely it's not 
very nice to read if (say) half of the word's letters are escaped like 
this. I believe Git is mostly used for tracking source codes where 
Ascii-only filenames are a common practice. I'm using Git to develop 
Finnish spell-checking system (called Voikko) and we have some 
non-Ascii filenames in the repo.

             reply	other threads:[~2008-04-01 19:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 19:32 Teemu Likonen [this message]
2008-04-01 20:08 ` BUG: "git add --interactive" does not work with UTF-8 filenames Jakub Narebski
2008-04-01 20:29   ` BUG: "git add --interactive" does not work with UTF-8 filenames if core.quotepath=true Teemu Likonen
2008-04-02  0:41   ` BUG: "git add --interactive" does not work with UTF-8 filenames Junio C Hamano
2008-04-02 11:17     ` Jakub Narebski
2008-04-02 15:50       ` Junio C Hamano
2008-04-02 17:06     ` [PATCH] Describe the bug about handling non-Ascii filenames in 'git add -i' Teemu Likonen
2008-04-02 17:18       ` Junio C Hamano

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200804012232.03559.tlikonen@iki.fi \
    --to=tlikonen@iki.fi \
    --cc=git@vger.kernel.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 public inbox

	https://80x24.org/mirrors/git.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).