> replacing the <ol> with a <ul> and parsing the ref from the [^definition]:?

This can work 👀

edit: hey a bug! inline code in block quotes is ignored lol

Yeah that's a behavior change from before, doesn't have to be a bug per se.

 and correspond to the numbered list in the footer as

the only issue right now is that a displayed 

 corresponds to item 1 in the list, except there is no way to tell other than by the 

Edit: perhaps not parsing non-numericals (and forcing us to order them manually) is the easy solution, or the hard mode otherwise, replacing the 

Stacker Saloon

saloon

Yeah that's a behavior change from before, doesn't have to be a bug per se.

`[^😭][^a][^4][^3]` would previously display as `[1][2][3][4]` and correspond to the numbered list in the footer as 

```
----
1. ...
2. ...
3. ...
4. ...
```

the only issue right now is that a displayed `[😭]` corresponds to item 1 in the list, except there is no way to tell other than by the `#fn-<x>` and `#fnrev-<x>` in the urls.

Edit: perhaps not parsing non-numericals (and forcing us to order them manually) is the easy solution, or the hard mode otherwise, replacing the `<ol>` with a `<ul>` and parsing the ref from the `[^definition]:`?