Web-Projects/blog-static
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Replace all of the ref with relrefs

Browse Source
This commit is contained in:
Danila Fedorin 2022-03-09 22:03:33 -08:00
parent f719cedc37
commit 21ca8e5e90
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/blog/02_learning_emulation.md
View File

@ -3,7 +3,7 @@ title: Learning Emulation, Part 2
date: 2016-11-23 23:23:18.664038 date: 2016-11-23 23:23:18.664038
tags: ["C and C++", "Emulation"] tags: ["C and C++", "Emulation"]
--- ---
_This is the second post in a series I'm writing about Chip-8 emulation. If you want to see the first one, head [here]({{< ref "/blog/01_learning_emulation.md" >}})._ _This is the second post in a series I'm writing about Chip-8 emulation. If you want to see the first one, head [here]({{< relref "/blog/01_learning_emulation.md" >}})._
Now that we have an understanding of the physical capabilities of a Chip-8 system, we can write code that will represent such a system on our computer. In this post we'll start writing some basic code - be prepared. Now that we have an understanding of the physical capabilities of a Chip-8 system, we can write code that will represent such a system on our computer. In this post we'll start writing some basic code - be prepared.

2
content/blog/03_learning_emulation.md
View File

@ -3,7 +3,7 @@ title: Learning Emulation, Part 2.5 - Implementation
date: 2016-11-23 23:23:56.633942 date: 2016-11-23 23:23:56.633942
tags: ["C and C++", "Emulation"] tags: ["C and C++", "Emulation"]
--- ---
_This is the third post in a series I'm writing about Chip-8 emulation. If you want to see the first one, head [here]({{< ref "/blog/01_learning_emulation.md" >}})._ _This is the third post in a series I'm writing about Chip-8 emulation. If you want to see the first one, head [here]({{< relref "/blog/01_learning_emulation.md" >}})._
In the previous part of this tutorial, we created a type to represent a basic Chip-8 machine. However, we've done nothing to make it behave like one! Let's start working on that. In the previous part of this tutorial, we created a type to represent a basic Chip-8 machine. However, we've done nothing to make it behave like one! Let's start working on that.

4
content/blog/haskell_language_server_again.md
View File

@ -21,7 +21,7 @@ GHC IDE is a Haskell-based program that uses the
{{< sidenote "right" "lsp-note" "language server protocol" >}} {{< sidenote "right" "lsp-note" "language server protocol" >}}
You don't really need to know what the language server protocol (LSP) is You don't really need to know what the language server protocol (LSP) is
to use GHC IDE. If you are nonetheless interested, I wrote a little to use GHC IDE. If you are nonetheless interested, I wrote a little
bit about it <a href="{{< ref "/blog/haskell_language_server" >}}#prelude-language-server-protocol">in the previous iteration of this post.</a> bit about it <a href="{{< relref "/blog/haskell_language_server" >}}#prelude-language-server-protocol">in the previous iteration of this post.</a>
If you want more information, check out the <a href="https://microsoft.github.io/language-server-protocol/">official Microsoft page on LSP.</a> If you want more information, check out the <a href="https://microsoft.github.io/language-server-protocol/">official Microsoft page on LSP.</a>
{{< /sidenote >}} to communicate with any editor that supports it. Editors {{< /sidenote >}} to communicate with any editor that supports it. Editors
with support the the LSP include Atom, Visual Studio Code, Emacs, and Vim. Thus, with support the the LSP include Atom, Visual Studio Code, Emacs, and Vim. Thus,
@ -61,7 +61,7 @@ export PATH=$PATH:/home/<yourusername>/.local/bin
On Windows, this is done by On Windows, this is done by
{{< sidenote "right" "path-note" "editing your PATH variable." >}} {{< sidenote "right" "path-note" "editing your PATH variable." >}}
If you need to know how to change your <code>PATH</code>, I wrote If you need to know how to change your <code>PATH</code>, I wrote
about it briefly in the <a href="{{< ref "/blog/haskell_language_server" >}} about it briefly in the <a href="{{< relref "/blog/haskell_language_server" >}}
#installation-of-v0-5-0-0-windows-systems">previous iteration of this post.</a> #installation-of-v0-5-0-0-windows-systems">previous iteration of this post.</a>
{{< /sidenote >}} I don't run Windows, {{< /sidenote >}} I don't run Windows,
so I don't know where `cabal install` will place the executable, but I do know so I don't know where `cabal install` will place the executable, but I do know