-
Notifications
You must be signed in to change notification settings - Fork 22
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
allow to specify build exceptions #32
Comments
We should avoid yet another (additional) configuration file. Maybe just the mmt command line syntax for "
where |
Also |
I am not sure, how would I do the following use case: I would like to say something like
and I have the expectation that it would build all the omdoc files that need building. But it would not recurse into the |
It does not recurse into |
is there a way to specify that it should leave out a specific file in this? e.g. because it is not ready? |
No, but would you like to add the name of such a file into another file (like META-INF/MANIFEST.MF)? |
BTW the |
yes, the proposal here was to to a file |
Ok, it's implemented by a167960. Several regexprs (separated by blanks) may follow the colon. I've tested it with a single file. I'm not sure how |
documentation is at the bottom of https://github.com/KWARC/MMT/wiki/Customizing-LaTeXML-processing |
The java pattern http://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html for your example must be written as |
Make a new ticket if also directories should be excluded. |
allow to specify exceptions for directories, too |
I think that the regular expressions should just match the full relative path to the file. That would be useful to me. I have committed a regular expression in ```MiKoMH/TDM/META-INF/MANIFEST.MF |
I match the relative path (below source), now. Also positive |
someone wanted special |
I would like to have mechanism where I can specify files that should not be built (by a regexp). I imagine a
.mmtbuild
file per directory which has entries likeAnd when we have something like this, we could have other build-config targets as well.
The text was updated successfully, but these errors were encountered: