NOT from the devs
aka Loupau's understanding of blueprint codes
Last updated : 0.1.0-pre8-rc1
To sart, a blueprint code is structured as follows :
prefix + separator + version + separator + blueprint + suffix
\colorbox
and \fcolorbox
are broken and Github did't talk about if it's a temporary thing or if it will not be added back.
#
's)
As you can se with the above message(s) Tex may not be very stable and may not be an option to you as of the dates expressed above. You can also check other tex problems here.
Based on https://www.gnu.org/software/make/manual/html_node/Quick-Reference.html
Directive | Description |
---|---|
define variable define variable = define variable := define variable ::= define variable += define variable ?= endef |
Define multi-line variables. |
undefine variable |
Undefining variables. |
#!/usr/bin/env bash | |
# | |
# Wraps curl with a custom-drawn progress bar. Use it just like curl: | |
# | |
# $ curl-progress -O http://example.com/file.tar.gz | |
# $ curl-progress http://example.com/file.tar.gz > file.tar.gz | |
# | |
# All arguments to the program are passed directly to curl. Define your | |
# custom progress bar in the `print_progress` function. | |
# |