On Sonntag, 29. August 2021 15:41:06 CEST Kolja Koch wrote:
> > Regex patterns are doing the job, including use cases that go beyond
> > your
> > personal needs, and I don't have to maintain parsing code by myself.
> > So the
> > plan is to make this feature configurable by standard regex patterns
> Because somebody would need to write *and* maintain all of that
> software. Keep
> in mind that almost all people stepping by here are usually just
> saying
> feature x doesn't work, please fix it. Or feature y is nice, but
> please extend
> it in this and that way.
>
True!
> I understand t
On Samstag, 28. August 2021 20:23:34 CEST Kolja Koch wrote:
> > wav2gig -a '(.*) - \d* - .* - .*.wav" \
> >-b '.* - (\d*) - .* - .*.wav" \
> >-c '.* - \d* - (.*) - .*.wav" \
> >-d '.* - \d* - .* - (.*).wav"
>
> It took me a moment to understand your prop
I was thinking a little bit more about this.
Maybe we should agree upon some kind of complexity-level we want to
catch.
For instance:
The user might want to put samples into a gig-file, that have no common
filename structure. We could write an interface to let him enter the
required attributes (wi
