d.awk
dayone-json-to-obsidian
d.awk | dayone-json-to-obsidian | |
---|---|---|
1 | 2 | |
85 | 19 | |
- | - | |
3.2 | 0.0 | |
about 1 year ago | over 1 year ago | |
Awk | Awk | |
MIT No Attribution | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
d.awk
-
Markdeep
If you'll indulge me for a moment, I have a story to tell:
Many years ago, I had this idea of creating a documentation tool for my hobby projects that was based on Awk.
I liked Doxygen, but it was a bit heavy duty for a small C library with only a handful of functions. You could almost guarantee that Awk would be available on the system where you might be compiling the project, so you could just bundle the awk script with your sources, add two lines to your makefile and have HTML documentation ready to go.
Now I had never heard of Markdown at this time; It was before StackOverflow or GitHub was a thing (perhaps they existed, but I haven't used them yet). Therefore my syntax was a crude markup scheme that was difficult to explain and didn't always work correctly.
Skip forward a couple of years and I had the bright idea to rewrite the script to rather use a Markdown syntax. This ended up being one of those hobby projects that you never really finish, and it grew organically to include all sorts of Markdown features. The result of that effort is now on GitHub [1].
Where does Markdeep fit into all of this? Sometimes when I stumble upon a project on GitHub that I find interesting, I click on the author's name to see what other repositories they have that looks interesting. One day I browsed GitHub like that and stumbled upon user r-lyeh's `stddoc.c` file [2].
It is a C program that simply extracts the comments from your source file and appends the Markdeep tags to the end. If you save the result to a HTML file, you achieve the same result as my script, except the implementation is much much simpler.
I nearly fell off my chair when I realised that all the effort I put into my own script was basically made useless(*) by Markdeep. Instead of parsing the markdown, I could rather have had Markdeep do all the heavy lifting, and it comes with a bunch of very nice features that I doubt I'd ever be able to implement in my own script.
[1]: https://github.com/wernsey/d.awk
dayone-json-to-obsidian
What are some alternatives?
awkdoc - Shell documentation generation from comment annotations.
jp - Validate and transform JSON with Bash
catless - cat and less in one program
boost - Get started right. Become a shell native. This is the way.
advent_of_code_2022 - Advent of Code 2022 solutions in Awk
stddoc.c - Tiny documentation generator for 60 programming languages. Using Markdeep.
git-repo-sync - Auto synchronization of remote Git repositories. Auto conflict solving. Network fail resilience. Linux & Windows support. And more.
gitlcd - Turn your Github contribution board into a simple LCD panel
jello - CLI tool to filter JSON and JSON Lines data with Python syntax. (Similar to jq)
reference - ⭕ Share quick reference cheat sheet for developers.