Jean-Marc Lasgouttes wrote: > Angus> More importantly, tell me how I should recognize > Angus> .../preamble.tex is part of the file name. Ie, what > Angus> characteristic indicates that it is a file name? Is it the > Angus> blank line that follows or do I need to recognize the > Angus> characteristics of the .../preamble.tex string? > > There are a number of regexps for that, but in this case, it is the > opening parenthesis that triggers, I guess. > > I would do as follows: > > if I find a line with opening parenthesis so that what follows does > not form an existing file name and _if_ the line is exactly 80 chars > long (check the value, maybe), then try to merge with the next line. > > I also did a patch that I never applied which does the opposite > (handle several file name son the same line). I guess the two should > be merged. > http://marc.theaimsgroup.com/?l=lyx-devel&m=108232356511531&w=2
Ouch :-( How horrible. Using regexes to parse a file reminds me of reLyX and the pain I suffered in there. You know far, far more about these log files than me, but it seems that a file name is followed either by a space or by an empty line. That, together with your ideas above should result in a fairly robust test. MikTeX can handle file names with spaces in them, can't it? Maybe we need a log file containing such a file name too? -- Angus
