* 'git config --edit' unexpected behavior
@ 2023-04-10 19:44 Mervin Guy
2023-04-10 20:18 ` Jeff King
0 siblings, 1 reply; 4+ messages in thread
From: Mervin Guy @ 2023-04-10 19:44 UTC (permalink / raw
To: git
What did you do before the bug happened? (Steps to reproduce your issue)
- Changed my directory to a git-repo I was working on, using 'cd <directory_name>'. Then I ran 'git config --global -e'.
What did you expect to happen? (Expected behavior)
- I exepected the command to display my current-config file, with all settings included, in my editor.
What happened instead? (Actual behavior)
- My config-file was overwritten and displayed a default-setup message, the config-file was lost after this point.
I experimented with different ways of activating the command, but they all led to an overwrite of the file.
What's different between what you expected and what actually happened?
- The config-file should've displayed as-was, and no overwrite should've occurred unless explicitly commanded.
Anything else you want to add:
- It should be noted that I've been updating my config-file manually, up until this point. When updating it, I used
'[subsection] component' rather than 'subsection.component'.
[System Info]
git version: 2.40.0
cpu: i686
sizeof-long: 4
sizeof-size_t: 4
shell-path: /bin/sh
compiler info: gnuc: 12.2
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/ash
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 'git config --edit' unexpected behavior
2023-04-10 19:44 'git config --edit' unexpected behavior Mervin Guy
@ 2023-04-10 20:18 ` Jeff King
0 siblings, 0 replies; 4+ messages in thread
From: Jeff King @ 2023-04-10 20:18 UTC (permalink / raw
To: Mervin Guy; +Cc: git
On Mon, Apr 10, 2023 at 03:44:26PM -0400, Mervin Guy wrote:
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> - Changed my directory to a git-repo I was working on, using 'cd <directory_name>'. Then I ran 'git config --global -e'.
>
> What did you expect to happen? (Expected behavior)
>
> - I exepected the command to display my current-config file, with all settings included, in my editor.
>
> What happened instead? (Actual behavior)
>
> - My config-file was overwritten and displayed a default-setup message, the config-file was lost after this point.
> I experimented with different ways of activating the command, but they all led to an overwrite of the file.
That's certainly unexpected. "git config --global -e" works fine for me.
And Git itself won't overwrite the file; it will run your editor with
the name of the file, and the editor is responsible for any writing.
Which editor are you trying to use? Can you try running with:
GIT_TRACE=1 git config --global -e
which should show the editor command that Git runs.
-Peff
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 'git config --edit' unexpected behavior
[not found] <D6798678-9CC3-416F-B238-F3D28EC910B2@mervin.works>
@ 2023-04-10 23:05 ` Mervin Guy
2023-04-11 9:41 ` Jeff King
0 siblings, 1 reply; 4+ messages in thread
From: Mervin Guy @ 2023-04-10 23:05 UTC (permalink / raw
To: Jeff King; +Cc: git
I'm confident there is an error in the `git config --global -e` pipeline though (very likely git.c), because when using git-aliases the function performs as expected.
My current alias `ec` pointing to the command `!vi $HOME/.gitconfig` - where $HOME is `/root`. The full command looks like `git ec` and works as expected.
Meaning that the only difference between the failed-run and successful-run was calling the git built-in `git config --global -e`.
> On Apr 10, 2023, at 16:49, Hello World! <mail@mervin.works> wrote:
>
> Using the command, the trace says it’s using 'vi /root/.gitconfig' - which is indeed the set editor.
>
> For more verbosity, the call-chain is 'git.c' (trace: built-in: git config) → 'run_command.c' (trace: run_command: 'vi /root/.gitconfig') which doesn’t seem strange.
>>> On Apr 10, 2023, at 16:25, Jeff King <peff@peff.net> wrote:
>>> On Mon, Apr 10, 2023 at 03:44:26PM -0400, Mervin Guy wrote:
>>>
>>> What did you do before the bug happened? (Steps to reproduce your issue)
>>> - Changed my directory to a git-repo I was working on, using 'cd <directory_name>'. Then I ran 'git config --global -e'.
>>> What did you expect to happen? (Expected behavior)
>>> - I exepected the command to display my current-config file, with all settings included, in my editor.
>>> What happened instead? (Actual behavior)
>>> - My config-file was overwritten and displayed a default-setup message, the config-file was lost after this point.
>>> I experimented with different ways of activating the command, but they all led to an overwrite of the file.
>>
>> That's certainly unexpected. "git config --global -e" works fine for me.
>> And Git itself won't overwrite the file; it will run your editor with
>> the name of the file, and the editor is responsible for any writing.
>> Which editor are you trying to use? Can you try running with:
>>
>> GIT_TRACE=1 git config --global -e
>>
>> which should show the editor command that Git runs.
>>
>> -Peff
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 'git config --edit' unexpected behavior
2023-04-10 23:05 ` Mervin Guy
@ 2023-04-11 9:41 ` Jeff King
0 siblings, 0 replies; 4+ messages in thread
From: Jeff King @ 2023-04-11 9:41 UTC (permalink / raw
To: Mervin Guy; +Cc: git
On Mon, Apr 10, 2023 at 07:05:12PM -0400, Mervin Guy wrote:
> I'm confident there is an error in the `git config --global -e`
> pipeline though (very likely git.c), because when using git-aliases
> the function performs as expected.
>
> My current alias `ec` pointing to the command `!vi $HOME/.gitconfig` -
> where $HOME is `/root`. The full command looks like `git ec` and works
> as expected.
>
> Meaning that the only difference between the failed-run and
> successful-run was calling the git built-in `git config --global -e`.
OK, so we can guess it has to do with the "--edit" option specifically,
and your editor is doing what we'd expect. The main thing that code is
doing is just opening the editor, but there's this curious bit of code
before it does so:
$ sed -ne '851,+11p' builtin/config.c
if (use_global_config) {
int fd = open(config_file, O_CREAT | O_EXCL | O_WRONLY, 0666);
if (fd >= 0) {
char *content = default_user_config();
write_str_in_full(fd, content);
free(content);
close(fd);
}
else if (errno != EEXIST)
die_errno(_("cannot create configuration file %s"), config_file);
}
launch_editor(config_file, NULL, NULL);
That shouldn't be overwriting your existing file, since O_EXCL will
refuse to open the file in that case.
But I wonder if something funny is going on with the file selection. We
support both the traditional $HOME/.gitconfig location, but also the xdg
location (usually $HOME/.config/git/config, but $XDG_CONFIG_HOME can
tweak that).
When reading config for most commands, we will generally pull from both
sources. But for "git config --global", we have to pick one to operate
on, both for reading and writing. The logic is supposed to prefer
$HOME/.gitconfig, but use the xdg location if it exists and the $HOME
one doesn't.
From your output:
> > Using the command, the trace says it’s using 'vi /root/.gitconfig' -
> > which is indeed the set editor.
it's picking the $HOME one. You said you had previous contents that were
overwritten. How did you add them originally, and might they have been
in the xdg location? Can you see if there is anything in /root/.config/git?
I admit I still don't know how we'd trigger this case; if the file did
exist then we should never use /root/.config in the first place.
Another left-field possibility: is /root on an unusual filesystem (e.g.,
a networked one) where O_EXCL might not behave as it should?
-Peff
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-04-11 9:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-04-10 19:44 'git config --edit' unexpected behavior Mervin Guy
2023-04-10 20:18 ` Jeff King
[not found] <D6798678-9CC3-416F-B238-F3D28EC910B2@mervin.works>
2023-04-10 23:05 ` Mervin Guy
2023-04-11 9:41 ` Jeff King
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).