- I wanted to do something in rust since it has a reputation for being hard.
- I had a pile of HTML from my google+ to convert to hugo-friendly Markdown.
It processes command line arguments and verifies that the directories are there and laid out as expected. Then it finds the HTML files in the first directory.
Be careful about saying stuff like:
This code was written by human hands using
vim
without performance enhancing drugs or AI coding assistance. If you're into those things, you be you. But at this point in my life I'd rather see how well I can do naturally. I feel confidant that I'm learning more this way.
because you might eventually get lazy enough to give into the AI as a way to get things done. C'est la vie. Never say never.
At least I'm still editing with vim
.
cargo run -- $GOOGLE_PLUS_DUMP_DIR $MARKDOWN_DEST_DIR
It takes two arguments:
- The directory of the Google+ dump aka "Takeout". It needs to contain the
Google+ Stream/Posts
directory structure. - The directory where you want the Markdown files created.
Check out casey/just if you haven't heard of
just
yet.
You can see in the justfile
how I've been using it to build this
project on my machine. Running just
without arguments will run the try
stanza which processes the examples/
directory and outputs to test_output/
.
The project includes:
examples/
- Sample Google+ HTML files for testing the parsertest_output/
- Generated Markdown files (gitignored)
Other named recipes are:
check
- run rust linters locallynewdep crate_name
- add a new create dependancysync
- get out of a branch after mergingbacktrace
- run with detailed error traces
So just check
would rerun the linters for you.
I'm still new to just
, but it has been helpful while developing this
project. I'm working on a blog post or youtube video about my happy
experience with just
.