phlog

commit deed8f466cd3c9d6d28ad34211e84ef6faac03a1
parent 43b860042e46000a70a0aa1f8a05abb81a7f73a7
Author: Charlie Stanton <charlie@shtanton.xyz>
Date:   Thu,  9 Sep 2021 17:49:41 +0100

Fix bullet point syntax in pipes post

Diffstat:
M
posts/gripes_with_pipes.gmi
 | 
14
+++++++-------

1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/posts/gripes_with_pipes.gmi b/posts/gripes_with_pipes.gmi
@@ -3,10 +3,10 @@ A key feature of the POSIX shell is the pipe, allowing the output of one process
 This post will involve a fair amount of POSIX shell scripting and C programming, but I've explained all of it as best I can so if you have at least a surface level understanding of these things then you should be fine.
 
 ### Charlie's 4 gripes with pipes
-- Pipes can only pass string data delimited by newlines
-- Each process only has 1 input and 2 output streams (stdin, stdout and stderr)
-- Pipes can't do cyclical data passing
-- All communication must be byte streams
+* Pipes can only pass string data delimited by newlines
+* Each process only has 1 input and 2 output streams (stdin, stdout and stderr)
+* Pipes can't do cyclical data passing
+* All communication must be byte streams
 
 ## Gripe 1: I can only pass newline delimited strings
 
@@ -143,9 +143,9 @@ This makes a fun version of the yes utility (which loops forever, repeatedly pri
 ## Gripe 4: Byte streams are the only form of data passing
 
 POSIX and System V (two sets of standards that many operating systems adhere to) both define 3 types of IPC (inter-process communication):
-- Message queues
-- Shared memory
-- Semaphores
+* Message queues
+* Shared memory
+* Semaphores
 but in the shell we only have access to byte streams, how come? Well...
 
 ### Message queues