> I do not like much this solution... Having a dialog saying "lyx is not > configured correctly. Try to fix" and two buttons "reconfigure" and > "quit" would look better. With your solution, the user has to hunt in > the menus to guess which actions are possible.
This does not contradict with my patch at all. I did not do it simply because I do not know how to do it. At which point of the source code that I can insert this dialog? It is also possible to hack menubackend and display a single reconfigure menu item in this case. > But the right solution would be to make configure.py robust. As I have said, lyx should be able to start in any case, and configure.py may fail to produce valid list files if it is killed, no matter what we do in configure.py. Cheers, Bo
