Any time I cause my venv to be rebuilt, I need to remember to do this, and I
always have to search my shell history to remind myself what the command is.
That feels like it deserves to go into the Makefile.
Simply adds `make setup` as a shorthand for running the poetry command that
does the initial install for local development, and also `make update` to do
a package update. Simply aimed as handy extras for development.
This one's a little vague right now, and I'm not sure how best to test this.
Looking at the mkdocs documentation it isn't clear to me that you *can*
provide the config file to the gh-build command, but there's example command
lines in the docs showing that you can.
Need to see if there's a safe way to test this out -- the last thing I want
to do is nuke our website.
The idea here is that there is a single file for the nav for all the docs,
both online and offline. The nav will be the full online nav in all its blog
glory, and then the build system will strip out the nav items relating to
the blog when building the offline version.
There's a wrinkle or two still in here; the main one being that when doing a
docs-serve, it seems that the cleaning up of the online nav doesn't happen
when you Ctrl-C out of the server. I'm not 100% sure of the cause of
this (there could be a couple of different reasons).
For now... I'm ensuring that the online/offline nav files are excluded from
git. It would be nice to find out how best to always ensure that the online
nav file is removed so nobody attempting to update the docs gets confused
about what to edit.
It's a `Makefile` so it's handy to not have to think about if you need to be
within a poetry venv when running `make`. This commit adds a `poetry run`
before any command that needs the venv. This means that people who aren't in
a venv can just `make something` and it'll "just work", and the same is true
for those who are in a venv.
This removes the duplication of the screen cache cleaning, and also turns it
into a target so you can do it yourself from the command line if needed. It
also marks all the phony targets as such (that is, targets that aren't
actually items in the filesystem).
This will build the docs into a directory called docs-local, sans the blog.
Note the near-total copy/paste of the `nav` due to how mydocs does
configuration inheritance; this is fine for now.
* Register callbacks at message pump level, invoke them after refresh
* Fix a typo
* Code review feedback actions
* call_later callbacks invoked after refresh or on idle
* Fix space key in text input
* Make Widget.on_idle synchronous
* Fix call_later
* Rename PostScreenUpdate to InvokeCallbacks, and only fire if callbacks exist
* Update type hints for InvokeLater callbacks
* Update type signature of call_later callbacks, extract typevar
