On Sat, Oct 10, 2015 at 09:26:34PM +0200, Stephan Witt wrote: > Am 10.10.2015 um 20:40 schrieb Scott Kostyshak <skost...@lyx.org>: > > > On Sat, Oct 10, 2015 at 01:16:42PM -0500, jken...@ssc.wisc.edu wrote: > >>> On Sat, Oct 10, 2015 at 08:40:28AM -0500, jken...@ssc.wisc.edu wrote: > >>>> > >>>> > >>>>> On Thu, Oct 08, 2015 at 03:32:48PM +0200, Stephan Witt wrote: > >>>>>> This is really interesting. > >>>>>> > >>>>>> LyX 2.2.0 fixes some problem on latest Mac OS "El Capitan". > >>>>>> I guess the fix is there because of the change to Qt5. > >>>>> > >>>>> John, was the "can't preview PDF" issue that users of El Capitan > >>>> have > >>>>> reported also fixed with the 2.2.0 snapshot? > >>>>> > >>>>> Scott > >>>> > >>>> Yes, that problem seems to be fixed. I tried command-R and > >>>> command-T, > >>>> and both work, and clicking the view icon works too. > >>> > >>> Good to know. > >>> > >>>> I have SIP disabled -- should I re-enable SIP and see if it still > >>>> works? > >>> > >>> No, not now at least. I would have asked you to re-enable SIP, confirm > >>> that the problem exists with 2.1.4 and that the problem does not exist > >>> with LyX 2.2dev. I don't want you to spend the time to do that at this > >>> point, unless you are curious yourself. > >> > >> This of course made me curious (and as far as time is concerned, the > >> work you guys have done has already saved me lots and lots of time). > >> SIP doesn't seem to have anything to do with either the preview > >> problem or the palette problem. The palette problem exists in LyX > >> 2.1.4 under El Capitan, and the problem disappears in 2.2.0dev (April > >> 14, 2014). > > > > Great, thanks for testing! > > > >> I can't reproduce the preview PDF problem in either LyX version under > >> El Capitan. > > > > Good to know. This means we need to find a tester who does have the > > preview problem to see if 2.2.0dev makes things better. > > In theory the problem with SIP is the mismatch of the PATH setting in > preferences and the real file system. "In the past" the MacTeX installer > puts the things to /Library/TeX/texbin and adds sym links to /usr/bin > to reduce problems with missing PATH settings. With SIP enabled > these sym links are forbidden and will be removed. So the program has > to add /Library/TeX/texbin to the PATH explicitly. This has to be done > within the LyX binary (the user preferences) because of the 2nd "security > feature" - the settings in .profile of the user are not used for programs > launched from the desktop icon (e.g. the so called dock). This makes the > MacTeX installation invisible for LyX. > > The 2.1.4 binary is distributed with /Library/TeX/texbin in PATH as setup > default value. But users who are doing an upgrade doesn't benefit from this > because of the settings migration. LyX has no good mechanism to adjust the > settings on upgrade to some new version. This may be improved within the > 2.2.0 release, but I don't know of an acceptable way.
Thanks for the explanation. By upgrade do you mean ugrade of LyX or OS X? I don't actually understand what it means to upgrade LyX. Does it mean to use the old user directory with the new version? So if someone does a fresh installation of LyX 2.2.0dev on El Capitan there should be no problem? > A change of configure.py > is a controversial possibility. > > I couldn't test this with El Capitan - but it's easy to simulate this on any > platform (and I did it for 2.1.4). Although it's uncertain if there are any > other problems with the upgrade to El Capitan. Indeed. I am worried there are some lurking problems. Hopefully we will hear about them soon. > I hope I can install El Capitan on an external drive soon to test it. That would be great. That, combined with feedback from several others testing 2.2.0dev on El Capitan should be enough for us to be confident with the final 2.2.0 release. Scott
