git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Yuri <yuri@rawbw.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [BUG REPORT] File names that contain UTF8 characters are unnecessarily escaped in 'git status .' messages
Date: Thu, 27 May 2021 06:56:28 +0200	[thread overview]
Message-ID: <20210527045628.uvesihyhtqrfyfae@tb-raspi4> (raw)
In-Reply-To: <6318ccec-ec96-91a8-fd65-85daf4a9a22b@rawbw.com>

On Wed, May 26, 2021 at 04:41:38PM -0700, Yuri wrote:
> On 5/26/21 4:32 PM, Junio C Hamano wrote:
> > "git config core.quotepath no"?
>
>
> I didn't have the 'core.quotepath' value set. 'git config core.quotepath no'
> changed the behavior to no quoting.
>
> So it looks like the default value of 'core.quotepath' is incorrect: it
> should be based on terminal capabilities.
>

This are 2 different things.
If you are in a project where only ASCII names are allowed (for whatever reason),
you may want `git config core.quotepath no`, regardless what the terminal can do.

(Beside that, are ther terminals that don't handle UTF-8 these days?)

Any, if you prefer UTF-8 as a default,

git config --global core.quotepath yes

is your friend (like mine)


  reply	other threads:[~2021-05-27  4:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 22:47 [BUG REPORT] File names that contain UTF8 characters are unnecessarily escaped in 'git status .' messages Yuri
2021-05-26 23:32 ` Junio C Hamano
2021-05-26 23:41   ` Yuri
2021-05-27  4:56     ` Torsten Bögershausen [this message]
2021-05-27 14:02       ` Jeff King
2021-05-27 20:50         ` Yuri
2021-05-28  4:39           ` Bagas Sanjaya
2021-05-28  4:45             ` Yuri
2021-05-29  9:27               ` Torsten Bögershausen
2021-05-30 21:44                 ` Jeff King
2021-05-30 21:55                   ` Yuri
2021-05-31  1:14                     ` Thomas Guyot
2021-05-31  3:35                       ` Bagas Sanjaya
2021-05-30 22:23                   ` 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

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

  git send-email \
    --in-reply-to=20210527045628.uvesihyhtqrfyfae@tb-raspi4 \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=yuri@rawbw.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).