>>>>> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Actually this is still wrong. The order in 1.4 is: Georg> - Parse all known LyX arguments in the LyX singleton and store Georg> them - Let the frontend parse and remove all arguments that it Georg> knows - Complain for all remaining arguments that are not Georg> filenames in the LyX singleton Georg> The difference to the procedure above is that it is possible to Georg> override frontend options in LyX. Yes. >>> In particular, if the toolkit has arguments like "-c 3", the "3" >>> will be read as a file name... Georg> But not if the toolkit eats all known arguments first. Or do I Georg> miss something? No, I was trying to point out the difficulty of interpreting our own arguments without touching the toolkit's ones. >> Which is bad. Would you accept a change WRT the argument interface? Georg> No. I start LyX (and other programs) with filenames many times Georg> a day, and always adding -f for LyX would be inconsistent and Georg> too much work. I do not want this -f either. In general, we shall not introduce such limitations for reason that are just our internal organization of code (like the issue of mathed color corners). JMarc
