-
Notifications
You must be signed in to change notification settings - Fork 77
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] Before auto-name, hardlink, softlink or copy #135
Comments
I see your point about seeding. It's beyond the scope of overall simplicity of nefarious, but I'm always open to contributions if someone wants to invest the time. I'm definitely not opposed to the feature, but I try and focus on the general-use stuff. Here's some of the relevant logic: Function that returns the new names: nefarious/src/nefarious/utils.py Line 141 in 5e1c893
Get the new name: Do the rename within transmission: |
It would be a great feature to be able to hard link the content to another folder where it is renamed to the right convention. Many private trackers require the files to be named exactly the same for seeding.
I tried to do this myself but I could not figure out where the renaming process is happening. Would love to know!
The text was updated successfully, but these errors were encountered: