63688b0d6e
Of course, the calling process is different from us, and we can't actually change their PWD >_< *sigh* But, this can be put in e.g. an alias, which seems to be what most jump/cd expanding types of programs do. We are not those, so, going beyond what most of those do with ptrace and hackery is not really in scope... But ugh, I hate this. But I still want this feature for myself so ¯\_(ツ)_/¯ Signed-off-by: Christina Sørensen <christina@cafkafk.com> |
||
|---|---|---|
| benches | ||
| bin | ||
| doc | ||
| src | ||
| tests | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| cliff.toml | ||
| CODE_Of_CONDUCT.md | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE | ||
| README.org | ||
gg - git gut
A Rust GitOps/symlinkfarm orchestrator inspired by GNU Stow. Useful for dealing with "dotfiles", and with git support as a first class feature. Configuration is done throug a single yaml file, giving it a paradigm that should bring joy to those that use declarative operating systems and package managers.
Although this isn't really a case where it matters that much for performance, being written in rust instead of e.g. janky scripting languages does also mean it is snappy and reliable, and the extensive (hardly, but eventually) testing helps ensure regressions aren't introduced.
That said, we're in 0.Y.Z, here be dragons for now (although a little less each commit).
Installation
$ git clone https://github.com/cafkafk/gg
$ cd gg
$ cargo install --path .Configuration
If you want a template, you can copy the file from src/test/config.yaml:
$ mkdir -p ~/.config/gg/
$ cp src/test/config.yaml ~/.config/gg/config.yamlYou should seriously change this file before running any commands.
The configuration format will likely break regularly in versions 0.Y.Z.