diff --git a/2024/inso/build.ninja b/2024/inso/build.ninja index 21e6819..965ad62 100644 --- a/2024/inso/build.ninja +++ b/2024/inso/build.ninja @@ -2,7 +2,7 @@ builddir = build pandocflags = -M wf-embed-base=https://git.lain.faith/haskal/writeups/raw/branch/main/ -M wf-link-base=https://git.lain.faith/haskal/writeups/src/branch/main/ --filter writefreely-validate --wrap=none --strip-comments -postid = temp +postid = ckzulowi2i rule pandoc command = pandoc $pandocflags -o $out $in diff --git a/2024/inso/post.md b/2024/inso/post.md index 00265bc..8b81b24 100644 --- a/2024/inso/post.md +++ b/2024/inso/post.md @@ -368,7 +368,7 @@ so i opened up the man page for bash..........and then i immediately gave up and @rhelmot whether there was any cheese with bash environment variables you could do, and she offered up `BASH_ENV` -``` +```text BASH_ENV If this parameter is set when bash is executing a shell script, its value is interpreted as a filename containing commands to initialize the shell, as in ~/.bashrc. The value of BASH_ENV @@ -629,7 +629,7 @@ needed to gain code execution. notice that `pts.txt` is in the `quizzes` directo allowed input because it's 7 chars and only uses allowed characters. what happens if we try to run the quiz `pts.txt`? -``` +```bash $ make username=user quizz=pts.txt pts.txt:1:1: error: expected ‘,’ or ‘;’ at end of input 1 | user = {1,2,3,4,5,6,1} @@ -665,7 +665,7 @@ this actually compiles, and interestingly enough just `main = { .... };` still c run because `main` gets put in `.data` which is not normally executable. hence the `const` in the above example. that actually causes main to get put in `.rodata` -``` +```bash gcc -x c -w - <