Communities

Writing

Codidact Meta

The Great Outdoors

Photography & Video

Scientific Speculation

Cooking

Electrical Engineering

Judaism

Languages & Linguistics

$Mathematics$

tag:snake search within a tag

answers:0 unanswered questions

user:xxxx search by author id

score:0.5 posts with 0.5+ score

"snake oil" exact phrase

votes:4 posts with 4+ votes

created:<1w created < 1 week ago

post_type:xxxx type of post

Search help

Notifications

Mark all as read See all your notifications »

Q&A Code Reviews Meta

Q&A

Posts Tags Edits

Ask Question

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Get global gitconfig path

Parent

Get global gitconfig path

+3

−0

Is there a command I can run to get the path of global gitconfig for a user? Like git config --global --edit, but I want the path, not an editor window.

I want the right path whether or not this file already exists. i.e. I want the path that Git will use, even if this is a brand new system. This may pose problems for git config --list --show-origin --show-scope.

I can't figure out how to disable the hint in the command below, but that would work great.

git -c 'core.editor=echo' config --global --edit

git

posted 7 days ago

CC BY-SA 4.0

6d ago

Michael‭

861 reputation 3 20 91 71

Raw

Markdown

History

is a duplicate

This question has been asked before and has already been answered. It should be marked as a duplicate.

Please enter the URL of the proposed duplicate in the details field below.

not constructive

This question cannot be answered in a way that is helpful to anyone. It's not possible to learn something from possible answers, except for the solution for the specific problem of the asker.

2 comment threads

Not sure if it answers, but the [documentation](https://git-scm.com/docs/git-config#FILES) says: >... (2 comments)

The wording of the question is confusing (2 comments)

Post

+2

−0

This works for me in both bash and zsh on Debian 12. I can't guarantee it will work the same on every platform and shell.

EDITOR=echo git config --global --edit 2>/dev/null

or, if you prefer not to rely on environment variables:

git -c "core.editor=echo" config --global --edit 2>/dev/null

This is based on your original attempt, with an additional stream-specific redirection which gets rid of "hint: Waiting for your editor to close the file..." because this hint is (conveniently) written to stderr whereas the actual output goes to stdout.

posted 5 days ago

CC BY-SA 4.0

5d ago

InfiniteDissent‭

21 reputation 0 1 2 1

Copy Link

Raw

Markdown

History

1 comment thread

Good find (3 comments)

Michael‭ wrote 5 days ago

copy link

Thanks! I kept searching for the advice.* variables to turn off the hint, but I didn't think to check the output stream itself.

I think I'm going to use this but move the editor assignment in the CLI config override like I have it in OP.

git -c 'core.editor=echo' config --global --edit 2>/dev/null

Welcome to Codidact!

alx‭ wrote 5 days ago · edited 4 days ago

copy link

Wow! Great idea!

Minor caveat: the environment variable doesn't work in my case, because I do have the following in my gitconfig file:

[core]
	editor = vim

which maybe I should remove. I think I added that to avoid using nano(1) in new Debian installations, but I tend to purge it as one of the first things I do, anyway.

But the -c 'core.editor=echo' version does work for me.