Iron(III) Oxide

is there any way to make it more concise? PJ pointed out `clap::Arg::parse_values()` but it's not obvious how or if this could simplify our code.

> This seems unnecessary the code is currently messy and hard to find around. Refactoring makes it easier for newcomers like myself to find a specific item in a long...

Imagine having a dictionary where the words are just put there in random order. It would be kinda hard to get an overview of what's available when learning the codebase

> but this is not a dictionary, it's a codebase, which you can easily ctrl+f or go by reference/symbol if I know the name of the item, then I can...

> Then you can read? Still it doesn't require everything to be sorted yeah I can read, but I think that having it sorted makes it easier for me to...

this refactoring also sorts items by how many arguments they take in. Let's suppose I'm looking for an item that takes 3 arguments as input. I have them all in...

> this just sorts everything and adds noise in git log, the noise in git log can be solved by git rebase, where you merge this commit into one of...

> How should this work and what should mdbook watch do differently than mdbook build? It was a while ago, but let's imagine this scenario: you have built a book....

I think it was mostly a minor issue. I don't remember all the details and it was a while ago. Let's close it for now. If someone else encounters this...

> You do remember correctly smile I'm just a user of mdbook and in my experience, it only takes a few seconds to rebuild the book. ok let's fix that...