Autosave: 2024-06-16 18:45:04

README.md

@@ -14,7 +14,7 @@ computer science.
 It is a [Zettelkasten](https://en.wikipedia.org/wiki/Zettelkasten) work in
 progress. I've recently converted the topic-based subdirectories into a single
 flat directory structure organised by tags. I'm in the process of partitioning
-longer notes into smaller informational units.
+longer notes into smaller units.
 
 I use the [zk](https://github.com/zk-org/zk) CLI package to help with indexing
 and task automation alongside its [zk-nvim](https://github.com/zk-org/zk-nvim)
@@ -22,48 +22,8 @@ Neovim wrapper. I occassionally utilise [Obsidian](https://obsidian.md/)
 alongside Neovim for when I want to view my notes as a knowledge graph or read
 them alongside their rich content (images, videos etc).
 
-## Commands
-
-Commands are local to my Linux machine, specified in my
-[dotfiles](https://github.com/thomasabishop/dotfiles). They are how I generate
-new entries and manage the knowledge base.
-
-| Alias          | Command                | Output                                                                                                                       |
-| -------------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
-| `z`            | `cd $HOME/repos/eolas` | Access Zettelkasten                                                                                                          |
-| `zn`           | `zk new --title ...`   | Create new entry from template                                                                                               |
-| `<leader> zk`  | `:ZkNotes`             | Access Zettelkasten from anywhere within `nvim`                                                                              |
-| `<leader> zi`  | `:ZkIndex`             | Index Zettelkasten within `nvim`                                                                                             |
-| `<leader> zt`  | `:ZkTags`              | View tags via [Telescope](https://github.com/nvim-telescope/telescope.nvim) within `nvim`                                    |
-| `<leader> ztt` | `:ObsidianTags`        | View tags in a Vim buffer via within `nvim` using [obsidian-nvim](https://github.com/epwalsh/obsidian.nvim)                  |
-| `<leader> zl`  | `:ZkLinks`             | View links in current entry via Telescope within `nvim`, using [obsidian-nvim](https://github.com/epwalsh/obsidian.nvim)     |
-| `<leader> zb`  | `:ZkBacklinks`         | View backlinks to current entry via Telescope within `nvim`, using [obsidian-nvim](https://github.com/epwalsh/obsidian.nvim) |
-
-## Frontmatter
-
-When I run the `zn` command this generates a new Zettelkasten entry with the
-following frontmatter template:
-
-```yaml
----
-id: o8yzcrtv
-title: test
-tags: []
-created: Saturday, February 17, 2024 | 17:44
----
-```
-
 ## Scripts
 
 The [scripts](/scripts) directory contains several Bash and Python scripts I use
 for general housekeeping, such as formatting image URLs, removing unused assets,
 and autosaving.
-
-## Autosave
-
-I use a [bash script](./scripts/auto_save.sh) to create autosave functionality
-via Git. This script runs every 15 minutes via a
-[systemd time](https://github.com/thomasabishop/dotfiles/tree/master/systemd/zettelkasten_autosave)
-timer. It tidies up the directory (removes unused images, ensures all file names
-use underscores rather than spaces and hyphens etc) and commits and pushes to
-GitHub.

zk/2_POST.md

@@ -62,7 +62,7 @@ client.
 
 We should accept alterations to the database that are not first validated. We
 can use the
-[Joi validator](Validation.md) to vet
+[Joi validator](Validation_in_NodeJS.md) to vet
 the request:
 
 ```js

zk/CPU_architecture.md

@@ -1,7 +1,6 @@
 ---
 tags:
   - CPU
-  - clock
   - computer-architecture
 ---
 

zk/Circuits.md

@@ -1,7 +1,6 @@
 ---
 tags:
   - electricity
-  - circuits
   - electronics
 ---
 

zk/Clock_signals.md

@@ -2,7 +2,6 @@
 tags:
   - binary
   - memory
-  - clock
   - electromagnetism
   - hardware
 ---

zk/Expansions_and_substitutions.md

@@ -79,7 +79,7 @@ the second list against them.
 ## Parameter expansion: `${...}`
 
 We use most frequently for returning the value of stored
-[variables](Variables_and_data_types.md).
+[variables](Variables_and_data_types_in_Bash.md).
 Techically we do not have to use the braces, we can retrieve with just `$var`
 however it's better to use them to minimise interpretation fuck-ups which happen
 a lot.

zk/Flip_flops.md

@@ -1,5 +1,8 @@
 ---
-tags: [logic-gates, binary, memory, clock]
+tags:
+  - logic-gates
+  - binary
+  - memory
 ---
 
 # Flip-Flops

zk/Monitoring_processes_and_resources.md

@@ -61,7 +61,7 @@ _Here I have pressed `u` to show only the processes associated with my user:_
     ```
 - `VIRT`
   - The total amount of
-    [virtual memory](Virtual_memory_and_the_MMU.md) used by
+    [virtual memory](Virtual_memory_and_the_MMU_in_Linux.md) used by
     the process including: program code, data, shared libraries, pages that have
     been swapped, pages that have been mapped but not used.
 - `RES`
@@ -69,7 +69,7 @@ _Here I have pressed `u` to show only the processes associated with my user:_
   - The non swapped _physical_ memory the process has used
 - `SHR`
   - The size of the process's
-    [shared pages](Virtual_memory_and_the_MMU.md#shared-pages)
+    [shared pages](Virtual_memory_and_the_MMU_in_Linux.md#shared-pages)
 - `S`
   - Status:
     - S for sleeping (idle)
@@ -168,7 +168,7 @@ $ uptime
 
 We know that processes primarily interact with virtual memory in the form of
 pages which are then translated to physical blocks by the kernel via the
-[MMU](Virtual_memory_and_the_MMU.md). There are several tools
+[MMU](Virtual_memory_and_the_MMU_in_Linux.md). There are several tools
 which provide windows onto this process.
 
 ### System page size

zk/The_kernel.md

@@ -64,7 +64,7 @@ It has the following jobs to manage:
 - Allowing for the use of disk space as auxiliary memory
 
 > Modern CPUs include a
-> [memory management unit](Virtual_memory_and_the_MMU.md#the-memory-management-unit-mmu)
+> [memory management unit](Virtual_memory_and_the_MMU_in_Linux.md#the-memory-management-unit-mmu)
 > which provides the kernel with **virtual** memory. In this scenario, memory
 > isn't directly accessed by the process instead it works on the assumption that
 > is has access to the entire memory of the machine and this is then translated

zk/Three_bit_counter.md

@@ -1,5 +1,8 @@
 ---
-tags: [logic-gates, binary, memory, clock]
+tags:
+  - logic-gates
+  - binary
+  - memory
 ---
 
 # 3-bit Counter

zk/User_Space.md

@@ -1,5 +1,6 @@
 ---
 tags:
+  - operating-systems
 ---
 
 # User space

zk/User_management_in_Linux.md

@@ -1,5 +1,7 @@
 ---
-tags: []
+tags:
+  - Linux
+  - procedural
 ---
 
 # User management

zk/Using_env_vars.md

@@ -1 +0,0 @@
-// Add notes on using env vars locally and in prod

zk/Validating_Mongoose_schemas.md

@@ -31,7 +31,7 @@ the property of `required` for a cell in the table. If we didn't set any
 validation via Mongoose, Mongo would accept whatever we sent to it.
 
 What is the relationship between this Mongoose validation and the
-[Joi](Validation.md) validation that we
+[Joi](Validation_in_NodeJS.md) validation that we
 use when validating API requests in Node/Express? They complement each other. We
 use Joi to validate the client request to the API. If this is valid, the process
 would then move onto the next stage which would be transforming the data from a

zk/Views_in_relational_databases.md

@@ -1,5 +1,6 @@
 ---
-tags: []
+tags:
+  - databases
 ---
 
 # Views in relational databases

zk/Virtual_memory_and_the_MMU_in_Linux.md

@@ -1,5 +1,7 @@
 ---
-tags: [memory]
+tags:
+  - memory
+  - Linux
 ---
 
 # Virtual memory and the Memory Management Unit

zk/What_are_disks.md

@@ -1,6 +1,7 @@
 ---
 tags:
   - disks
+  - computer-architecture
 ---
 
 # What are disks?

zk/Why_computers_use_binary.md

@@ -1,5 +1,7 @@
 ---
-tags: [binary]
+tags:
+  - binary
+  - computer-architecture
 ---
 
 # Why computers use binary