Ready for El Capitan: DEVONthink and DEVONnote 2.8.6

Markdown with images in DEVONthinkOS X El Capitan became just available as public beta. Right in time, DEVONthink and DEVONnote 2.8.6 bring important compatibility changes for it. In addition, DEVONthink 2.8.6 supports images referenced in Markdown documents. When importing Bookends references, DEVONthink imports their keywords too. PDF text annotations created by other applications keep their appearance. They are only restyled as soon as you edit them with DEVONthink.

For Calendar events dropped into rich text documents both DEVONthink and DEVONnote add a back link, too. Reminder: You could already add files and contact cards to RTFs in earlier versions. Also, version 2.8.6 adds a placeholder for the name of the top group that you can place into templates.

Of course, DEVONthink and DEVONnote 2.8.6 bring further usability enhancements as well as important bug fixes too.

Read the full news here. We recommend these free updates to all users. Get the new versions directly by using the apps’ update function or our Download page. If you purchased DEVONnote or DEVONthink Personal on the App Store, use the App Store application to update your copy.

5 Responses to “Ready for El Capitan: DEVONthink and DEVONnote 2.8.6”

  1. john maassen says:

    Thanks for the alternate menu item “Copy Page Link” – I use that a lot and this will help speed up my workflow 🙂

  2. jneumann says:

    You’re very welcome, John. Enjoy!

  3. […] after we updated DEVONthink for OS X El Capitan, here are now the maintenance updates for DEVONagent and DEVONsphere Express. They improve the […]

  4. elbs says:

    Been running the OS X El Capitan public beta & have both it and DEVONthink Pro updated to the latest versions, but have been getting crashes in DTPro where I never did before. Just giving y’all a heads-up!

  5. eboehnisch says:

    Thank you for your support. Please send bug reports and crash logs to development@devontechnologies.com.

Leave a Reply

Note: Blog comments are for commenting on a post. They are unsuitable for proper customer support, honestly. Please consider writing to our support team instead.