.RECIPEPREFIX := |
.DEFAULT_GOAL := tangle
# Adapted From: https://www.systutorials.com/how-to-get-the-full-path-and-directory-of-a-makefile-itself/
mkfilePath := $(abspath $(lastword $(MAKEFILE_LIST)))
mkfileDir := $(dir $(mkfilePath))
emkDir := $(mkfileDir)/.emacs.d/
emkFile := $(emkDir)/makefile
emkMake := make -f $(emkFile)
README:
|git tangle $(mkfileDir)/README.org
tangle: README
|git tangle $(mkfileDir)/oreo.aiern.org
tangle-emacs:
|$(emkMake) tangle
tangle-all: tangle tangle-emacs
emacs:
|$(emkMake) emacs
emacs-nw:
|$(emkMake) emacs-nwMy pride and joy; based off of Andrew Moffat’s sh, this python module allows you to import shell commands as modules as well. For example:
<<20210601181755824433500>>
<<20210601181800630609300>>
<<20210601181804730771100>>You might be thinking to yourself, “Cool!” And also, “…Wait what?”
from baker.y import gitThis will import the git utility from your path as a bakery object;
note, however, that while the statement is importing git from baker.y,
there are actually two submodules in play here: baker with a y,
and baker with an i.
To facilitate the use of git(C = [path]).status(), the latter submodule must be used.
This also prevents the use of something like git(), but, since that just shows the help text,
one can simply use git.help() instead.
git.clone(
b = "master",
recurse_submodule = True,
"https://github.com/<<username>>/<<username>>",
"~/<<username>>",
_run = True,
)print(git(C = "~/<<username>>").status())Get it here! https://gitlab.com/picotech/bakery
Also: eh heh heh… yeah… I like gitlab's grouping system… /sheepish grin/