Then I can make the choices:

• make-change
• dry-run
• ask

It would be great to have something like:

fling --src-dir grabbit import filename

This would be a shortcut for:

# move the file to the specified src-dir
mv $HOME/filename grabbit/filename

# link the file
fling --src-dir grabbit link

At the moment, I have a makefile that sorta lets me automate this, but having it be a fling-native command would be amazing :)

Now that I'm on windows more, I'm finding that I can't really assume the same folder locations and maybe other things.

Ideas:

• analyze apps in dotfiles for what symlinks I'd like on which platforms/hostnames/etc
• research whether anything like this exists in other dotfile managers
• try to turn that into a config file format I can use- maybe prototype the whole thing with a hardcoded python script so I can evolve relevant data structures
• add subsection to use this new format
• move current link/unlink functionality to subsection (breaking change)

Ideas:

Make a group of symlinks the basic unit of work and identity it by tags (name == nvim and auto filled in properties (hostname/os/???)

Have the user retrieve the units of work (symlimk groups) via boolean search query and then execute them

The issue is going to be setting defaults per platform per unit of work and how to structure that

https://engineering.kablamo.com.au/posts/2021/quick-comparison-between-go-file-walk-implementations/

I also probably need to sort fileInfo stuff to make them easily comparable in tests if I switch to an unordered filewalking function

Add UnsetSentinal

Assignees:
Labels:
Milestone:

https://github.com/volllly/rotz

Thank you for this awesome tool. Can implement the '--no-folding' feature just like stow?