Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Optionally create symlinks instead of move or copy #16

Open
timshannon opened this issue Jun 29, 2018 · 2 comments
Open

Comments

@timshannon
Copy link

Just what the title says. It'd be nice not to have to duplicate files or move files from where another process may be expecting them.

@PoppyPop
Copy link
Contributor

I will have multiple problems with creating symlink.

All OS does not support it (windows)
Symlinks only work if in the same partition.
You will get an hudge flat AutoOrganize directory with all your file, potentially with the wrong name.
At each scan, the plugin must guess if the file is already symlinked.

For the 2 last argument this will give a scan that can last hours, if it work.

if you're already on Unix system and with a single partition the move command take no time, it's just an logical move.

After that the purpose of this plugin is to read a flat directory with multiple files, identify files and organize it in the correct destination folder

@bjoern-vh
Copy link

Hello,

I would also be very happy about this feature.
Also don't share your argumentation ;-)

All OS does not support it (windows)

Not all file systems support symlinks (FATx), but Windows (NTFS) does. For example here: https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

Symlinks only work if in the same partition.

This is not true. Hardlinks must be on the same partition, symlinks work. See here: https://serverfault.com/questions/300713/how-to-create-symbolic-link-ln-between-two-partitions

You will get an hudge flat AutoOrganize directory with all your file, potentially with the wrong name.
At each scan, the plugin must guess if the file is already symlinked.

The same problem exists when copying files.

Kind regards
Bjoern

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants