`tuckr pop` does not support popping individual files/directories

[MaddyGuthridge]

I consider "pop" to be the opposite behaviour of "push", and so I think tuckr pop should do the inverse of tuckr push.

Currently, tuckr pop just removes the group and cleans up its symbolic links (ie tuckr rm some_group && rm Configs/some_group), whereas tuckr push begins with the given files already existing on the system.

As such, I think it would be logical for tuckr pop to restore any symbolic linked files from some_group to just be regular old files, ie: for each file in some_group:

1. Copy the file from the dotfiles repository to its install location on the system, replacing the symbolic link
2. Remove the file from the dotfiles.

This would also lend itself nicely to allowing specific files to be given as arguments to tuckr pop, expanding the usefulness of the command.

[MaddyGuthridge]

Happy to help implement this :)

[RaphGL]

yeah, I like this idea.
So you'd have something like:

• tuckr pop <group>: pops files out of the dotfiles and into $TUCKR_TARGET
• tuckr pop <group> <...files>: pops the specified files from the group

You should make a -d/--delete option that just straight up deletes the files. Because that's the way I tend to use it most often :P

I'm not too sure about what's the best UX for the file paths themselves, but I'll let you figure it out.

[RaphGL]

I've partially implemented the fix discussed in this issue with 2f99874

I haven't implemented the popping for specific files yet, like I stated, it only does it for the entire group, so I decided not to close this issue just yet. If you're up for the task, go for it, otherwise I'll implement it eventually myself.

[MaddyGuthridge]

Awesome! Thanks for your work. Sorry for the delays with mine, work has started ramping up so I haven't had so much time to do side projects.

[RaphGL]

No worries. Take your time.