Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[REQ] Use shared name of files excluding [.ext] #236
Thank you for making Keka. I use it regularly and promote it heavily amongst our user base for use with ROMs in our GitHub project: Provenance.
I'd like to make a feature request:
But we could infer the filenames from the shared naming to resolve this:
Examples of basic multi-file sets:
The basic idea of this would be to infer the archive name from the commonality of the shared filename, excluding the variable
Suggestion: Archive as:
As a more advanced version it would be also nice if it could infer a set from common file-naming conventions such as…
Example of complex multi-file sets:
—by excluding the variable filenaming as 'tails', when the majority frontend naming is shared and equivalent.
Suggestion: Archive as:
Additionally, if any of this could be done in a single drop instead of in queued groups, even better, but I'd be happy with the first phase of this, if there is interest in it.
@gingerbeardman, Thanks for the upvote on this, but not sure it's very strongly related to the other thread—maybe in terms of inferential naming, but I think the suggestion here is a bit more universal than inferring from containing folders… I think I agree with the commentary on that thread.
Thanks @sevdestruct for such a complete request. Cool project you're working on, by the way.
So if I got it right, the thing will be:
I'm thinking in a check in the Preferences for
Thanks! Give it a test run on your iOS/tvOS device(s) sometime and drop by our Discord server.
Yeah, i think that's basically it, although in 2nd part of your list I would try to do it universally versus specifically to disk # or part # …instead opting for something more universal if possible, i suggested above:
…then again, today I encountered these filenames:
…an extreme case which though it makes me think of scenarios where the command part may not be the majority, but nonetheless prefixed identically. Perhaps when words like Disk, Track, Part and numbers are detected, can be an extra failsafe just incase the prefixxed text is actually the minority but still identical and still a set.
I am sure there are filenaming conventions that have a prefix that are not considered a set but are just similar types of things that start with the same kind of naming:
Though, I feel there is definitely a means to make this rather catchall and universal if we get clever. But before it's robust enough automatically, might need easier access to a toggle. (maybe the first version of this just allows grouping of things that start the same (regardless of majority) without getting too clever, yet.