summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorThomas Voss <mail@thomasvoss.com> 2023-12-10 03:20:06 +0100
committerThomas Voss <mail@thomasvoss.com> 2023-12-10 03:20:06 +0100
commit4f58504d167743810b89cee1906366ae56896c2f (patch)
tree9fb73c2459aa919df07f2122692afedb9eae6844
parentd0c2b2cf706cc46268f690e07ab78d341a56861a (diff)
Fix sentence spacing and add more abbrs
-rw-r--r--src/blog/extend/index.gsp15
-rw-r--r--src/blog/index.gsp2
-rw-r--r--src/blog/new-sh/index.gsp6
-rw-r--r--src/prj/index.gsp2
-rw-r--r--src/prj/mkpass/index.gsp4
-rw-r--r--src/prj/mmv/index.gsp18
-rw-r--r--src/prj/totp/index.gsp2
-rw-r--r--src/style.css50
8 files changed, 52 insertions, 47 deletions
diff --git a/src/blog/extend/index.gsp b/src/blog/extend/index.gsp
index 57334c1..3d986ff 100644
--- a/src/blog/extend/index.gsp
+++ b/src/blog/extend/index.gsp
@@ -205,11 +205,12 @@ html lang="en" {
figure .quote {
blockquote {
p {=
- The talk reviews reasons for UNIX’s popularity and shows, using UCB
- @code{-cat} as a primary example, how UNIX has grown fat.
- @code{-cat} isn’t for printing files with line numbers, it isn’t for
- compressing multiple blank lines, it’s not for looking at
- non-printing ASCII characters, it’s for concatenating files.
+ The talk reviews reasons for UNIX’s popularity and shows, using
+ m4_abbr(UCB) @code{-cat} as a primary example, how UNIX has grown
+ fat. @code{-cat} isn’t for printing files with line numbers, it
+ isn’t for compressing multiple blank lines, it’s not for looking at
+ non-printing m4_abbr(ASCII) characters, it’s for concatenating
+ files.
}
p {=
We are reminded that @code{-ls} isn’t the place for code to break a
@@ -300,8 +301,8 @@ html lang="en" {
another program (such as the @code{-st} terminal) and it adds
tab-support to it. Not only does this reduce code-duplication, but it
also is beneficial for you the software user as it means you get a
- consistent UI with consistent-behavior and -key-bindings wherever you
- go.
+ consistent m4_abbr(UI) with consistent-behavior and -key-bindings
+ wherever you go.
}
}
diff --git a/src/blog/index.gsp b/src/blog/index.gsp
index aac12e0..0673da3 100644
--- a/src/blog/index.gsp
+++ b/src/blog/index.gsp
@@ -32,7 +32,7 @@ html lang="en" {
m4_article(new-sh, {-Making a New Shell})
m4_article(extend, {-Extensible Scripting})
m4_article(nvim-ts, {-Hacking with Tree-Sitter on Neovim})
- m4_article(gsp, {-Writing an HTML Preprocessor (feat. Tree-Sitter)})
+ m4_article(gsp, {-Writing an m4_abbr(HTML) Preprocessor (feat. Tree-Sitter)})
m4_article(fw-ec, {-Patching My Laptop’s Embedded Controller})
}
}
diff --git a/src/blog/new-sh/index.gsp b/src/blog/new-sh/index.gsp
index 9da8e39..156971a 100644
--- a/src/blog/new-sh/index.gsp
+++ b/src/blog/new-sh/index.gsp
@@ -31,11 +31,11 @@ html lang="en" {
at times, and the available resources outside of the m4_abbr(POSIX)
specification itself are absolutely piss-poor as a result of the
average *NIX user failing to understand the difference between
- @code{-/bin/sh} and Bash @x-ref{-2}. What @em{-really} drew me into the
+ @code{-/bin/sh} and Bash @x-ref{-2}. What @em{-really} drew me into the
Shell was the powerful idea of composability, and being able to combine
simple tools to form a much more powerful one in only a handful of
- lines. I talked more about this @a href="/blog/extend" {-in my
- previous post}.
+ lines. I talked more about this
+ @a href="/blog/extend" {-in my previous post}.
}
p {-
diff --git a/src/prj/index.gsp b/src/prj/index.gsp
index a6e773c..1583fe1 100644
--- a/src/prj/index.gsp
+++ b/src/prj/index.gsp
@@ -27,7 +27,7 @@ html lang="en" {
p {-Posts:}
ul {
- li {a href="totp" {-totp — generate TOTP codes}}
+ li {a href="totp" {-totp — generate m4_abbr(TOTP) codes}}
li {a href="mkpass" {-mkpass — make a password}}
li {a href="mmv" {-mmv, mpc — mapped file moves and -copies}}
}
diff --git a/src/prj/mkpass/index.gsp b/src/prj/mkpass/index.gsp
index 145b5f7..e780993 100644
--- a/src/prj/mkpass/index.gsp
+++ b/src/prj/mkpass/index.gsp
@@ -15,8 +15,8 @@ html lang="en" {
over a period of a week or so. He did it because Microsoft was
largely perceived as evil, and his aim was to create a programming
platform in the Netscape navigator. That way, the browser would run
- everywhere, and the OS wouldn’t matter as much. HAHA! Down with
- Microsoft. You can see how well that worked out.
+ everywhere, and the m4_abbr(OS) wouldn’t matter as much. HAHA! Down
+ with Microsoft. You can see how well that worked out.
}
}
figcaption {-Sahil Malik}
diff --git a/src/prj/mmv/index.gsp b/src/prj/mmv/index.gsp
index 185d93e..7dc8d3b 100644
--- a/src/prj/mmv/index.gsp
+++ b/src/prj/mmv/index.gsp
@@ -195,7 +195,7 @@ html lang="en" {
input will be referred to as the @em{-input files}. Once all the input
files have been read, the utility specified by the arguments is spawned;
in this case that would be @code{-sed} with the argument
- @code{-'s/[A-Z]/‌\\L_&/g'}. The input files are then piped into
+ @code{-'s/[A-Z]/‌\\L_&/g'}. The input files are then piped into
@code{-sed} the exact same way that they would have been if we ran the
above commands without @code{-mmv}, and the output of @code{-sed} then
forms what will be referred to as the @em{-output files}. Once a
@@ -216,7 +216,7 @@ html lang="en" {
p {-
In the above example @code{-mmv} reads 2 lines from standard input,
those being @em{-LICENSE} and @em{-README}. Those are our 2 input files
- now. The @code{-tr} utility is then spawned and the input files are
+ now. The @code{-tr} utility is then spawned and the input files are
piped into it. We can simulate this in the shell:
}
@@ -323,7 +323,7 @@ html lang="en" {
@code{--0} flag to @code{-mmv}. This will tell @code{-mmv} that we want
to use the NUL-byte as our input separator and not the newline. We also
need @code{-ls} to actually provide us with the filenames delimited by
- NUL-bytes. Luckily m4_abbr(GNU) @code{-ls} gives us the @code{---zero}
+ NUL-bytes. Luckily m4_abbr(GNU) @code{-ls} gives us the @code{---zero}
flag to do just that:
}
@@ -379,7 +379,7 @@ html lang="en" {
newline-separated input, it reversed out NUL-byte separators and now
gives us 3 outputs. Luckily the folks over at @em{-util-linux} provided
us with the @code{--0} flag here too, so that we can properly handle
- NUL-delimited input. Combining all of this together we get a final
+ NUL-delimited input. Combining all of this together we get a final
working product:
}
@@ -505,7 +505,7 @@ html lang="en" {
p {-
When compared to the standard @code{-for f in *; do mv $f …; done} or
@code{-ls | … | xargs -L2 mv} constructs, @code{-mmv} is significantly
- more safe to use. These are some of the safety features that are built
+ more safe to use. These are some of the safety features that are built
into the tool:
}
@@ -548,7 +548,7 @@ html lang="en" {
directory will be automatically removed, but it remains when things go
wrong so that you can recover any missing data. The names of the
backup-subdirectories in the @code{-$XDG_CACHE_DIR/mmv} directory are
- timestamps of when the directories were created. This should make it
+ timestamps of when the directories were created. This should make it
easier for you to figure out which directory you need to recover if you
happen to have multiple of these.
}
@@ -558,9 +558,9 @@ html lang="en" {
aside {
p {-
All of these examples are ripped straight from the @code{-mmv(1)}
- manual page. If you installed @code{-mmv} through a package manager or
- via @code{-make install} then you should have the manual installed on
- your system.
+ manual page. If you installed @code{-mmv} through a package manager
+ or via @code{-make install} then you should have the manual installed
+ on your system.
}
}
diff --git a/src/prj/totp/index.gsp b/src/prj/totp/index.gsp
index a0308a2..50bfbd3 100644
--- a/src/prj/totp/index.gsp
+++ b/src/prj/totp/index.gsp
@@ -33,7 +33,7 @@ html lang="en" {
li {a href="#prologue" {-Prologue}}
li {a href="#terms" {-Terminology}}
li {a href="#usage" {-Basic Usage}}
- li {a href="#qr" {-Working with QR Codes}}
+ li {a href="#qr" {-Working with m4_abbr(QR) Codes}}
}
h2 #prologue {-Prologue}
diff --git a/src/style.css b/src/style.css
index 3c7527f..70419ed 100644
--- a/src/style.css
+++ b/src/style.css
@@ -246,30 +246,34 @@ dl {
pointer-events: none;
}
- abbr.api::before { content: 'Application Programming Interface'; }
- abbr.ast::before { content: 'Abstract Syntax Tree'; }
- abbr.cli::before { content: 'Command-Line Interface'; }
- abbr.cpu::before { content: 'Central Processing Unit'; }
- abbr.css::before { content: 'Cascading Stylesheets'; }
- abbr.cv::before { content: 'Curriculum Vitæ'; }
- abbr.ec::before { content: 'Embedded Controller'; }
- abbr.gnu::before { content: 'GNU’s Not UNIX'; }
- abbr.gsp::before { content: 'German Shorthaired Pointer'; }
- abbr.html::before { content: 'Hypertext Markup Language'; }
- abbr.it::before { content: 'Information Technology'; }
- abbr.js::before { content: 'JavaScript'; }
- abbr.led::before { content: 'Light-Emitting Diode'; }
- abbr.nas::before { content: 'Network Attached Storage'; }
- abbr.pdf::before { content: 'Portable Document Format'; }
+ abbr.api::before { content: 'Application Programming Interface'; }
+ abbr.ascii::before { content: 'American Standard Code for Information Interchange'; }
+ abbr.ast::before { content: 'Abstract Syntax Tree'; }
+ abbr.cli::before { content: 'Command-Line Interface'; }
+ abbr.cpu::before { content: 'Central Processing Unit'; }
+ abbr.css::before { content: 'Cascading Stylesheets'; }
+ abbr.cv::before { content: 'Curriculum Vitæ'; }
+ abbr.ec::before { content: 'Embedded Controller'; }
+ abbr.gnu::before { content: 'GNU’s Not UNIX'; }
+ abbr.gsp::before { content: 'German Shorthaired Pointer'; }
+ abbr.html::before { content: 'Hypertext Markup Language'; }
+ abbr.it::before { content: 'Information Technology'; }
+ abbr.js::before { content: 'JavaScript'; }
+ abbr.led::before { content: 'Light-Emitting Diode'; }
+ abbr.nas::before { content: 'Network Attached Storage'; }
+ abbr.os::before { content: 'Operating System'; }
+ abbr.pdf::before { content: 'Portable Document Format'; }
abbr.posix::before { content: 'Portable Operating System Interface'; }
- abbr.qr::before { content: 'Quick Response'; }
- abbr.rgb::before { content: 'Red Green Blue'; }
- abbr.sha::before { content: 'Secure Hash Algorithm'; }
- abbr.tfa::before { content: 'Two-Factor Authentication'; }
- abbr.totp::before { content: 'Time-Based One-Time Password'; }
- abbr.uri::before { content: 'Uniform Resource Identifier'; }
- abbr.xml::before { content: 'Extensible Markup Language'; }
- abbr.yaml::before { content: 'YAML Ain’t Markup Language™'; }
+ abbr.qr::before { content: 'Quick Response'; }
+ abbr.rgb::before { content: 'Red Green Blue'; }
+ abbr.sha::before { content: 'Secure Hash Algorithm'; }
+ abbr.tfa::before { content: 'Two-Factor Authentication'; }
+ abbr.totp::before { content: 'Time-Based One-Time Password'; }
+ abbr.ucb::before { content: 'University of California, Berkeley'; }
+ abbr.ui::before { content: 'User Interface'; }
+ abbr.uri::before { content: 'Uniform Resource Identifier'; }
+ abbr.xml::before { content: 'Extensible Markup Language'; }
+ abbr.yaml::before { content: 'YAML Ain’t Markup Language™'; }
}
@media (max-width: 600px) {