diff options
| -rw-r--r-- | src/blog/extend/index.gsp | 12 | ||||
| -rw-r--r-- | src/blog/grab/index.gsp | 12 | ||||
| -rw-r--r-- | src/blog/gsp/index.gsp | 14 | ||||
| -rw-r--r-- | src/blog/termios/index.gsp | 6 | ||||
| -rw-r--r-- | src/blog/windowing/index.gsp | 12 | ||||
| -rw-r--r-- | src/me/index.gsp | 4 | ||||
| -rw-r--r-- | src/www/index.gsp | 4 |
7 files changed, 32 insertions, 32 deletions
diff --git a/src/blog/extend/index.gsp b/src/blog/extend/index.gsp index a88a1b4..d89da74 100644 --- a/src/blog/extend/index.gsp +++ b/src/blog/extend/index.gsp @@ -27,7 +27,7 @@ html lang="en" { world. One of my favorite parts of UNIX-like systems is the composability of command-line tools. Instead of having giant monolithic programs that do everything, you have various small domain-specific - tools that all use a common interface — standard-input and -output. The + tools that all use a common interface – standard-input and -output. The following is a good example of this: } @@ -98,7 +98,7 @@ html lang="en" { you’re texting your friend or sending an email, and want to include a Unicode symbol such as ‘™’, or want to properly refer to a site you visited such as Ta’ Ħaġrat? Perhaps you even have a friend whose - surname is Mäkelä. Or maybe — you just want to send your friends a + surname is Mäkelä. Or maybe – you just want to send your friends a middle-finger emoji sometimes. } @@ -122,7 +122,7 @@ html lang="en" { p {- You can check out the file for yourself if you want. It’s got a bunch - of information in it — a lot of which is really useless for our + of information in it – a lot of which is really useless for our purposes. There are also a bunch of control characters and other things in there that I personally don’t care for, so those can probably be removed too. If it tickles your fancy, I’ve written a @code{-sed} @@ -190,7 +190,7 @@ html lang="en" { Congratulations! That entire script, which can be easily condensed down into only 2 lines of code is all you need to create a graphical interface that allows you to pick a Unicode character, and then copies - your selection to your clipboard — and it was all done by taking simple + your selection to your clipboard – and it was all done by taking simple tools and combining them to make a greater application. } @@ -290,7 +290,7 @@ html lang="en" { } p {- - Suckless — the same people that brought us @code{-dmenu} — also created + Suckless – the same people that brought us @code{-dmenu} – also created a lesser-known application called @code{-tabbed}. You can @a href="https://tools.suckless.org/tabbed/" @@ -309,4 +309,4 @@ html lang="en" { footer { FOOT } } -} +}
\ No newline at end of file diff --git a/src/blog/grab/index.gsp b/src/blog/grab/index.gsp index 87ebb5f..38918eb 100644 --- a/src/blog/grab/index.gsp +++ b/src/blog/grab/index.gsp @@ -125,7 +125,7 @@ html lang="en" { p {- So over the following few days I made major changes, rewrote lots of the - code, and overall turned my tool — @code{-grab} — into a staple part of + code, and overall turned my tool – @code{-grab} – into a staple part of my hackers toolbelt. } @@ -134,8 +134,8 @@ html lang="en" { If you’re familiar with the UNIX environment, you’re probably used to querying text with tools such as @code{-sed} and @code{-awk} using regular expressions. These are the same regular expressions we as - programmers all know and love, but with one important — yet often - overlooked — characteristic: you cannot match the newline. + programmers all know and love, but with one important – yet often + overlooked – characteristic: you cannot match the newline. } p {- @@ -143,8 +143,8 @@ html lang="en" { newline is treated no differently from another other character you want to match. Want to match an entire paragraph of text? The pattern is as simple as ‘@code{-[^\\n].+?(?=\\n\\n|$)}’. It may look - complicated if you’re new to regular expressions — PCREs to be specific - — but it’s really quite simple. You just match a non-newline character, + complicated if you’re new to regular expressions – PCREs to be specific + – but it’s really quite simple. You just match a non-newline character, and then as many characters as possible until reaching either a double newline, or the end of input. } @@ -272,4 +272,4 @@ html lang="en" { footer { FOOT } } -} +}
\ No newline at end of file diff --git a/src/blog/gsp/index.gsp b/src/blog/gsp/index.gsp index 5fae118..3989073 100644 --- a/src/blog/gsp/index.gsp +++ b/src/blog/gsp/index.gsp @@ -34,7 +34,7 @@ html lang="en" { Why do I mention all of this? Well as anyone who’s ever tried their hand at web-development knows, websites are written in HTML. I wish I could say that’s a good thing, but as anyone who’s ever looked at HTML - before would know, that language is — to put it lightly — really not + before would know, that language is – to put it lightly – really not great. It’s extremely verbose, and awkward to write- and edit (angle brackets are not the easiest-to-reach keys on the keyboard). } @@ -115,11 +115,11 @@ html lang="en" { p {= While Pug certainly hits the ‘maintain the same structure’ point right - on the head, it fails in one very crucial area — it’s a JavaScript + on the head, it fails in one very crucial area – it’s a JavaScript library @em{-only}, and so requires a whole JS setup simply to transpile your site to HTML. What a bummer. There is also a second issue which is that it uses an indentation-sensitive syntax. Normally I am actually - a fan of languages like this — such as Python — but in the case of a + a fan of languages like this – such as Python – but in the case of a markup language like Pug, this is terrible as it makes macros and templating with tools such as @code{-m4} exceptionally difficult. Pug @em{-does} offer templating faculties via JavaScript, but I really try @@ -152,7 +152,7 @@ html lang="en" { p {= Templating and macros are also very easy via macro processors thanks to the use of braces instead of whitespace-based scoping. As an example, I - like to have code samples in articles like this one — but I like to have + like to have code samples in articles like this one – but I like to have the code in an external file. To achieve this I use the following m4 macro to insert the named file verbatim into my document with delimiters escaped. As a bonus it also syntax-highlights diffs: @@ -228,7 +228,7 @@ html lang="en" { p {= As you can see, this is all really simple stuff, which is what I love so - much about Tree Sitter — it’s just so easy! With these basic + much about Tree Sitter – it’s just so easy! With these basic annotations your editor knows that attribute values should be highlighted like strings, braces like tag delimiters, etc. In a similar vein, writing a query to describe code-folding is really easy: @@ -250,7 +250,7 @@ html lang="en" { to instead identify the specific thing that annoys you and find a fix for it. I thought that the syntax of HTML was annoying and bad, so I found a solution for the syntax, while keeping the core structure the - same. In the same line of thinking, try not to over-abstract — I’m + same. In the same line of thinking, try not to over-abstract – I’m looking at you, Java developers. Abstraction often leads to exponentially increased complications the moment we want to do anything different or out of the ordinary, so unless you can find a really nice @@ -266,4 +266,4 @@ html lang="en" { footer { FOOT } } -} +}
\ No newline at end of file diff --git a/src/blog/termios/index.gsp b/src/blog/termios/index.gsp index d1f4e48..6a824c0 100644 --- a/src/blog/termios/index.gsp +++ b/src/blog/termios/index.gsp @@ -59,7 +59,7 @@ html lang="en" { aside data-ref="REF(yz)" {= If you’re familiar with the game @em{-Yahtzee} then you might - think this is a typo — it’s not. Yatzy is a very similar game + think this is a typo – it’s not. Yatzy is a very similar game to Yahtzee that is more commonly played in the nordic countries (including my current country of residence, Sweden). } @@ -192,7 +192,7 @@ html lang="en" { @code{-tcsetattr()} comes into play; we just give it our attributes and file descriptor and we can now use @kbd{-^S} without freezing our terminal! The only other thing to note is - the @code{-TCSANOW} flag — it just means that we want our + the @code{-TCSANOW} flag – it just means that we want our changes to take effect immediately. } @@ -219,4 +219,4 @@ html lang="en" { footer { FOOT } } -} +}
\ No newline at end of file diff --git a/src/blog/windowing/index.gsp b/src/blog/windowing/index.gsp index 6064a2d..61a0c64 100644 --- a/src/blog/windowing/index.gsp +++ b/src/blog/windowing/index.gsp @@ -21,14 +21,14 @@ html lang="en" { text-editor of mine. One standard feature of nearly all text editors worth their salt is windowing: the ability to have two-or-more files open side-by-side or in other configurations. - At a surface level this might seem like a no-brainer feature — + At a surface level this might seem like a no-brainer feature – and one which can substantially increment on the user-experience - — but I think we can do better …by removing it all together. + – but I think we can do better …by removing it all together. } p {= What I am not suggesting is that people should remove windowing - from their workflows entirely — windows are incredibly useful and + from their workflows entirely – windows are incredibly useful and even more so on larger monitors. I instead suggest that we begin delegating the task of windowing to the tool that does windowing best: the window manager. @@ -112,8 +112,8 @@ html lang="en" { p {= The problem here is quite clear: because I use a tiling window manager, opening Firefox to read some documentation caused my - screen to be split into two halves — one for Emacs and one for - Firefox — rendering my Emacs buffers unreadable. This is + screen to be split into two halves – one for Emacs and one for + Firefox – rendering my Emacs buffers unreadable. This is completely correct behaviour from my window manager and I don’t expect it to behave any differently, but it is clearly not ideal. The result we want is the result seen in the third image, where @@ -213,4 +213,4 @@ html lang="en" { footer { FOOT } } -} +}
\ No newline at end of file diff --git a/src/me/index.gsp b/src/me/index.gsp index ca3eced..1825151 100644 --- a/src/me/index.gsp +++ b/src/me/index.gsp @@ -30,7 +30,7 @@ html lang="en" { p {= I’m Thomas, a self-taught software-developer. I like simplicity and simple software, and I take great pride in writing small programs that - get more work done — faster — than conventional alternatives. + get more work done – faster – than conventional alternatives. } / p {= @@ -84,4 +84,4 @@ html lang="en" { footer { FOOT } } -} +}
\ No newline at end of file diff --git a/src/www/index.gsp b/src/www/index.gsp index 886fea2..059ccf6 100644 --- a/src/www/index.gsp +++ b/src/www/index.gsp @@ -63,7 +63,7 @@ html lang="en" { ul { li { NEWTAB href="https://cat-v.org" {= - @cite{-Cat -v} — @q{-The Internet is not for sissies.} + @cite{-Cat -v} – ‘The Internet is not for sissies’ } } li { @@ -148,4 +148,4 @@ html lang="en" { footer { FOOT } } -} +}
\ No newline at end of file |