Use mv when applicable

[abaldwin88]

This...

roamer-trash-copy /Users/abaldwin/Desktop/bleh/meh.txt
cp /Users/abaldwin/Desktop/bleh/meh.txt /Users/abaldwin/Desktop/bleh/argh.txt
rm /Users/abaldwin/Desktop/bleh/meh.txt

Should instead be this...

roamer-trash-copy /Users/abaldwin/Desktop/bleh/meh.txt
mv /Users/abaldwin/Desktop/bleh/meh.txt /Users/abaldwin/Desktop/bleh/argh.txt

[alex-bender]

Hi @abaldwin88, could you please describe little bit the reason what command roamer-trash-copy exists for?
I want to pick up this issue.

[abaldwin88]

It does two things:

• It copies an entry (document or folder) into the trash directory. Default directory is here: ~/.roamer-data/trash.
• It saves the trash entry in the SQLite db

This is done so that users can delete/overwrite files but still paste it in later sessions. In short it makes cut/paste operations work.

[alex-bender]

Aha, I see, thanks.

[alex-bender]

What do you think about using hard links instead of copying moving files?

Maybe even copying.

[abaldwin88]

The tricky part is linking to the correct content after a file has been copied over top of. Take a look through some of the test cases around that.

…

On Oct 6, 2017 12:12 PM, "Alex Bender" ***@***.***> wrote: What do you think about using hard links instead of copying files? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AOeD_bzvTWPkk9CUCovKl7SA4JuAJtXZks5splF0gaJpZM4PGu8H> .