On 10/14/07, Bennett Helm <[EMAIL PROTECTED]> wrote: > I thought you were doing fine! No one else has reported such a > problem, so I'm guessing it's something peculiar to Honest's system. > The trouble is that it's unclear what changes Honest might have made.
At the lyx level I cleared all configuration information I was aware of when installing 1.5.2 because the earlier 1.5 versions on OSX 10.3 were not functioning particularly well. This problem existed, 1.5.2 introduced another in being unable to change the screen font, it can be unreasonably slow and seems to make the graphics card buzz at times,... but the most serious problem is probably that the code will not compile and so I cannot simply run it under a debugger and report what is wrong. The inability to compile easily has been a problem with lyx for many years since opting for bleeding edge C++. I used to use a Sun workstation before the powerbook and made significant efforts to get lyx to compile when boost was first adopted but had to eventually accept defeat. Now when lyx fails to compile I make no effort to fix it although I will sometimes report it. This is not really intended as a criticism but more an observation since I presume those that put in the time and effort are attracted to writing C++ programs in this manner. > One workaround might be to set LyX > Preferences > Paths > Temporary > directory setting to something in his home directory, such as ~/tmp. > Then quit and restart LyX and see if the problem reemerges. > Otherwise, I'm at a loss. The problem is not directly the one being reported. There is nothing wrong with the permissions of the reported files to prevent them being deleted. 777ing everything before quitting makes no difference. I tried your suggestion but the behaviour was the same. The problem may well be related to the environment. The compilation of lyx fails with complaints about a C++ file called environment.
