I thought I was being clever by making a "print statement" in javascript (yes, I miss python 2's print statement, and BASIC too)
print `${attacker} attacks ${defender} for ${damage} hp.`;
But it turns out Mozilla's docs have this same idea developer.mozilla.org/en-US/docs/W...
console.log`Hello`;
developer.mozilla.org
Template literals (Template strings) - JavaScript | MDN
Template literals are literals delimited with backtick (`) characters, allowing for multi-line strings, string interpolation with embedded expressions, and special constructs called tagged templates.
![### HTTP responses have:
- a status code (200 OK! 404 not found!)
- headers
- a body (HTML, an image, JSON, etc)
### Here's the HTTP response from `examplecat.com/cat.txt`:
```
HTTP/1.1 200 OK
status
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Content-Length: 33
Content-Type: text/plain; charset=UTF-8 Date: Mon, 09 Sep 2019 01:57:35 GMT
Etag: "ac5affa59f554a1440043537ae973790-ssl"
Strict-Transport-Security: max-age=31536000
Age: 0
Server: Netlify
[ASCII image of a cat, labelled "cat!" with a smiley face]
```
The first line, `HTTP/1.1 200 OK` is the status code. "200" is the status.
The lines from `Accept-Ranges` to `Server` are the headers.
The cat picture is the body.
### There are a few kinds of response headers:
- when the resource was sent/modified:
```
Date: Mon, 09 Sep 2019 01:57:35 GMT
Last-Modified: 3 Feb 2017 13:00:00 GMT
```
- about the response body:
```
Content-Language: en-US
Content-Length: 33
Content-Type: text/plain; charset=UTF-8
Content-Encoding: g](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:ygxqgtpypjuaf2b3oyrdn44x/bafkreiddcdprzhtnwxvofkmdifyesdu2jfvdweyyosp6heqe6wnnx3ylx4)
![### our hero: `set -x`
`set -x` prints out every line of a script as it executes, with all the variables
expanded!
`#!/bin/bash
set -x`
(I usually put `set -x` at the top)
### or `bash -X`
`$ bash -x script.sh` does the same thing as putting `set -x` at the top of `script.sh`
### you can stop before every line
`trap read DEBUG`\
the `DEBUG` "signal" is triggered before every line of code
### a fancy step debugger trick
put this at the start of your script to confirm every line before it runs:
`trap '(read -p "\[$BASH_SOURCE: $LINENO] $BASH_COMMAND")' DEBUG`
- `read -p` prints a message, press enter to continue
- `$BASH_SOURCE` is the script filename
- `$LINENO` is the line number
- `$BASH_COMMAND` is the next command that will run
### how to print better error messages
this die function:
`die() { echo $1 >&2; exit 1; }` lets you exit the program and print a message if a command fails, like this:
`some_command || die "oh no!"`](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:ygxqgtpypjuaf2b3oyrdn44x/bafkreigtmjo6ogs6rsyw5ldhsrzblsgztaf3vxd6ntbtw2x22oruobahii)
