- Scale mathjax output font size (trying to address #63)
- in
package.jsonchange version requirement for git-utils - in
lib/mathjax-helper.coffeechange config option for the SVG output processor so it fits what's given in the official mathjax doc
- Trying to fix issue #68
- Trying to fix issue #72
- openConfig button in EVND panel now opens specific config page of EVND package
- license year update
- Added some shields.io badges to README
- More proper warning when designated notebook does not exist
- Trying to fix issue #43
- Trying to fix issue #34
- Trying to fix issue #16
- Trying to fix issue #26
- Update July 2016: apparently this bug is not completely fixed yet!
- Temporarily addressing issue #21
- explicitly set default text color to black
- Trying to fix issue #23 and possibly #20 ?
- Steps to take:
- Option 1:.Remove the package
ever-notedownand do a clean re-install - Option 2. :
- Update
ever-notedown - In command line,
cd ~/.atom/packages/ever-notedown/ - Run
apm clean - Run
apm install
- Update
- Option 1:.Remove the package
- Steps to take:
- Fixed #19
- Merged pull-request #12 : Removed window message for successful operations
- Moving away from
window.alerttoatom.notifications - Revert commit 4c26b53 because the fix was problematic. See #11 for details.
- Trying to fix issue #9 ("Syntax error, unrecognized expression" when html element id contains special characters)
- Fixed the confusion when two notes created on different days happen to have the same file name
- Fixed a typo (side panel)
- Footnote rendering
- (Attempted) to fix issue #7
- First step in fixing issue #4
- Not sure about this...
- (Attempted) to fix issue #3
- A rather basic patch... the functionality of writing notes in plain text or html is barely there and lacks testing
- Minor documentation updates (help document, notes for developers)
- Added CHANGELOG
- package.json now requires a newer version of Atom
- (Attempted) to fix issue #2
- Picking up some updates from markdown-preview
- Resolve deprecations for Atom 1.0 API
- Minor code clean-up
- Minor documentation update
- (Attempted) to fix issue #1
- Release