Skip to content

Commit 416eff1

Browse files
gamingrobotgamingrobot
committed
Change to yaml frontmatter for obsidian, combine callout shortcode
1 parent c710a49 commit 416eff1

26 files changed

Lines changed: 186 additions & 194 deletions

‎.vscode/shortcodes.code-snippets‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,8 @@
2929
},
3030
"callout": {
3131
"scope": "markdown,jinja-md",
32-
"prefix": ["call","callout","danger","info","tip","warning"],
33-
"body": ["{% ${1|info,tip,warning,danger|}() %}",
32+
"prefix": ["call","callout","danger","info","tip","warn"],
33+
"body": ["{% callout(type=\"${1|info,tip,warn,danger|}\") %}",
3434
"$2",
3535
"{% end %}"],
3636
"description": "Callout"

‎config.toml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ taxonomies = [
1414
{name = "tags", rss = false},
1515
]
1616

17+
ignored_content = ["**/.obsidian/**"] # ignore the .obsidian folder for publishing
18+
1719
[search]
1820
include_date = true
1921
index_format = "elasticlunr_json"

‎content/_index.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
+++
2-
title = "Doing Stuff"
3-
description = "A blog about stuff"
4-
paginate_by = 10
5-
sort_by = "date"
6-
+++
1+
---
2+
title: "Doing Stuff"
3+
description: "A blog about stuff"
4+
paginate_by: 10
5+
sort_by: "date"
6+
---

‎content/posts/_index.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
+++
2-
title = "Posts"
3-
sort_by = "date"
4-
template = "posts.html"
5-
transparent = true
6-
in_search_index = false
7-
insert_anchor_links = "right"
8-
[extra]
9-
hide_copyright = true
10-
+++
1+
---
2+
title: "Posts"
3+
sort_by: "date"
4+
template: "posts.html"
5+
transparent: true
6+
in_search_index: false
7+
insert_anchor_links: "right"
8+
extra:
9+
hide_copyright: true
10+
---

‎content/posts/blender-year-one/index.md‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
+++
2-
title = "Blender - Year One"
3-
description = "Stuff I made this year using Blender"
4-
date = 2025-05-19
5-
slug = "blender-year-one"
6-
[taxonomies]
7-
tags = ["Blender"]
8-
[extra]
9-
hide_toc = true
10-
cover_image = "cover.webp"
11-
+++
1+
---
2+
title: "Blender - Year One"
3+
description: "Stuff I made this year using Blender"
4+
date: 2025-05-19
5+
slug: "blender-year-one"
6+
taxonomies:
7+
tags: ["Blender"]
8+
extra:
9+
hide_toc: true
10+
cover_image: "cover.webp"
11+
---
1212

1313
{{ img(src="cover.webp", alt="" ) }}
1414

‎content/posts/c64-puzzle/index.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
1-
+++
2-
title = "Commodore 64 Puzzle"
3-
description = "A fun Commodore 64 Puzzle"
4-
date = 2020-02-27
5-
slug = "c64-puzzle"
6-
[extra]
7-
cover_image = "problem.webp"
8-
+++
1+
---
2+
title: "Commodore 64 Puzzle"
3+
description: "A fun Commodore 64 Puzzle"
4+
date: 2020-02-27
5+
slug: "c64-puzzle"
6+
extra:
7+
cover_image: "problem.webp"
8+
---
99

1010
My college professor posted this image with the question
1111

‎content/posts/ctf-innoctf-2019/index.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
1-
+++
2-
title = "InnoCTF 2019 Writeups"
3-
description = "Writeups for InnoCTF 2019"
4-
date = 2019-07-19
5-
slug = "ctf-innoctf-2019"
6-
[taxonomies]
7-
tags = ["CTF"]
8-
+++
1+
---
2+
title: "InnoCTF 2019 Writeups"
3+
description: "Writeups for InnoCTF 2019"
4+
date: 2019-07-19
5+
slug: "ctf-innoctf-2019"
6+
taxonomies:
7+
tags: ["CTF"]
8+
---
99

1010
Writeups for [InnoCTF](http://innoctf.com/) 2019
1111

‎content/posts/ctf-peactf-2019/index.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
1-
+++
2-
title = "peaCTF 2019 Writeups"
3-
description = "Writeups for peaCTF 2019"
4-
date = 2019-07-26
5-
slug = "ctf-peactf-2019"
6-
[taxonomies]
7-
tags = ["CTF"]
8-
+++
1+
---
2+
title: "peaCTF 2019 Writeups"
3+
description: "Writeups for peaCTF 2019"
4+
date: 2019-07-26
5+
slug: "ctf-peactf-2019"
6+
taxonomies:
7+
tags: ["CTF"]
8+
---
99

1010
Writeups for [peaCTF](https://peactf.com/) 2019
1111

‎content/posts/elf-shared-library-version.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
1-
+++
2-
title = "Embedding Version Info into ELF Shared Libraries"
3-
description = "How-to embed version information into an ELF binary"
4-
date = 2023-03-22
5-
slug = "elf-shared-library-version"
6-
[taxonomies]
7-
tags = ["Linux", "Code"]
8-
+++
1+
---
2+
title: "Embedding Version Info into ELF Shared Libraries"
3+
description: "How-to embed version information into an ELF binary"
4+
date: 2023-03-22
5+
slug: "elf-shared-library-version"
6+
taxonomies:
7+
tags: ["Linux", "Code"]
8+
---
99

1010
*How to embed version information into an ELF shared library?*
1111

@@ -19,7 +19,7 @@ These methods are for embedding a version into libraries distributed outside of
1919

2020
ABI version can be separate from your product/release version. If you haven't changed the ABI interface, you can keep the same ABI version while updating the product/release version on new builds. There are some great [resources](https://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html), [policy](https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html#abi.changes_allowed), and [tools](https://www.gnu.org/software/libtool/manual/libtool.html#Versioning) for how to handle ABI versioning.
2121

22-
{% info() %}
22+
{% callout(type="info") %}
2323
Symbol versioning is another way to handle ABI changes without changing the ABI version, [this blog post is all about symbol versioning](https://maskray.me/blog/2020-11-26-all-about-symbol-versioning).
2424
{% end %}
2525

@@ -75,7 +75,7 @@ static const struct version_note version = {
7575
7676
> Note sections contain a series of notes. Each note is followed by the name field (whose length is defined in `namesz`) then by the descriptor field (whose length is defined in `descsz`) and whose starting address has a 4 byte alignment. Neither field is defined in the note struct due to their arbitrary lengths.
7777
78-
{% info() %}
78+
{% callout(type="info") %}
7979
More details in the [elf manpage](https://man7.org/linux/man-pages/man5/elf.5.html) under the `Notes (Nhdr)` section.
8080
{% end %}
8181

‎content/posts/floating-point-hell.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
1-
+++
2-
title = "Floating Point Hell"
3-
description = "Did you know JavaScript uses floats for all numbers?"
4-
date = 2014-03-16
5-
slug = "floating-point-hell"
6-
[taxonomies]
7-
tags = ["Code"]
8-
[extra]
9-
hide_toc = true
10-
+++
1+
---
2+
title: "Floating Point Hell"
3+
description: "Did you know JavaScript uses floats for all numbers?"
4+
date: 2014-03-16
5+
slug: "floating-point-hell"
6+
taxonomies:
7+
tags: ["Code"]
8+
extra:
9+
hide_toc: true
10+
---
1111

1212
This blog post will show how to deal with floating-point error in JavaScript by encoding all uint64's, and int64's as strings in JSON Marshaling.
1313

0 commit comments

Comments
 (0)