Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cli: let "config set"/"unset" continue if file to edit can be disambiguated #5101

Merged
merged 3 commits into from
Dec 15, 2024

Conversation

yuja
Copy link
Collaborator

@yuja yuja commented Dec 15, 2024

Checklist

If applicable:

  • I have updated CHANGELOG.md
  • I have updated the documentation (README.md, docs/, demos/)
  • I have updated the config schema (cli/src/config-schema.json)
  • I have added tests to cover my changes

CHANGELOG.md Outdated Show resolved Hide resolved
yuja added 3 commits December 15, 2024 16:25
This patch adds simpler user/repo_config_path() accessors. existing_*_path()
are kinda implementation details (for testing), so they are now private methods.
new_user_config_path() will be removed later.
…guated

If the user config path was an empty directory, these commands would fail with
EISDIR instead of "can't set config in path (dirs not supported)". I think this
can be changed later to create new "$dir/config.toml" file. Maybe we can also
change the default path to ~/.config/jj directory, and load all *.toml files
from there?
I don't think the new behavior is strictly better, but it's more consistent
with the other "jj config" commands so we can remove the special case for
"jj config edit".
@yuja yuja force-pushed the push-qvromyyrtokp branch from 7253669 to b138da9 Compare December 15, 2024 07:26
@yuja yuja enabled auto-merge (rebase) December 15, 2024 07:26
@yuja yuja merged commit e50673d into jj-vcs:main Dec 15, 2024
18 checks passed
@yuja yuja deleted the push-qvromyyrtokp branch December 15, 2024 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants