Bo Peng wrote: > Your second regex can be wrong since . is allowed in path, at least > under linux.
I see what you mean (a preceding dot, as in ./myfile; any other dots in the path are allowed, aren't they?). What I try to assure with that is that the blank is checked after the _first_ dot. With a regex like "File: (.+\\.[^ ]+).*", a line like File: babel.def 2004/11/20 v3.8d Babel common definitions is returned as babel.def 2004/11/20 v3.8d instead of babel.def Any idea? > I do not know why it can not parse your two examples > though. Your committed version seems to be fine but why is the + after > \\.? Are you allowing multiple .? Oops. This wasn't intended (I'll change that, even if it would not harm to allow multiple dots). > I would do .+\\.\w+ (not tested). But then the brackets are not excluded. Jürgen
