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

Can't escape characters in Scan syntax and other regex issues #265

Open
Sirver51 opened this issue Sep 9, 2022 · 0 comments
Open

Can't escape characters in Scan syntax and other regex issues #265

Sirver51 opened this issue Sep 9, 2022 · 0 comments

Comments

@Sirver51
Copy link

Sirver51 commented Sep 9, 2022

Can't use backslash ("") to escape characters in the regex provided to the scanning tool because they get converted to forward slashes ("/"), thereby invalidating the regex. For example:

/content/{re:"\[.*\]"}/

Results in:

[CommandError|120]: Command(166) has failed with: [ScanError|130]: [Errno 2] No such file or directory: '//content/{re:"/[.*/]"}'

The regex engine being used also seems to lack convenience tokens like /w and /W, and there doesn't seem to be a way to specify which part of the match should be taken as the collection/series/gallery token. For example, if I have:

/content/
    [<artist>] <series>/
        [<artist>] <chapter_name_1>.zip
        [<artist>] <chapter_name_2>.zip
        [<artist>] <chapter_name_3>.zip

The actual galleries are going to have the artist parsed as <artist> because it's in the name, but how do I get the series/grouping name to be <series> instead of [<artist>] <series>?

Environment:

  • OS: Ubuntu Server 22.04
  • Browser: Chrome 105.0.5195.54
  • HPX Version: 0.13.3 (client: 0.13.1)

Additional context
Installed via docker-compose.

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

1 participant