From: Theodor Negrescu <theodor.negrescu@gmail.com>
To: git@vger.kernel.org
Subject: Re: BUG: Git path --config doesn't work with ~ symbol
Date: Wed, 5 May 2021 21:13:58 +0300 [thread overview]
Message-ID: <CAEumJaBDqSyqbnvWSeCyXYQJz92dOg+y1pz2JLjPSMRzWxc1aA@mail.gmail.com> (raw)
In-Reply-To: <CAEumJaDRvU8LP=q3PQ1z6-cg75DmbHE_7OXZVA+nm=-77pVLEg@mail.gmail.com>
I meant Git config --file!! Sorry, I wrote the wrong thing in the title.
On Wed, May 5, 2021 at 9:06 PM Theodor Negrescu
<theodor.negrescu@gmail.com> wrote:
>
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
>
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> I ran the command "git config --file ~/git-settings/.gitconfig -l"
> (git-settings is a repo where I keep my config, the global one is just
> an include)
>
> What did you expect to happen? (Expected behavior)
>
> It would list the settings in the file.
>
> What happened instead? (Actual behavior)
>
> fatal: unable to read config file '~/git-settings/.gitconfig': No such
> file or directory
>
> What's different between what you expected and what actually happened?
>
> The ~ symbol should point to my home folder.
>
> Anything else you want to add:
>
> "git config --file ~/.gitconfig -l" doesn't work either so the ~
> symbol is the problem.
> fatal: unable to read config file '~/.gitconfig': No such file or directory
> "git config --file .gitconfig -l" works when I run it from my home
> folder or from git-settings so the --file argument is working.
>
> [System Info]
> git version:
> git version 2.31.1.windows.1
> cpu: x86_64
> built from commit: c5f0be26a7e3846e3b6268d1c6c4800d838c6bbb
> sizeof-long: 4
> sizeof-size_t: 8
> shell-path: /bin/sh
> feature: fsmonitor--daemon
> uname: Windows 10.0 19042
> compiler info: gnuc: 10.2
> libc info: no libc information available
> $SHELL (typically, interactive shell): <unset>
>
>
> [Enabled Hooks]
> not run from a git repository - no hooks to show
next prev parent reply other threads:[~2021-05-05 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 18:06 BUG: Git path --config doesn't work with ~ symbol Theodor Negrescu
2021-05-05 18:13 ` Theodor Negrescu [this message]
2021-05-05 18:14 ` Jeff King
2021-05-05 18:21 ` Eric Sunshine
2021-05-05 18:30 ` Theodor Negrescu
2021-05-05 18:35 ` Jeff King
2021-05-05 18:59 ` Theodor Negrescu
2021-05-05 19:01 ` Jeff King
2021-05-05 18:32 ` Jeff King
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=CAEumJaBDqSyqbnvWSeCyXYQJz92dOg+y1pz2JLjPSMRzWxc1aA@mail.gmail.com \
--to=theodor.negrescu@gmail.com \
--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).