Skip to content

Releases: Edditoria/markdown-plus-plus

v3.4.0

23 Aug 20:34
bad918e
Compare
Choose a tag to compare

Key Changes

  • Feature 🆕 Add support of "Dark Mode" in Notepad++.

Please use the new command switch to get a dark mode UDL, e.g. mpp obsidian --dark.

May the force be... Welcome to the dark side. 😈

v3.3.0

20 Mar 09:10
Compare
Choose a tag to compare
  • Feature: 🆕 Add goodies.extraProtocols in config, e.g. "ssh://", "bitcoin:". Please rise an issue if some protocols should be added by default.
  • Feature: 🆕 Highlight ../ as link.
  • Improve: npx markdown-plus-plus --help will also print the themes available in the repo, so users don't need to fetch the npm package twice.
  • Change: Rename config option: goodies.hex ➡️ goodies.highlightHex.
  • Change: Rename config option: header.fgColor ➡️ heading.fgColor.

📝 Note:

  • goodies.hex and header.fgColor are still supported currently, but it will trigger a log message "depreciated" in console.
  • This version focuses on existing code. There is no change in final output, i.e. the files in <udl\> directory.

v3.2.0

24 Oct 10:25
Compare
Choose a tag to compare
  • Themes: Twilight (official theme) and Material (community theme). 🆕
  • Improve: Table syntax in Github Flavored Markdown.
  • New Feature: GFM is now an option in each config. Start with gtm.table (default: true). 🆕

Also thanks to the awesome Material theme repo: Material Theme for Notepad++

v3.1.0

27 Apr 14:02
Compare
Choose a tag to compare
  • Themes: Bespin and Obsidian. 🆕
  • Security: Fixed via updating npm dependency.

v3.0.0

13 Mar 10:50
Compare
Choose a tag to compare

Breaking Changes

  • This repo is now a npm package. Simply run npm install for development.
  • Users can make use of npx to fetch (download) UDL files in command line. If you have Node.js installed, try to run for details: npx markdown-plus-plus --help.
  • Use Handlebars.js instead of Mustache.js for further improvement in future.
  • Options, in config files, are being organized in 3 categories:
    1. GitHub Flavored Markdown (not implemented yet, but later).
    2. Goodies: Eye candy highlighting. Not standard markdown syntax.
    3. Flags: Danger zone that has side-effect, and for experimental purpose.

Comparing v3.0.0 to v2.2.0, there is no change on the build output, i.e. the UDL XML files. However, please expect there will be some change breaking backward compatibility.

v2.2.0

23 Jan 07:10
Compare
Choose a tag to compare

Add support of 2 themes: Solarized (dark), and Solarized-light

In these 2 color schemes, I follow the Solarized guideline. For <em> and <strong> syntax, I use the color similar to normal text. I aim to pick different color in other themes because of display problem in some fonts or some Windows system. This is still a test to see your comments.

Happy 2019

v2.1.0

21 Dec 14:18
Compare
Choose a tag to compare

Begin to support GitHub Flavored Markdown. Start with:

Options via build script:

  • New: Option to make the text background becoming transparent. So, you can build a theme using existing color scheme for different theme. Thanks @andrewhu-uw .
  • New: Option to highlight HEX value, e.g. 0x123ABC. Not Markdown, only for eye candy. Thanks again @RaffaeleMorganti .

Minor:

  • Improve: Add \~ \> \< highlighting.
  • Improve: Syntax keyword is no longer case sensitive.

v2.0.0

30 Nov 11:46
Compare
Choose a tag to compare

Breaking changes for users:

  • Introduce new highlighting mechanism: "modern" build that is trying to highlight *multiple <em> words*
  • The old version is kept as "classic" build for users who write * Asterisk-style bullet points
  • Better folder and file naming conventions; Easier to identify theme name and build type

That is: 2 builds for each theme.

For developers (forkers):

  • "master" branch becomes "classic" build; "v2.0-beta" branch becomes "modern" build
  • build.sh script can generate 2 UDL-XML files at once
  • adapts UDL 2.1 in coming updates (may break in old Notepad++ versions)
  • use "semantic versioning"
  • use hyphen rather than underscore; use tab rather than space (sorry for changes 😟)
  • organize files and directories to keep consistent in future