github Feel-ix-343/markdown-oxide v0.22.0

latest releases: v0.23.2, v0.23.1, v0.23.0...
3 months ago

Notes on this release and a status update below

Discussion: #134

What's Changed

  • feat: support for cargo binstall by @KSaiAkshit in #58
  • Define PKM in the readme (hah) @jlin in #69
  • Use LSP commands to open/create daily notes (by the format either imported from your obsidian settings or in the config you provide). There is now Today, Tomorrow, Yesterday, and Daily {natural language} (Daily three days ago). You may have to modify your editor config; check the README -- and I have only tested this on Neovim: @Kxnr and @Feel-ix-343 in #85
  • Add option to set the folder to create daily notes @Feel-ix-343 and @SpyrosMourelatos in #111
  • Configure whether to add a .md extension to markdown and wikilink completions; this also modifies the parser to parse links with this: by @RyanGreenup and @Feel-ix-343 in #114
  • Add config options for respecting/ignorice character case in fuzzy matching: Smart, Ignore, Respect.
  • updated the tag parsing, it should be more aligned with common mark spec now

All of these features should be fully documented in the README.

New Contributors

Full Changelog: v0.0.21...v0.22.0

Status

I have been vacationing for the past month as my school year has ended, but now and for the next couple months at least I am working on this primarily (while also diving deeper into category theory and haskell!).

in this time period, there are three main things I will be working on.

  1. Refining the current features and version: there are several odd behaviors and bugs in markdown oxide. This does not stop me from using it daily, but some things are just clunky and I want to fix them.
  2. A new major version: the code for markdown oxide was written in an attempt to get a product (that I could use) developed, and therefore, it is quite crap. It is confusing for new contributors and difficult to extend for new features. To remedy this, I am rewriting a significant amount of the code -- considering maintainability, simplicity, and creating a foundation for new features. After that, some new major features will be implemented -- possibly including integration with Obsidian.nvim, semantic search powered link completions, adding filters to link queries, Obsidian code block queries, transclusion, ...
  3. Adding features to the current version: the rewrite will take some time, and there is functionality that I want out of this PKM sooner rather than later. Yes, these will probably have to be rewritten, but it is what it is.

If you have thoughts on these items, let me know in an associated discussion. Also feel free to describe your experience using this PKM: some of your struggles, things you appreciate about it, and comparisons to other PKMs you've used.

Don't miss a new markdown-oxide release

NewReleases is sending notifications on new releases.