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

Suggestion: Add ability to include templates for files to skip #9

Closed
pastiche9761 opened this issue Jan 7, 2017 · 5 comments
Closed

Comments

@pastiche9761
Copy link

utorrent has the ability to create a delimited (|) template of files that will be skipped in the directory when the torrent is created. Could this be implemented?

From help file:
The Skip Files field allows you to skip files using specific filters. This field only gets activated if you use the "Add directory" button. Wildcards can be used to specify multiple files.

In several places in µTorrent, wildcards can be used in place of normal characters in order to specify a pattern of characters that µTorrent should use to match whatever it needs. The following may be used in those situations:

  • (asterisk) to match any text of any length
    ? (question mark) to match any single character
    | (vertical pipe) is an "or" conditional
    Example: File?A|File?B* matches any file that contains File?A anywhere in the filename (where ? is any single character, such as a space or an underscore), or any file that begins with File?B in its filename (again, where ? is any single character).
@kz26
Copy link
Owner

kz26 commented Jan 9, 2017

Yes, regex-based file exclusion support is planned for the future. The dottorrent library would need to be updated as well.

@nyakze
Copy link

nyakze commented Jan 21, 2017

I second this. Since I migrated from uTorrent to qBt, I have to start up uTorrent again to make a torrent when I need to exclude certain filetypes from a folder.

@fecchan
Copy link

fecchan commented Mar 15, 2017

Since the dottorrent backend already supported this, I think it's just a matter of time until this gets implemented. Looking forward to it!

@kz26
Copy link
Owner

kz26 commented Mar 15, 2017

Yep, I plan to get this into the next release when I have a chance...unless of course someone beats me to it with a PR!

@kz26
Copy link
Owner

kz26 commented Mar 19, 2017

Implemented in version 1.3.0/1.3.1.

@kz26 kz26 closed this as completed Mar 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants