@screwlisp wrote:
> I've had the idea that the loved-and-hated #commonLisp #formattedOutput is basically markdown

Again, I'd rather draw a (partial) similarity between Common Lisp's format language
and extended Backus-Naur (or Normal) form (EBNF).
Note also the common root of the two F-words.
It must be intentional; probably this has already been said.

Some format directives are analogous to lexical tokens
(as are almost all `printf' directives), of course.

@publicvoit @ramin_hal9001 @sacha

I've had the idea that the loved-and-hated #commonLisp #formattedOutput is basically markdown except all control characters are escaped using ~, and instead of repeating the control characters for different levels, Common lisp's formatted output takes parameters between the ~ and control character.

@publicvoit @ramin_hal9001 @sacha

#commonLisp #formattedOutput annotated examples and #programming #tutorial .
I use format a lot in my #lisp codes, so to ameliorate the this-looks-crazy feelings common lisp formatted output induces, I wrote this #printing #medium #article :

https://medium.com/@screwlisp/introductory-then-crazy-lisp-format-examples-446940b6d746

I'm also trying out directly sharing #emacs #orgmode markdown blocks, since Medium hasn't achieved common lisp syntax highlighting yet.

Introductory then Crazy LISP format examples - screwlisp - Medium

Common Lisp’s pretty printing is featurose. Ad hoc pretty-printing comes in the form of format, which is way fancier than C’s printf(3). Not-enough-arguments is an error, unused extra arguments are…

Medium
#CommonLisp #FormattedOutput
those feelings when
(format t "~@v,,,' a" '7 'padded)