git/list[1] front-page[2] threads[3] people[4] search[5] about
 

BUG: "git add --interactive" does not work with UTF-8 filenames

From
TLTeemu Likonen <tlikonen@iki.fi>
Date
Apr 1, 2008, 19:32 UTC
Message-ID
<200804012232.03559.tlikonen@iki.fi>

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.

Next: Jakub Narebski
Message 1 of 8 in “BUG: "git add --interactive" does not work with UTF-8 filenames”
  1. Teemu LikonenApr 1, 2008
  2. Jakub NarebskiApr 1, 2008
  3. Teemu LikonenApr 1, 2008
  4. Junio C HamanoApr 2, 2008
  5. Jakub NarebskiApr 2, 2008
  6. Junio C HamanoApr 2, 2008
  7. Describe the bug about handling non-Ascii filenames in 'git add -i'Teemu Likonen, Apr 2, 2008
  8. Junio C HamanoApr 2, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.