Yuya Nishihara ac52e43435 cli: let "config set"/"unset" continue if file to edit can be disambiguated ... 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?		2024-12-15 16:36:29 +09:00
..
examples	working_copy: plumbing to propagate untracked paths to caller	2024-12-11 20:19:51 +09:00
src	cli: let "config set"/"unset" continue if file to edit can be disambiguated	2024-12-15 16:36:29 +09:00
testing	style: inline variables into format strings	2024-10-04 22:29:13 +02:00
tests	cli: let "config set"/"unset" continue if file to edit can be disambiguated	2024-12-15 16:36:29 +09:00
build.rs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
Cargo.toml	cargo: drop dependency on config crate	2024-12-10 16:08:50 +09:00
docs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
LICENSE	cargo: add LICENSE file to each crate we publish	2023-09-22 21:48:28 -07:00