From f6a71fe353cd2b229738559b90afbe1c67deaf90 Mon Sep 17 00:00:00 2001 From: Simon Petit Date: Thu, 14 Nov 2024 16:05:52 +0100 Subject: [PATCH] test --- .drone.yml | 2 +- .../awk_for_static_site_generation.md | 20 ++++++++--------- posts/awk_for_static_site_generation.html | 22 +++++++++---------- 3 files changed, 22 insertions(+), 22 deletions(-) diff --git a/.drone.yml b/.drone.yml index 9021162..e5f494c 100644 --- a/.drone.yml +++ b/.drone.yml @@ -15,4 +15,4 @@ steps: target: /var/www/html/blog/ source: - index.html - - posts/*.html + - posts diff --git a/drafts/published/awk_for_static_site_generation.md b/drafts/published/awk_for_static_site_generation.md index a877f44..2305c5b 100644 --- a/drafts/published/awk_for_static_site_generation.md +++ b/drafts/published/awk_for_static_site_generation.md @@ -23,18 +23,18 @@ AWK works as follow : it takes an optional regex and execute some code between b For example : /^#/ { - print "

" $0 "

" + print "<h1>" $0 "</h1>" } Although `$n` refers to the n-th records in the line (according to a delimiter, like in a csv), the special `$0` refers to the whole line. -In this case, for each line starting with `#`, awk will print (to the standard output), `

[content of the line]

`. +In this case, for each line starting with `#`, awk will print (to the standard output), `<h1> [content of the line] </h1>`. This is the beginning to parse headers in markdown. However, by trying this, we immediatly see that `#` is part of the whole line, hence it also appear in the html whereas it sould not. AWK has a way to prevent this, as it is a complete scripting language, with built-in functions, that enable further manipulations. `substr` acts as its name indicates, it return a substring of its argument. /^#/ { - print "

" substr($0, 3) "

" + print "<h1>" substr($0, 3) "</h1>" } In the example above, as per the [documentation](https://www.gnu.org/software/gawk/manual/html_node/String-Functions.html#index-substr_0028_0029-function) @@ -46,11 +46,11 @@ and allows the script to dynamically determine which depth of header it parses : /^#+ / { match($0, /#+ /); n = RLENGTH; - print "" substr($0, n + 1) "" + print "<h" n-1 ">" substr($0, n + 1) "</h" n-1 ">" } Reproducing this technique to parse the rest proves to be difficult, as lists for example, are not contained in a single line, hence -how to know when to close it with `` or `` +how to know when to close it with `</ul>` or `</ol>` ## Introducing a LIFO stack @@ -82,7 +82,7 @@ Turns out it came out to be easy, I only needed a pointer to track the size of t } The stack does not have to be strictly declared. The value of inside the LIFO correspond to the current markdown environment. -This is a clever trick, because when I need to close an html tag, I use the poped element between a `` instead of having a matching table. +This is a clever trick, because when I need to close an html tag, I use the poped element between a `</` and a `>` instead of having a matching table. I also used a simple `last()` function to return the last pushed value in the stack without popping it out : @@ -99,11 +99,11 @@ This way, parsing lists became trivial : env = last() if (env == "ul" ) { # In a unordered list block, print a new item - print "
  • " substr($0, 3) "
    • " + print "<li>" substr($0, 3) "</li>" } else { # Otherwise, init the unordered list block push("ul") - print "` or ``

    +

    how to know when to close it with `</ul>` or `</ol>`

    Introducing a LIFO stack

    Since according to the markown syntax, it is possible to have nested blocks such as headers and lists withing blockquotes, or lists withing lists, I came with the simple idea to track to current environnement in a stack in AWK.

    Turns out it came out to be easy, I only needed a pointer to track the size of the lifo, a fonction to push an element, an another one to pop one out :

    @@ -88,7 +88,7 @@ function pop() {

    The stack does not have to be strictly declared. The value of inside the LIFO correspond to the current markdown environment.

    -

    This is a clever trick, because when I need to close an html tag, I use the poped element between a `` instead of having a matching table.

    +

    This is a clever trick, because when I need to close an html tag, I use the poped element between a `</` and a `>` instead of having a matching table.

    I also used a simple `last()` function to return the last pushed value in the stack without popping it out :

    # Function to get last value in LIFO
 function last() {
@@ -102,12 +102,12 @@ function last() {
     env = last()
     if (env == "ul" ) {
         # In a unordered list block, print a new item 
-        print "
  • " substr($0, 3) "
    • " 
+        print "<li>" substr($0, 3) "</li>" 
     } else {
         # Otherwise, init the unordered list block 
         push("ul")
-        print "