-
Turabian 8 support will be included in 5.2b which is currently in beta. The current version of Turabian shipping is version 7. The open-source history of all of the styles we ship is available on github under the citation styles repository. Periodically, we update the versions we ship in the app to make sure they are up to date. The history of the Zotereo
-
Alan, It looks like that crash log that was submitted was dated: Date/Time: 2014-03-26 08:31:22 +0000 Do you have a crash report in /Library/Logs/ or ~/Library/Logs with "Logos_2014-03-26" in the name? If so, what's the full name of the file?
-
Thank you too Jack :)
-
Alan, Thanks for the grace and sense of humour! And thanks for taking the time to report it. Again, sorry for the inconvenience. Tom
-
[quote user="Jack Caviness"] [quote user="Alan Macgregor"] Personally, I think of it as an extra splash screen, designed to annoy both users and developers in equal measure.[/quote] Does not seem to have annoyed developers as much as it does us users [/quote] Jack, The developers occasionally introduce crashes and fix them in the normal course of development
-
Martin, I don't think I've ever seen an indexer log quite that big. It should get recreated every time the app runs, so it seems the indexer got "stuck" on something. Can you try running this from the command line in Terminal: tail -n1000 ~/Library/Application\ Support/Logos4/Logging/Indexer.log > Indexer_huge.log && zip ~/Desktop/Indexer_huge.zip Indexer_huge
-
Darryl, One other question: Are you clicking on the title to open the resource, or pressing Enter or dragging the resource out? Are you typing in the filter box to filter before you open the resource? You seem to be able to reproduce this with some regularity, so I'm just curious if there might be more information that can help us.
-
[quote user="Darryl Burling"] Just to narrow this down further, the crash doesn't seem to occur if I open a library pane (i.e. cmd+L), only if I click the library button and try and open a resource. Hope that helps. [/quote] Darryl, That helps alot! Having a set of steps to reproduce this (even a partial set) is helpful. I saw the crash reports for
-
The problem is that the latest crash report file ( Logos_2014-04-06-234152_XXs-Mac-mini.crash) was modifed on Apr 13 at 9:38 PM, which was after it was originally submitted. Currently, if a crash report is modified it will get resubmitted because the crash reporter looks for a more recently modified crash report than the last time it sent a report.
-
It looks like the "crash" log that was sent was an old one from 4-6-2014 when you were running 5.2a (5.2.1.0067). Would you mind running the following command from Terminal and pasting the output here? (You'll need to make sure it's all on one line) defaults read com.logos.Logos "CrashReportSender.lastCrashDate" && ls -lt ~/Library/Logs/DiagnosticReports
-
Alan, see my response here: http://community.logos.com/forums/p/82138/574924.aspx#574924
-
OK, so it looks like this might be a new issue with Mavericks. We're investigating and should have a fix post 5.2a Beta 6
-
Alan, I think this should be fixed now. Thanks, Tom
-
I think this should be fixed now. Can you repost here if it starts happening again?
-
[quote user="Jon crappel"]Tom -- Thanks for your reply. I am on 5.2 SR-6, and I can assure you that I am still experiencing crashes. You probably don't see crash reports because I've clicked out of sending them recently, just because I sometimes feel it's useless. Sorry, but every time I see the prompt to send a crash report it just reminds me that
-
John, I'm sorry you've had a poor experience with Logos on the Mac. I went into our crash reports database and the last crash reports from your user account are back in Dec 2013 on version 5.1a SR-2. Most of the crash reports we have from your systems were related to the sleep issue that we fixed in 5.2 SR-5 and the 5.2a betas. If you update to the
-
[quote user="David Sobey"] Hebrew font options [/quote] This is the same issue that Jack mentioned. 5.2a will fix this (currently in beta) issue and allow SBL BibLit, SBL Hebrew, Ezra SIL or Ezra SIL SR to be used as your Hebrew font if you have those fonts installed. To work around the issue, you can temporarily uninstall Ezra SIL from Font Book on
-
Our Mac crash reporting server is having some issues receiving crash reports, so the desktop app thinks it needs to submit the crash logs every time. I've notified our operations team. For now, if you want to work around the issue, delete any "Logos .crash" files in ~/Library/Logs/DiagnosticReports.
-
[quote user="Jack Caviness"] [quote user="Tom Philpot (Logos)"]We ship a versions of Ezra SIL and Ezra SIL SR internally in the Logos.app bundle so that is why the font is always available in the app, even if you don't have it installed.[/quote] Suspected as much. Thanks for the confirmation. Guess you need to include a way to override the duplicate
-
Jeremy, Left and Right switch to parallel resources, so we can't repurpose those keys. But you can always use Space and Shift-Space to go forward/backward one page in either resource viewing mode. Hope that helps.