diff options
| author | Aki <please@ignore.pl> | 2023-12-30 03:02:56 +0100 |
|---|---|---|
| committer | Aki <please@ignore.pl> | 2023-12-30 03:02:56 +0100 |
| commit | b334c0b6bcf520ff20ab2a3192b56304c6ffb306 (patch) | |
| tree | 025843b261791ebdb191a357777396e4a06b0d8f | |
| parent | 178348d704a6186d8ed0485b7909ee9bd5b9ff9d (diff) | |
| download | ignore.pl-b334c0b6bcf520ff20ab2a3192b56304c6ffb306.zip ignore.pl-b334c0b6bcf520ff20ab2a3192b56304c6ffb306.tar.gz ignore.pl-b334c0b6bcf520ff20ab2a3192b56304c6ffb306.tar.bz2 | |
Date and post headers styles changed
37 files changed, 234 insertions, 174 deletions
diff --git a/LICENSE.html b/LICENSE.html index d26dd88..aba8927 100644 --- a/LICENSE.html +++ b/LICENSE.html @@ -13,7 +13,7 @@ <nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> <article> -<header> +<header style="display: block; text-align: center;"> <h1 style="margin-bottom: 0;">IGNORE THIS LICENSE</h1> <p style="margin-top: 0;">Version 2, <time>July 2020</time> <p>Copyright <u><Year></u> <u><Holder></u> diff --git a/alcohol_of_the_year_2022.html b/alcohol_of_the_year_2022.html index ff433da..767ca47 100644 --- a/alcohol_of_the_year_2022.html +++ b/alcohol_of_the_year_2022.html @@ -10,11 +10,13 @@ <title>Alcohol of the Year 2022</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>29 March 2023</time> +<h1>Alcohol of the Year 2022</h1> +</header> <article> -<h1>Alcohol of the Year 2022</h1> -<p class="subtitle">Published on 2023-03-29 20:21:00+02:00 <p>I was thinking about making some profound blog article about how creating any stuff not only hardware, software or art is nice and anyone can find a niche for themselves. Well, there you have it, until I finalize proper analysis of my writing habits and goals I don't think I want to write things like that. Instead, let's talk about alcohol. diff --git a/atom.xml.sh b/atom.xml.sh index f478cfd..4022604 100755 --- a/atom.xml.sh +++ b/atom.xml.sh @@ -14,7 +14,7 @@ dates () { if [ -z "$published" ]; then published=$(git rev-list --no-commit-header --pretty=%aI HEAD -- "$1" | tail -n1) fi - local modified=$(git rev-list --after="2023-12-27 00:45+01:00" -1 --no-commit-header --pretty=%aI HEAD -- "$1") + local modified=$(git rev-list --after="2023-12-30 03:30+01:00" -1 --no-commit-header --pretty=%aI HEAD -- "$1") [ -z "$modified" ] && modified=$(meta "last-modified-on" "$1") [ -z "$modified" ] && modified=$published echo "<updated>$modified</updated>" diff --git a/dear_imgui_and_love.html b/dear_imgui_and_love.html index 2acb165..7c0b3ab 100644 --- a/dear_imgui_and_love.html +++ b/dear_imgui_and_love.html @@ -10,11 +10,13 @@ <title>Dear ImGui and LÖVE,</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>14 August 2020</time> +<h1>Dear ImGui and LÖVE,</h1> +</header> <article> -<h1>Dear ImGui and LÖVE,</h1> -<p class="subtitle">Published on 2020-08-14 21:47:00+02:00 <p>Believe it or not, this one was requested. It's surprising considered that just recently I claimed that according to stats nobody reads this website. It may or may not be a coincident that I have received this request over a phone. <p>Anyway, <a href="https://github.com/ocornut/imgui">Dear ImGui</a> is a C++ library for graphical user interface. As diff --git a/deconstructing_web_browsers.html b/deconstructing_web_browsers.html index 4a6cc25..a7f3cee 100644 --- a/deconstructing_web_browsers.html +++ b/deconstructing_web_browsers.html @@ -10,11 +10,13 @@ <title>Deconstructing Web Browsers</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>25 July 2021</time> +<h1>Deconstructing Web Browsers</h1> +</header> <article> -<h1>Deconstructing Web Browsers</h1> -<p class="subtitle">Published on 2021-07-25 14:53:00+02:00 <p>Welcome to one of my little experiments! The theme is simple: to deconstruct a web browser and create several utilities with distinct and clear responsibilities in its stead. This is not your regular blog post. Honestly, I'm not yet sure what it is, but I'll figure it out at some point. Expect this page to be updated and extend. (Well, just like diff --git a/difference_between_mnt_and_media.html b/difference_between_mnt_and_media.html index dbfbf80..47fddcf 100644 --- a/difference_between_mnt_and_media.html +++ b/difference_between_mnt_and_media.html @@ -10,11 +10,13 @@ <title>Difference Between /mnt and /media</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>12 June 2020</time> +<h1>Difference Between /mnt and /media</h1> +</header> <article> -<h1>Difference Between /mnt and /media</h1> -<p class="subtitle">Published on 2020-06-12 19:00:00+02:00 <p>In this article I will try to answer questions like: <i>What is the difference between /mnt and /media in FHS and *nixes?</i>, <i>Why was /media added to FHS?</i>, and perhaps <i>What is the purpose of /mnt, and what is it for /media?</i> diff --git a/different_ways_of_reporting_errors.html b/different_ways_of_reporting_errors.html index 6130e29..b4e693b 100644 --- a/different_ways_of_reporting_errors.html +++ b/different_ways_of_reporting_errors.html @@ -5,17 +5,19 @@ <meta name="author" content="aki"> <meta name="tags" content="programming, tutorial, error handling, errors, exceptions"> <meta name="published-on" content="2022-04-28T19:00:00+02:00"> -<meta name="last-modified-on" content="2023-06-17T22:27:00+02:00"> +<meta name="last-modified-on" content="2022-06-17T22:27:00+02:00"> <link rel="icon" type="image/png" href="favicon.png"> <link rel="stylesheet" href="style.css"> <title>Different Ways of Reporting Errors</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>28 April 2022</time> +<h1>Different Ways of Reporting Errors</h1> +</header> <article> -<h1>Different Ways of Reporting Errors</h1> -<p class="subtitle">Published on 2022-04-28 19:00:00+02:00, last modified on 2022-06-17 22:27:00+02:00 <p>Errors are a key component of writing software - programs, libraries, scripts, you name it. We need to check for them, catch them, mitigate, log, and finally create. In this article, I want to give you an overview of various methods of that last activity - creating errors - sometimes also called raising or throwing, especially when the errors are diff --git a/environments_in_lua_5_2_and_beyond.html b/environments_in_lua_5_2_and_beyond.html index ee2e922..3c6469c 100644 --- a/environments_in_lua_5_2_and_beyond.html +++ b/environments_in_lua_5_2_and_beyond.html @@ -10,11 +10,13 @@ <title>Environments in Lua 5.2 and Beyond</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>4 July 2020</time> +<h1>Environments in Lua 5.2 and Beyond</h1> +</header> <article> -<h1>Environments in Lua 5.2 and Beyond</h1> -<p class="subtitle">Published on 2020-07-04 20:39:00+02:00 <p>Environments are a way of dealing with various problems. Or creating them entirely on your own. Primarily, they are used to isolate a selected part of a program. As Lua is meant to be used as an embedded language, you may find yourself wanting to separate user created addons from more internal scripts. In short: sandboxing and overall security. diff --git a/git_rebase_illustrated_with_time_travel.html b/git_rebase_illustrated_with_time_travel.html index 2daee15..0b7d4c6 100644 --- a/git_rebase_illustrated_with_time_travel.html +++ b/git_rebase_illustrated_with_time_travel.html @@ -10,11 +10,13 @@ <title>Git Rebase Illustrated With Time Travel</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>28 January 2022</time> +<h1>Git Rebase Illustrated With Time Travel</h1> +</header> <article> -<h1>Git Rebase Illustrated With Time Travel</h1> -<p class="subtitle">Published on 2022-01-28 16:43:00+01:00 <p>Back in the office days, colleagues and I would have weekly discussions about git which usually ended with comparing merge to rebase or with me preaching about the dangers of rewriting the history. Let's go back to these times but with a slight twist. There's already plenty of other in-depth git tutorials and <b>git-rebase</b>(1) is great and you should diff --git a/graveyard_of_the_drawings.html b/graveyard_of_the_drawings.html index 930295b..893c6a6 100644 --- a/graveyard_of_the_drawings.html +++ b/graveyard_of_the_drawings.html @@ -11,11 +11,13 @@ <title>Graveyard of the Drawings</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>26 December 2023</time> +<h1>Graveyard of the Drawings</h1> +</header> <article> -<h1>Graveyard of the Drawings</h1> -<p class="subtitle">Last modified on 2023-12-26 21:39:00+01:00 <p>Here are the drawings I made for articles that I decided to remove. No context, no nothing. Just images. Despite the style, I still think that it'd be a little bit of waste to just remove them along the texts and reusing them in different articles is just lazy.</p> diff --git a/guilty_pleasure_of_dirty_memory.html b/guilty_pleasure_of_dirty_memory.html index 200070a..5e3bbcb 100644 --- a/guilty_pleasure_of_dirty_memory.html +++ b/guilty_pleasure_of_dirty_memory.html @@ -10,11 +10,13 @@ <title>Guilty Pleasure of Dirty Memory</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>28 July 2022</time> +<h1>Guilty Pleasure of Dirty Memory</h1> +</header> <article> -<h1>Guilty Pleasure of Dirty Memory</h1> -<p class="subtitle">Published on 2022-07-28 22:40:00+02:00 <p>"Remember to free the allocated memory!" That's what we usually teach everyone when they start their journey with manual memory management. Of course, it's the rightful way. The one and only, isn't it? <p>Well, yes but no.</p> diff --git a/half_of_my_css_are_links.html b/half_of_my_css_are_links.html index 84e4e40..68d64af 100644 --- a/half_of_my_css_are_links.html +++ b/half_of_my_css_are_links.html @@ -10,11 +10,13 @@ <title>Half of My CSS Are Links</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>19 May 2020</time> +<h1>Half of My CSS Are Links</h1> +</header> <article> -<h1>Half of My CSS Are Links</h1> -<p class="subtitle">Published on 2020-05-19 20:09:00+02:00 <p>Lately, I've been tinkering in <a href="style.css">stylesheet of this website</a>. My main goals are readability and minimalism, in this order. I do put some little things to appeal to my taste, but let this one slide, please, I'm confident that my stylesheet is one of the smallest there are. diff --git a/how_to_archive_with_posix_ar.html b/how_to_archive_with_posix_ar.html index 19fc082..147f9f2 100644 --- a/how_to_archive_with_posix_ar.html +++ b/how_to_archive_with_posix_ar.html @@ -11,11 +11,13 @@ <title>How to Archive With POSIX ar</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>26 July 2021</time> +<h1>How to Archive With POSIX ar</h1> +</header> <article> -<h1>How to Archive With POSIX ar</h1> -<p class="subtitle">Published on 2021-07-26 00:47:00+02:00, last modified on 2021-07-26 17:09:00+02:00 <p>Let's continue <a href="how_to_archive_with_posix_tar_cpio_and_pax.html">last POSIX archiving guide</a> from the very spot we finished. Today, we'll deal with just one tool. Very peculiar one, because it's more of a development utility than an archiver with portable format. In fact, it doesn't have a defined format at all. More than that, POSIX diff --git a/how_to_archive_with_posix_tar_cpio_and_pax.html b/how_to_archive_with_posix_tar_cpio_and_pax.html index e24b8d8..ead23c7 100644 --- a/how_to_archive_with_posix_tar_cpio_and_pax.html +++ b/how_to_archive_with_posix_tar_cpio_and_pax.html @@ -11,11 +11,13 @@ <title>How to Archive With POSIX tar, cpio and pax</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>22 July 2020</time> +<h1>How to Archive With POSIX tar, cpio and pax</h1> +</header> <article> -<h1>How to Archive With POSIX tar, cpio and pax</h1> -<p class="subtitle">Published on 2020-07-22 22:30:00+02:00, last modified on 2022-01-26 19:10:00+01:00 <p>The usual answer to archive anything is <a href="https://www.gnu.org/software/tar/">tar</a>. As you may see I intentionally linked to the GNU Tar. If you are a *BSD user then you use some other implementation. Both of them follow and extend POSIX'es standard for tar utility. Or so you would think. diff --git a/how_to_build_software_with_make.html b/how_to_build_software_with_make.html index 10e612f..25f3792 100644 --- a/how_to_build_software_with_make.html +++ b/how_to_build_software_with_make.html @@ -10,11 +10,13 @@ <title>How to Build Software With Make</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>27 March 2023</time> +<h1>How to Build Software With Make</h1> +</header> <article> -<h1>How to Build Software With Make</h1> -<p class="subtitle">Published on 2023-03-27 22:35:00+02:00 <p>To compile an executable from a single C source file we need just one compiler invocation in our shell: <pre> $ cc myprogram.c -o myprogram diff --git a/how_to_compress_files_in_posix.html b/how_to_compress_files_in_posix.html index 5b3e1af..bb5e5dc 100644 --- a/how_to_compress_files_in_posix.html +++ b/how_to_compress_files_in_posix.html @@ -10,11 +10,13 @@ <title>How to Compress Files in POSIX</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>14 August 2021</time> +<h1>How to Compress Files in POSIX</h1> +</header> <article> -<h1>How to Compress Files in POSIX</h1> -<p class="subtitle">Published on 2021-08-14 19:48:00+02:00 <p>This was quite an amusing one to read about. On one hand, the results kind of surprised me, but then, on the other... What exactly did I expect? <p>Anyway! How does one compress files in a POSIX-compliant system? @@ -113,6 +115,5 @@ for why it is not used or even installed by default in most Linux distributions. but I expect rather good results. <p>The main takeaway from this article is that if you plan to write anything that is portable across POSIX-compliant or semi-compliant systems, then you need to give compressing slightly more attention. - </article> -<script src="https://stats.ignore.pl/track.js"></script>
\ No newline at end of file +<script src="https://stats.ignore.pl/track.js"></script> diff --git a/how_to_flash_lolin_nodemcu_v3.html b/how_to_flash_lolin_nodemcu_v3.html index 573d88e..3fc7eca 100644 --- a/how_to_flash_lolin_nodemcu_v3.html +++ b/how_to_flash_lolin_nodemcu_v3.html @@ -9,11 +9,13 @@ <title>How to Flash LOLin NodeMCU v3</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>29 June 2020</time> +<h1>How to Flash LOLin NodeMCU v3</h1> +</header> <article> -<h1>How to Flash LOLin NodeMCU v3</h1> -<p class="subtitle">Published on 2020-06-29 17:58:00+02:00 <p>Republishing old content. This is from when I bought and flashed my first NodeMCU clone (perhaps "loose implementation"?) of NodeMCU v3 called LOLin v3. <p>This little board is using CH304G TTL to USB converter, so if you happen to work on Windows you must make sure you diff --git a/how_to_generate_files_from_templates_in_shell.html b/how_to_generate_files_from_templates_in_shell.html index c22b069..5dae721 100644 --- a/how_to_generate_files_from_templates_in_shell.html +++ b/how_to_generate_files_from_templates_in_shell.html @@ -10,11 +10,13 @@ <title>How to Generate Files From Templates in Shell</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>26 March 2023</time> +<h1>How to Generate Files From Templates in Shell</h1> +</header> <article> -<h1>How to Generate Files From Templates in Shell</h1> -<p class="subtitle">Published on 2023-03-26 18:05:00+02:00 <p>This is a total rewrite of an old article. I no longer liked it and my methods have changed. <p>Generating or "configuring" files from a template is a common occurrence. A prime example from what I usually use is <a href="https://cmake.org/cmake/help/latest/command/configure_file.html">configure_file</a> in CMake. Another example diff --git a/how_to_organize_your_lua_project.html b/how_to_organize_your_lua_project.html index 639c6d4..0b7bab5 100644 --- a/how_to_organize_your_lua_project.html +++ b/how_to_organize_your_lua_project.html @@ -11,11 +11,13 @@ <title>How to Organize Your Lua Project</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>7 January 2021</time> +<h1>How to Organize Your Lua Project</h1> +</header> <article> -<h1>How to Organize Your Lua Project</h1> -<p class="subtitle">Published on 2021-01-07 15:45:00+01:00, last modified on 2022-01-26 19:20:00+01:00 <p>From time to time I hear complaints about how Lua handles modules. Here and there I see and even answer myself questions regarding <code>require</code> and adjusting the paths in <code>package</code> to allow some desired behaviour, with the most prominent issue of relative imports that always work. diff --git a/how_to_write_install_targets_for_lua_modules_in_makefiles.html b/how_to_write_install_targets_for_lua_modules_in_makefiles.html index a43b259..40e69b7 100644 --- a/how_to_write_install_targets_for_lua_modules_in_makefiles.html +++ b/how_to_write_install_targets_for_lua_modules_in_makefiles.html @@ -31,11 +31,13 @@ <title>How to Write Install Targets for Lua Modules in Makefiles</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>29 December 2023</time> +<h1>How to Write Install Targets for Lua Modules in Makefiles</h1> +</header> <article> -<h1>How to Write Install Targets for Lua Modules in Makefiles</h1> -<p class="subtitle">Published on 2023-12-29 21:45:00+01:00 <p>You can skip the full context and go right to the <a href="#proposition">explanation of the proposed makefile</a>. <p>"Installation" can mean two things: installing packages using package manager (e.g., <b>pacman</b>(8), <b>apt</b>(8)) or copying files from one spot to another. Of course, package managers may copy files during the installation process, diff --git a/hunt_for_lex_and_yacc_the_dinosaur.html b/hunt_for_lex_and_yacc_the_dinosaur.html index 05a3026..d510bc3 100644 --- a/hunt_for_lex_and_yacc_the_dinosaur.html +++ b/hunt_for_lex_and_yacc_the_dinosaur.html @@ -10,11 +10,13 @@ <title>Hunt for Lex and Yacc, the Dinosaur</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>20 June 2020</time> +<h1>Hunt for Lex and Yacc, the Dinosaur</h1> +</header> <article> -<h1>Hunt for Lex and Yacc, the Dinosaur</h1> -<p class="subtitle">Published on 2020-06-20 23:36:00+02:00 <p><q>Everything is text</q> we were told. Imagine that with this assumption we plan to take on a dinosaur. Indeed, this is one of the greatest jokes ever done in history of programming. Lex manual page said that there is an asteroid that will kill it for us. There is none, and the dinosaur is what we created ourselves and what we are made of. @@ -41,74 +41,72 @@ software and hardware engineering. I post here my projects, experiments, and wha <ul> <li> <a href="how_to_write_install_targets_for_lua_modules_in_makefiles.html">How to Write Install Targets for Lua Modules in Makefiles</a><br> - <time>2023-12-29</time> + <time>29 December 2023</time> <li> <a href="self_update_end_of_year_2023.html">Self Update: End of Year 2023</a><br> - <time>2023-12-27</time> + <time>27 December 2023</time> <li> <a href="alcohol_of_the_year_2022.html">Alcohol of the Year 2022</a><br> - <time>2023-03-29</time> + <time>29 March 2023</time> <li> <a href="how_to_build_software_with_make.html">How to Build Software With Make</a><br> - <i>This replaced an old post from 2020 about the same topic.</i><br> - <time>2023-03-27</time> + <time>27 March 2023</time> <li> <a href="how_to_generate_files_from_templates_in_shell.html">How to Generate Files From Templates in Shell</a><br> - <i>This replaced an old post from 2020 about the same topic.</i><br> - <time>2023-03-26</time> + <time>26 March 2023</time> <li> <a href="self_update_march_2023.html">Self Update: March 2023</a><br> - <time>2023-03-23</time> + <time>23 March 2023</time> <li> <a href="starshatter_open_dev_update_2022_09.html">Starshatter: The Open Source Project - Dev Update - September 2022</a><br> - <time>2022-09-24</time> + <time>24 September 2022</time> <li> <a href="guilty_pleasure_of_dirty_memory.html">Guilty Pleasure of Dirty Memory</a><br> - <time>2022-07-28</time> + <time>28 July 2022</time> <li> <a href="lets_not_store_versions_in_versioned_files.html">Let's Not Store Versions in Versioned Files</a><br> - <time>2022-07-02</time> + <time>2 July 2022</time> <li> <a href="using_pacman_to_manage_emscripten_packages.html">Using pacman to Manage Emscripten Packages</a><br> - <time>2022-06-19</time> + <time>19 June 2022</time> <li> <a href="different_ways_of_reporting_errors.html">Different Ways of Reporting Errors</a><br> - <time>2022-04-28</time> + <time>28 April 2022</time> <li> <a href="starshatter_open_dev_update_2022_04.html">Starshatter: The Open Source Project - Dev Update - April 2022</a><br> - <time>2022-04-08</time> + <time>8 April 2022</time> <li> <a href="starshatter_open_dev_update_2022_01.html">Starshatter: The Open Source Project - Dev Update - January 2022</a><br> - <time>2022-01-30</time> + <time>30 January 2022</time> <li> <a href="git_rebase_illustrated_with_time_travel.html">Git Rebase Illustrated With Time Travel</a><br> - <time>2022-01-28</time> + <time>28 January 2022</time> <li> <a href="you_can_serve_static_data_over_http.html">You Can Serve Static Data Over HTTP</a><br> - <time>2022-01-27</time> + <time>27 January 2022</time> <li> <a href="playing_around_with_simple_interfaces.html">Playing Around With Simple Interfaces</a><br> - <time>2022-01-25</time> + <time>25 January 2022</time> <li> <a href="how_to_compress_files_in_posix.html">How to Compress Files in POSIX</a><br> - <time>2021-08-14</time> + <time>14 August 2021</time> <li> <a href="how_to_archive_with_posix_ar.html">How to Archive With POSIX ar</a><br> - <time>2021-07-26</time> + <time>26 July 2021</time> <li> <a href="deconstructing_web_browsers.html">Deconstructing Web Browsers</a><br> - <time>2021-07-25</time> + <time>25 July 2021</time> <li> <a href="how_to_organize_your_lua_project.html">How To Organize Your Lua Project</a><br> - <time>2021-01-07</time> + <time>7 January 2021</time> <li> <a href="dear_imgui_and_love.html">Dear ImGui and LÖVE,</a><br> - <time>2020-08-14</time> + <time>14 August 2020</time> <li> <a href="writing_minimal_html5_documents_is_fun.html">Writing Minimal HTML5 Documents is Fun</a><br> - <time>2020-08-03</time> + <time>3 August 2020</time> <li> <a href="web_browsers_are_no_more.html">Web Browsers Are No More</a><br> - <time>2020-07-28</time> + <time>28 July 2020</time> <li> <a href="how_to_archive_with_posix_tar_cpio_and_pax.html">How to Archive With POSIX tar, cpio and pax</a><br> - <time>2020-07-22</time> + <time>22 July 2020</time> <li> <a href="of_privacy_and_traffic_tracking.html">Of Privacy and Traffic Tracking</a><br> - <time>2020-07-11</time> + <time>11 July 2020</time> <li> <a href="environments_in_lua_5_2_and_beyond.html">Environments in Lua 5.2 and Beyond</a><br> - <time>2020-07-04</time> + <time>4 July 2020</time> <li> <a href="how_to_flash_lolin_nodemcu_v3.html">How to Flash LOLin NodeMCU v3</a><br> - <time>2020-06-29</time> + <time>29 June 2020</time> <li> <a href="hunt_for_lex_and_yacc_the_dinosaur.html">Hunt for Lex and Yacc, the Dinosaur</a><br> - <time>2020-06-20</time> + <time>20 June 2020</time> <li> <a href="difference_between_mnt_and_media.html">Difference Between /mnt and /media</a><br> - <time>2020-06-12</time> + <time>12 June 2020</time> <li> <a href="journey_home_application_deployment.html">Journey /home - Application Deployment</a><br> - <time>2020-05-29</time> + <time>29 May 2020</time> <li> <a href="half_of_my_css_are_links.html">Half of My CSS Are Links</a><br> - <time>2020-05-19</time> + <time>19 May 2020</time> <li> <a href="markdown_is_bad_for_you.html">Markdown Is Bad for You</a><br> - <time>2020-05-13</time> + <time>13 May 2020</time> </ul> </section> diff --git a/journey_home_application_deployment.html b/journey_home_application_deployment.html index 267754b..d1a0248 100644 --- a/journey_home_application_deployment.html +++ b/journey_home_application_deployment.html @@ -10,11 +10,13 @@ <title>Journey /home - Application Deployment</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>29 May 2020</time> +<h1>Journey /home - Application Deployment</h1> +</header> <article> -<h1>Journey /home - Application Deployment</h1> -<p class="subtitle">Published on 2020-05-29 01:27:00+02:00</p> <img src="journey_home_application_deployment-1.png" alt="mountains and stuff"> <p>File hierarchy in Linux is a mess. However, this time I won't discuss why it is so. Instead, I've mentioned it, so that we don't feel bad after what we'll do in here. It's a mess, and it's our little mess that we can shape to our diff --git a/lets_not_store_versions_in_versioned_files.html b/lets_not_store_versions_in_versioned_files.html index 70fa650..c7a5552 100644 --- a/lets_not_store_versions_in_versioned_files.html +++ b/lets_not_store_versions_in_versioned_files.html @@ -11,11 +11,13 @@ <title>Let's Not Store Versions in Versioned Files</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>2 July 2022</time> +<h1>Let's Not Store Versions in Versioned Files</h1> +</header> <article> -<h1>Let's Not Store Versions in Versioned Files</h1> -<p class="subtitle">Published on 2022-07-02 23:33:33+02:00, last modified on 2022-07-04 18:00:00+02:00 <p>It is a rather common practice to include version numbers directly in the meta files or sources that are stored inside a code repository. To list few examples: <a href="https://www.npmjs.com/">npm</a> makes it part of its regular practices, python's <a href="https://setuptools.pypa.io/">setuptools</a> usually involves various hacks, be it normal diff --git a/markdown_is_bad_for_you.html b/markdown_is_bad_for_you.html index 7d34b0b..c181eaf 100644 --- a/markdown_is_bad_for_you.html +++ b/markdown_is_bad_for_you.html @@ -11,11 +11,13 @@ <title>Markdown Is Bad for You</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>13 May 2020</time> +<h1>Markdown Is Bad for You</h1> +</header> <article> -<h1>Markdown Is Bad for You</h1> -<p class="subtitle">Published on 2020-05-13 17:32:00+02:00, last modified on 2022-01-30 15:00:00+01:00 <p>Markdown is a markup language. Actually, it wouldn't be misleading to say that it's a whole family of languages that are derived from the syntax created by <a href="https://daringfireball.net/">John Gruber</a> et alii. Gruber's creation was inspired from other markup languages but, as author notes, it mostly follows the convention used in plain-text diff --git a/of_privacy_and_traffic_tracking.html b/of_privacy_and_traffic_tracking.html index d924f89..dd4ce7a 100644 --- a/of_privacy_and_traffic_tracking.html +++ b/of_privacy_and_traffic_tracking.html @@ -10,11 +10,13 @@ <title>Of Privacy and Traffic Tracking</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>11 July 2020</time> +<h1>Of Privacy and Traffic Tracking</h1> +</header> <article> -<h1>Of Privacy and Traffic Tracking</h1> -<p class="subtitle">Published on 2020-07-11 21:11:00+02:00 <p>Over the past weeks I wondered if anyone actually reads or visits this website. I kind of started worrying that someone could want to leave some feedback in one way or another. I have plans to handle that, but I also have other interests right now. I decided to quickly set up a method that will show me that there is no need to worry or hurry up. diff --git a/playing_around_with_simple_interfaces.html b/playing_around_with_simple_interfaces.html index e4d682c..cd357e6 100644 --- a/playing_around_with_simple_interfaces.html +++ b/playing_around_with_simple_interfaces.html @@ -11,11 +11,13 @@ <title>Playing Around With Simple Interfaces</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>25 January 2022</time> +<h1>Playing Around With Simple Interfaces</h1> +</header> <article> -<h1>Playing Around With Simple Interfaces</h1> -<p class="subtitle">Published on 2022-01-25 23:45:00+01:00, last modified on 2022-01-26 18:44:00+01:00 <p>This one comes as a little surprising and for experienced (or even intermediate) reader may appear boring. Think of it as "back to the fundamentals" type of article. Now that I think about it... Do I even have anything that wouldn't classify into this category? Oh, yeah, rants.</p> diff --git a/self_update_end_of_year_2023.html b/self_update_end_of_year_2023.html index f7124e5..a46909c 100644 --- a/self_update_end_of_year_2023.html +++ b/self_update_end_of_year_2023.html @@ -10,11 +10,13 @@ <title>Self Update: End of Year 2023</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>27 December 2023</time> +<h1>Self Update: End of Year 2023</h1> +</header> <article> -<h1>Self Update: End of Year 2023</h1> -<p class="subtitle">Published on 2023-12-27 16:44:00+01:00 <p>This has been an... interesting year. I was too lazy and wasted too much time on unnecessary stuff, but I don't want to linger and kick myself as I lay down. Last three months I have been slowly going through what I did, what I want to do, how I want to do these things, what do I find fun, what is useful, what is not. This process is still ongoing. Heck, diff --git a/self_update_march_2023.html b/self_update_march_2023.html index 37727cc..e1024f5 100644 --- a/self_update_march_2023.html +++ b/self_update_march_2023.html @@ -10,11 +10,13 @@ <title>Self Update: March 2023</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>23 March 2023</time> +<h1>Self Update: March 2023</h1> +</header> <article> -<h1>Self Update: March 2023</h1> -<p class="subtitle">Published on 2023-03-23 22:58:00+01:00 <p>Time has passed, hasn't it? I didn't do any empty update posts for quite time now. Two years or so. Hard to tell really because I didn't use any specific version control for the blog at that time and I was changing pretty much everything in frenzy anyway. I'm wondering if I have another one of those in me. Still, contemplating this I saved for diff --git a/starshatter_open_dev_update_2022_01.html b/starshatter_open_dev_update_2022_01.html index 7cca862..8f99703 100644 --- a/starshatter_open_dev_update_2022_01.html +++ b/starshatter_open_dev_update_2022_01.html @@ -11,11 +11,13 @@ <title>Starshatter: The Open Source Project - Dev Update - January 2022</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>30 January 2022</time> +<h1>Starshatter: The Open Source Project<br>Dev Update - January 2022</h1> +</header> <article> -<h1>Starshatter: The Open Source Project<br>Dev Update - January 2022</h1> -<p class="subtitle">Published on 2022-01-30 20:00:00+01:00, last modified on 2022-04-08 19:10+02:00 <p>Few months ago I created a fork of Starshatter Open, and because it appears to be the only (semi-) active one, and also because I already have a platform on which I share my pointless thoughts; I thought that I'll do exactly that. <p>Starshatter was never a popular game and these days the community is even more dead. That's mostly because there's diff --git a/starshatter_open_dev_update_2022_04.html b/starshatter_open_dev_update_2022_04.html index 90d21e1..d9100ae 100644 --- a/starshatter_open_dev_update_2022_04.html +++ b/starshatter_open_dev_update_2022_04.html @@ -10,11 +10,13 @@ <title>Starshatter: The Open Source Project - Dev Update - April 2022</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>8 April 2022</time> +<h1>Starshatter: The Open Source Project<br>Dev Update - April 2022</h1> +</header> <article> -<h1>Starshatter: The Open Source Project<br>Dev Update - April 2022</h1> -<p class="subtitle">Published on 2022-04-08 20:13:00+02:00 <p>Around two months have passed since last development update for my for of Starshatter source. In this time I had a few activity spikes and got some work done. Sad news I'm still at the stage of breaking things rather than implementing novel things in the game. This theme will keep up until I will feel comfortable with the project structure enough to diff --git a/starshatter_open_dev_update_2022_09.html b/starshatter_open_dev_update_2022_09.html index 4b804ef..04c1dc1 100644 --- a/starshatter_open_dev_update_2022_09.html +++ b/starshatter_open_dev_update_2022_09.html @@ -10,11 +10,13 @@ <title>Starshatter: The Open Source Project - Dev Update - September 2022</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>24 September 2022</time> +<h1>Starshatter: The Open Source Project<br>Dev Update - September 2022</h1> +</header> <article> -<h1>Starshatter: The Open Source Project<br>Dev Update - September 2022</h1> -<p class="subtitle">Published on 2022-09-24 16:40:00+02:00 <p>The time has come to write a dev update of the Starshatter project. It's been some time and there are some news and some ideas that need a little more time to hatch but are good enough to share with you all to potentially get some feedback. Let's start. @@ -1,32 +1,40 @@ body { - max-width: 43em; - margin: 1em auto; - padding: 0 1em 22vh 1em; - font-family: sans-serif; + max-width: 43rem; + margin: 0 auto; + padding: 1rem 1rem 33vh 1em; + font-family: Garamond serif; } -p, dd { - line-height: 1.4em; - text-align: justify; +header { + display: grid; + grid-template: + "time nav" + "title title" / 1fr auto; } -p, dd, pre { - margin-bottom: 1em; +header > time { grid-area: time; } + +header > h1 { + grid-area: title; + margin-top: 0.2rem; + margin-bottom: 0; +} + +header > nav { + grid-area: nav; + margin-left: 1em; +} + +article { + line-height: 1.36em; } -h1, h2, h3, h4, h5, h6 { - font-weight: normal; - margin: 1.5em 0 0.2em 0; +p, dd, pre { + margin-bottom: 1em; } -article h2, -article h3, -article h4, -article h5, -article h6, -article .subtitle { - border-bottom: 1px dashed #999; - padding: 0 0 0.2em 0; +h1 { + margin-top: 0; } hr { @@ -35,17 +43,12 @@ hr { border-width: 0 0 1px 0; } -.subtitle { - color: #999; - margin-top: 0.2em; - font-size: 90%; - text-align: center; -} - pre { background-color: #f0f0f0; - padding: 1em; + padding: 0.4em 1rem; overflow-x: auto; + margin-left: -1rem; + margin-right: -1rem; } code { @@ -53,19 +56,12 @@ code { padding: 0 1px; } -img { - max-width: 100%; -} - article > img { + max-width: 100%; display: block; margin: 1em auto; } -article > header > *, article > h1 { - text-align: center; -} - a:link, a:visited.always-fresh { color: #0e42ef; diff --git a/using_pacman_to_manage_emscripten_packages.html b/using_pacman_to_manage_emscripten_packages.html index 87be102..4e2e733 100644 --- a/using_pacman_to_manage_emscripten_packages.html +++ b/using_pacman_to_manage_emscripten_packages.html @@ -10,11 +10,13 @@ <title>Using pacman to Manage Emscripten Packages</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>19 June 2022</time> +<h1>Using pacman to Manage Emscripten Packages</h1> +</header> <article> -<h1>Using pacman to Manage Emscripten Packages</h1> -<p class="subtitle">Published on 2022-06-19 17:35:00+02:00 <p>C was created for use with Unix. Quite quickly it became one of the most used programming languages of all time. After some additional years it made its way into Linux kernel and operating system. To this year it is the primary language that is used to interface with the kernel or to write any sort of utilities. If not directly then through diff --git a/web_browsers_are_no_more.html b/web_browsers_are_no_more.html index faf60df..1ac053e 100644 --- a/web_browsers_are_no_more.html +++ b/web_browsers_are_no_more.html @@ -5,16 +5,19 @@ <meta name="author" content="aki"> <meta name="tags" content="web, applications, internet, browser"> <meta name="published-on" content="2020-07-28T19:39:00+02:00"> +<meta name="last-modified-on" content="2021-07-25T12:56:00+02:00"> <link rel="icon" type="image/png" href="favicon.png"> <link rel="stylesheet" type="text/css" href="style.css"> <title>Web Browsers Are No More</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>28 July 2020</time> +<h1>Web Browsers Are No More</h1> +</header> <article> -<h1>Web Browsers Are No More</h1> -<p class="subtitle">Published on 2020-07-28 19:39:00+02:00, last updated on 2021-07-25 12:56:00+02:00 <p><b>Browsers</b>, we all know what those are, right? We use them every day and it wouldn't be an exaggeration to say that they are one of the most used pieces of software all over the world. They have tremendous impact on not only the diff --git a/writing_minimal_html5_documents_is_fun.html b/writing_minimal_html5_documents_is_fun.html index 996123f..d91c185 100644 --- a/writing_minimal_html5_documents_is_fun.html +++ b/writing_minimal_html5_documents_is_fun.html @@ -10,11 +10,13 @@ <title>Writing Minimal HTML5 Documents is Fun</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>3 August 2020</time> +<h1>Writing Minimal HTML5 Documents is Fun</h1> +</header> <article> -<h1>Writing Minimal HTML5 Documents is Fun</h1> -<p class="subtitle">Published on 2020-08-03 18:18:00+02:00 <p>Yes, I know how it sounds to have both "HTML" and "minimal" in one sentence. I think it's possible to accomplish that and I'll show you how. Before we start, let's set some rules:</p> diff --git a/you_can_serve_static_data_over_http.html b/you_can_serve_static_data_over_http.html index 214fcec..2d65c7d 100644 --- a/you_can_serve_static_data_over_http.html +++ b/you_can_serve_static_data_over_http.html @@ -10,11 +10,13 @@ <title>You Can Serve Static Data Over HTTP</title> -<nav><p><a href="https://ignore.pl">ignore.pl</a></p></nav> +<header> +<nav><a href="https://ignore.pl">ignore.pl</a></nav> +<time>27 January 2022</time> +<h1>You Can Serve Static Data Over HTTP</h1> +</header> <article> -<h1>You Can Serve Static Data Over HTTP</h1> -<p class="subtitle">Published on 2022-01-27 20:00:00+01:00 <p>This will be short. I need to let some steam off and flush this thing out of my mind because it's already hanging around for too long. The story goes like this: we're prototyping small tool for whatever and we're at the point where there is a visible need to store some (most likely) static data. Oh, the thing is in JavaScript by the way. |