From d9e7ce3e73cf7eff9ec6ac4398713c8872ec5c4c Mon Sep 17 00:00:00 2001
From: JozanLeClerc <bousset.rudy@gmail.com>
Date: Wed, 20 Apr 2022 13:06:33 +0200
Subject: New content, css update

---
 css/site.css              |  22 ++++--
 docs/dergods_style_v1.ms  | 169 ----------------------------------------------
 docs/dergods_style_v1.org | 104 ----------------------------
 docs/lowbat.org           |  62 -----------------
 files.html                |  10 +--
 img/tp_turtle.jpg         | Bin 0 -> 40110 bytes
 index.html                |  13 ++--
 projects/lowbat.html      |  46 -------------
 using.html                |  45 ++++++++----
 9 files changed, 63 insertions(+), 408 deletions(-)
 delete mode 100644 docs/dergods_style_v1.ms
 delete mode 100644 docs/dergods_style_v1.org
 delete mode 100644 docs/lowbat.org
 create mode 100644 img/tp_turtle.jpg

diff --git a/css/site.css b/css/site.css
index 65c3373..82b391d 100644
--- a/css/site.css
+++ b/css/site.css
@@ -12,7 +12,7 @@
  * ========================
  *
  * jozanofastora.xyz: css/site.css
- * Wed Apr 20 00:14:30 CEST 2022
+ * Wed Apr 20 12:52:41 CEST 2022
  * Joe
  *
  * The style
@@ -161,7 +161,7 @@ div.body-contents h1 {
 	text-align: left;
 	padding: 0em 0em 0.25rem 0em;
 	margin: 0pt;
-	margin-top: 1em;
+	margin-top: 0.75em;
 	color: #9d0006;
 	border-bottom: 2px solid #9d0006;
 }
@@ -172,7 +172,7 @@ div.body-contents h2 {
 	text-align: left;
 	padding: 0em 0em 0.25rem 0em;
 	margin: 0pt;
-	margin-top: 2em;
+	margin-top: 1em;
 	color: #9d0006;
 	border-bottom: 1px solid #9d0006;
 }
@@ -183,7 +183,7 @@ div.body-contents h3 {
 	text-align: left;
 	padding: 0em 0em 0.25rem 0em;
 	margin: 0pt;
-	margin-top: 2em;
+	margin-top: 1em;
 	color: #9d0006;
 }
 
@@ -193,7 +193,7 @@ div.body-contents h4 {
 	text-align: left;
 	padding: 0em 0em 0.20rem 0em;
 	margin: 0pt;
-	margin-top: 2em;
+	margin-top: 1em;
 }
 
 div.body-contents b {
@@ -203,6 +203,7 @@ div.body-contents b {
 
 div.body-contents li {
 	display: list-item;
+	padding: 0.10rem 0pt 0.10rem 0pt;
 }
 
 div.body-contents ul {
@@ -243,6 +244,17 @@ div.body-contents pre {
 	border: 1px solid #9d0006;
 }
 
+div.figure
+{
+	padding: 1em;
+}
+
+div.figure p
+{
+	font-size: 90%;
+	text-align: center;
+}
+
 div.body-contents pre.src {
 	background-color: #3c3836;
 	color: #ebdbb2;
diff --git a/docs/dergods_style_v1.ms b/docs/dergods_style_v1.ms
deleted file mode 100644
index fff2c0a..0000000
--- a/docs/dergods_style_v1.ms
+++ /dev/null
@@ -1,169 +0,0 @@
-.defcolor blue    rgb 0.1f 0.1f 1.0f
-.defcolor bsdred  rgb #990000
-.defcolor codered rgb #600000
-.defcolor grey    rgb #aaaaaa
-.defcolor black   rgb #000000
-.color
-.de bsdr
-.gcolor bsdred
-..
-.de endc
-.gcolor
-..
-.de xa
-.XA \\$1
-.ps 12p
-.B "\m[bsdred]\\$2\m[]" \\$3 \\$4
-..
-.de b
-.B "\m[bsdred]\\$1\m[]" \\$2 \\$3
-..
-.de code
-.gcolor bsdred
-.CW \\$1 \\$2 \\$3
-.gcolor
-..
-.de nh1
-.gcolor bsdred
-.NH 1
-.ps 14p
-\\$1
-.gcolor
-..
-.de nh2
-.gcolor bsdred
-.NH 2
-.ps 13p
-\\$1
-.gcolor
-..
-.de bu
-.IP \(bu 2
-..
-.
-.
-.
-.
-.nr PS 12p
-.nr PO 1.0i
-.nr LL 6.5i
-.RP no
-.P1
-.ND
-.
-.
-.
-.
-.gcolor black
-.bsdr
-.TL
-.LG
-.ps 17p
-Dergods' Style and good practices for C/C++ projects
-.endc
-.AU
-.ps 15p
-Joe
-.AI
-42 Lyon Auvergne-Rhône-Alpes
-.
-.
-.XS 1
-.ps 12p
-.b "1. Introduction"
-.xa 1 "2. Projects and version control"
-.xa 1 "	2.1 Directories"
-.XE
-.bsdr
-.PX
-.endc
-.
-.
-.nh1 "Introduction"
-.PP
-The following is a description of
-.b "Dergods' Style"
-code and project
-formatting to put in use if you work on Dergods' Realm-related code or if you
-just need a personal good-looking norm to improve your code readablity. It
-is heavily inspired by
-.b FreeBSD® 's
-.pdfhref W -D \
-https://www.freebsd.org/cgi/man.cgi?query=style&apropos=0&sektion=0&\
-manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html \
--A \m[black],\m[] \
-\f(CW\m[codered]style(9)\m[]\f[]
-.gcolor
-with some changes.
-.nh1 "Projects and version control"
-.nh2 "Directories"
-.RS
-.bu
-Working on a
-.b program :
-.RS
-.bu
-All
-.b source
-and
-.b "header files"
-should be in the
-.code src/
-directory.
-.bu
-Necessary
-.b "media files"
-such as images, sounds, fonts, etc... Necessary to the program execution
-should be in the
-.code media/
-directory.
-.bu
-Compilation-generated
-.b "object files"
-should be located in the
-.code obj/
-directory.
-.bu
-.b Sub-programs
-or
-.b utilities
-should be located in the
-.code utils/
-directory.
-.bu
-Optional
-.b "man page(s)"
-can be made for the project and its specularities and should be located in the
-.code man/
-directory.
-.RE
-.bu
-Working on a
-.b library :
-.RS
-.bu
-All
-.b "source files"
-should be located in the
-.code src/
-directory.
-.bu
-Compilation-generated
-.b "object files"
-should be located in the
-.code obj/
-directory.
-.bu
-Non-optional
-.b "man pages"
-for every function intended to be used externally
-should be located in the
-.code man/
-directory.
-.bu
-.b "Header files"
-should be located in the
-.code include/
-directory.
-.RE
-.RE
diff --git a/docs/dergods_style_v1.org b/docs/dergods_style_v1.org
deleted file mode 100644
index 7d27312..0000000
--- a/docs/dergods_style_v1.org
+++ /dev/null
@@ -1,104 +0,0 @@
-#+TITLE: Dergods' Style and good practices for C/C++
-#+AUTHOR: Joe
-#+DATE: v0.1
-#+LATEX_CLASS: article
-#+LATEX_CLASS_OPTIONS: [a4paper]
-#+LATEX_HEADER: \usepackage[margin=1.0in]{geometry}
-#+LATEX_HEADER: \usepackage[utf8]{inputenc}
-#+LATEX_HEADER: \usepackage[dvipsnames]{xcolor}
-#+LATEX_HEADER: \definecolor{mypink1}{rgb}{0.858, 0.188, 0.478}
-#+LATEX_HEADER: \let\OldTexttt\texttt
-#+LATEX_HEADER: \renewcommand{\texttt}[1]{%
-#+LATEX_HEADER:     \OldTexttt{%
-#+LATEX_HEADER:         \colorbox{gray}{%
-#+LATEX_HEADER:             \color{black} #1%
-#+LATEX_HEADER:         }%
-#+LATEX_HEADER:     }%
-#+LATEX_HEADER: }%
-
-* Introduction
-The following is a description of Dergods' Style code and project
-formatting to put in use if you work on Dergods' Realm-related code or if you
-just need a personnal good-looking norm to improve your code readablity. It
-is heavily inspired by BSD [[https://www.freebsd.org/cgi/man.cgi?query=style&apropos=0&sektion=0&manpath=FreeBSD+12.1-RELEASE+and+Ports&arch=default&format=html][style(9)]],
-with some changes.
-
-* Projects and version control
-** Directories
-   - Working on a *program*:
-      - All source and header files should be in the ~src/~ directory.
-      - Necessary media files such as images, sounds, fonts, etc... To the program execution should be in the ~media/~ directory.
-      - Compilation-generated object files should be located in the ~obj/~ directory.
-      - Sub-programs or utilities should be located in the ~tools/~ directory.
-      - An optional man page can be made for the program and should be located in the ~man/~ directory.
-   - Working on a *library*:
-      - All source files should be located in the ~src/~ directory.
-      - Compilation-generated object files should be located in the ~obj/~ directory.
-      - Non-optional man pages for every major function should be located in the ~man/~ directory.
-      - Header files should be located in the ~include/~ directory.
-
-** Files
-   - *C* sources and headers files should be of the ~.c~ and ~.h~ extensions.
-   - *C++* sources and header files should be of the corresponding ~.cxx~ / ~.hxx~ or ~.cc~ / ~.hh~ extensions unless the project is Microsoft™ Windows®-compatible only, then extensions should be ~.cpp~ / ~.hpp~. If the project is compatible with any UNIX®-like operating system, ~.cxx~ / ~.hxx~ or ~.cc~ / ~.hh~ should be the prefered extensions.
-   - Compilation-generated object files should be of the ~.c.o~, ~.cxx.o~, ~.cc.o~ or ~.cpp.o~ corresponding to the correct extensions.
-   - All files should follow the UNIX® case formatting, including only lowercase alphabetical letters (~a-z~), underscores (~_~) and dots (~.~). Numbers are not allowed.
-   - Compilation-generated object files should have the same pre-extension basename as its the corresponding source file.
-   - Working on a *program*, every source file should have its own header file. The pre-extension basenames names should be corresponding. Orphan header files are tolerated.
-   - Source files should be composed of two parts:
-      - An index letter followed by an underscore (~_~). An index letters list should be found in an info comment under the main function. The index letter should be consistent.
-      - A single explicit word describing the file's purpose.
-         - Example of what a source file should look like: ~g_inventory.cxx~. Its corresponding header file should be ~g_inventory.hxx~ and its compilation-generated object file should be ~g_inventory.cxx.o~. In our case, ~g_~ may be described under the main function as gameplay-related.
-   - ~.txt~ format is pointless and forbidden.
-   - Don't forget a LICENSE and a README. Prefer org-mode or markdown for README if the project is going to be published on platforms such as GitLab or GitHub. Therefore extensions should be ~.org~ or ~.md~. You can add a copy of the README without extension properly formatted to be displayed in a terminal or platforms that do not handle org-mode or markdown.
-
-** Makefile
-   - The project should always contain at least one makefile.
-   - There can be more more than one makefile per projects but only one by subdirectories.
-   - The makefile should be in lowercases only with a capital "M": ~Makefile~.
-   - The main makefile should contain at least the 3 rules:
-      - ~all~
-      - ~clean~
-      - ~install~
-   - Makefiles should not relink upon successful compilation.
-   - The main makefile should contain rules to compile any sub makefiles with the ~tools~ rule.
-   - All compiled binaries and libraries should be in the root of the project repository, next to the main makefile.
-
-** Compilation
-   - The compiler of choice for released binaries should be ~clang~ for C and ~clang++~ for C++.
-   - The program should compile with ~gcc~ or ~g++~ as well, so test those often.
-   - C standard of choice should be ~C89~.
-   - C++ standard of choice should be ~C++98~.
-   - ~C99~ is tolerated sometimes but ~C89~ should always be this first choice.
-   - Standard compiler flags should be:
-      - ~-std=c89~ for C or ~-std=c99~ for C++.
-      - ~-Wall~
-      - ~-Wextra~
-      - ~-Werror~
-      - ~-pedantic~
-   - When including external libraries, additional ~-Wno-~\x X flags may be added to mute external warnings generated by them, for example if one library uses a more recent standard.
-      - Example: ~-Wno-long-long~ if your library uses ~long long~'s. You will then have to be careful not using ~long long~'s in your code.
-   - Released binaries should never be compiled with ~-g~\x X options.
-   - The program should run without any issue with the ~-fsanitize=address~ or ~-fsanitize=memory~ options engaged. Test those often.
-   - Dynamic linking is prefearable.
-
-** Editors
-No specific editor should be imposed over another, you should always pick the
-one you feel the more comfortable with. However some of them are malicious
-spyware that should never be recommanded.
-
-Here is a non-exhaustive list of recommanded or banished programs:
-
-   - *Recommanded*:
-      - vi® / vim® and variants
-      - GNU Emacs®
-      - ee®
-      - joe® and variants
-   - *banished*:
-      - Microsoft™ VSCode®
-      - Microsoft™ Atom®
-      - JetBrains™ IntelliJ® variants
-
-** Version control
-   - Prefer ~fossil~ over ~git~. Using ~fossil~'s builtin function to mirror repository to ~git~ is fine.
-   - The repository should only contain files necessary to the compilation, execution or documentation of the program.
-   - The repository root should not contain anything else than the project's main makefile, LICENSE, README and subdirectories.
diff --git a/docs/lowbat.org b/docs/lowbat.org
deleted file mode 100644
index a2fc8a5..0000000
--- a/docs/lowbat.org
+++ /dev/null
@@ -1,62 +0,0 @@
-#+TITLE: lowbat - lightweight low battery notifier
-
-* Why lowbat?
-   I've been using minimalist OS installations for work, personnal computing
-and playing video games for a while now. I used [[https://www.archlinux.org/][Arch Linux]], I still use
-[[https://gentoo.org/][Gentoo Linux]] - which is by far my favorite Linux distribution - as a desktop
-OS, and now I am using [[https://www.freebsd.org/][FreeBSD]] on my workstation.
-
-Those operating systems and distributions basically come with a kernel,
-coreutils, a shell and that's pretty much it. Everything else has to be
-installed manually. I love this philosophy, the simplicity behind it and the
-fact that you know exactly what's on your system at any moment.
-
-As window managers, I used [[http://dwm.suckless.org/][dwm]] for a while, and I am now using [[https://github.com/baskerville/bspwm][bspwm]]. They
-are ultra-fast, very lightweight and do not bring extra bloatware to my systems.
-I do not use a status bar as well, I like my applications to use the full screen
-space available.
-
-A big problem for me with this setup for me was that they do not come with some
-kind of warning or notification system, like fancier desktop environments would,
-when my laptop battery is low. That also was before I started using *Emacs*,
-discovering the battery level indicator in the modeline. Ultimatly the
-frustration was too important when the computer kept shutting down in
-the middle of important work too many time. Then I decided to create *lowbat*
-to cure this issue.
-
-* History of lowbat
-  It started as a very short ~dash~ shell (get [[https://github.com/tklauser/dash][dash]] here) script that was
-working fine but I wanted to experiment a little bit with this. It turned into
-a ~C++~ program, which is still the case for the GNU/Linux version.
-Switching to FreeBSD, I exerimented again by turning it into an
-~x64 assembly~ program, following the *Intel* syntax. In that way *lowbat* is
-even more lightweight and consumes less battery power.
-These days, I am rewriting it in the *AT&T* syntax.
-
-* How it works
-** libnotify lowbat
-  The principle of *lowbat* is rather simple. When it's running in the
-background, it checks every 4 minutes whether your battery is above 15%.
-If that is the case, it sleeps for another 4 minutes. When your battery runs
-bellow 15%, *lowbat* checks your battery level every 20 seconds as well as
-sending you a *notification* using ~libnotify~. You can display live
-notifications on your desktop using ~dunst~ for example, as well as many
-other I'm sure.
-
-#+CAPTION: A notification generated by lowbat, displayed by dunst
-#+NAME: fig:lowbat-example
-[[../img/lowbat-01.jpg]]
-
-** espeak lowbat
-   *lowbat* also has an option to send a custom voice message to the use
-using ~espeak~. Very handy if you are not in front of your computer or
-if you want to bring joy to this dramatic event.
-
-** unknown lowbat
-   Sadly, I wasn't able to test lowbat on machines with more that one
-battery. My call is that it will only warn you for the /first/ battery,
-but I can't be sure. Try it and tell me!
-
-* Links to lowbat
-   - GNU/Linux: [[https://github.com/JozanLeClerc/lowbat][lowbat's GitHub GNU/Linux repository]]
-   - BSD: [[https://github.com/JozanLeClerc/lowbat-bsd][lowbat's GitHub BSD repository]]
diff --git a/files.html b/files.html
index 33640d9..048dbff 100644
--- a/files.html
+++ b/files.html
@@ -46,13 +46,15 @@
 				<p>
 					These are some files I give to you for free:
 				</p>
-				<ul>
+				<ul style="list-style: none;">
 					<li>
-						<a href="files/wp.tar.xz">
-							wp.tar.xz
-						</a>
+						<a href="files/wp.tar.xz">wp.tar.xz</a>
 						- my wallpapers, most are from /wg
 					</li>
+					<li>
+						<a href="files/cv.pdf">cv.pdf</a>
+						- my CV, if that's of any use to you
+					</li>
 				</ul>
 			<footer>
 				<p>
diff --git a/img/tp_turtle.jpg b/img/tp_turtle.jpg
new file mode 100644
index 0000000..54aba7a
Binary files /dev/null and b/img/tp_turtle.jpg differ
diff --git a/index.html b/index.html
index 6b2fa02..d22b5f7 100644
--- a/index.html
+++ b/index.html
@@ -12,7 +12,7 @@
  * ========================
  *
  * jozanofastora.xyz: index.html
- * Mon Apr 18 19:37:18 CEST 2022
+ * Wed Apr 20 12:52:46 CEST 2022
  * Joe
  *
  * The home page
@@ -58,10 +58,13 @@
 					I work on various personal projects beside that. Also I like
 					rocket science and astrophysics.
 				</p>
-				<p>
-					A picture of me IRL at work:
-				</p>
-				<img src="img/me.jpg" alt="me.jpg" width="325">
+				<div class="figure">
+					<p>
+						<img src="img/me.jpg" alt="me.jpg" width="325">
+					<p>
+						A picture of me IRL at work
+					</p>
+				</div>
 				<p>
 					I play a lot of music too. That's pretty much all there is.
 				</p>
diff --git a/projects/lowbat.html b/projects/lowbat.html
index bd436d5..7f8aab2 100644
--- a/projects/lowbat.html
+++ b/projects/lowbat.html
@@ -187,52 +187,6 @@
   .org-svg { width: 90%; }
   /*]]>*/-->
 </style>
-<script type="text/javascript">
-/*
-@licstart  The following is the entire license notice for the
-JavaScript code in this tag.
-
-Copyright (C) 2012-2019 Free Software Foundation, Inc.
-
-The JavaScript code in this tag is free software: you can
-redistribute it and/or modify it under the terms of the GNU
-General Public License (GNU GPL) as published by the Free Software
-Foundation, either version 3 of the License, or (at your option)
-any later version.  The code is distributed WITHOUT ANY WARRANTY;
-without even the implied warranty of MERCHANTABILITY or FITNESS
-FOR A PARTICULAR PURPOSE.  See the GNU GPL for more details.
-
-As additional permission under GNU GPL version 3 section 7, you
-may distribute non-source (e.g., minimized or compacted) forms of
-that code without the copy of the GNU GPL normally required by
-section 4, provided you include this license notice and a URL
-through which recipients can access the Corresponding Source.
-
-
-@licend  The above is the entire license notice
-for the JavaScript code in this tag.
-*/
-<!--/*--><![CDATA[/*><!--*/
- function CodeHighlightOn(elem, id)
- {
-   var target = document.getElementById(id);
-   if(null != target) {
-     elem.cacheClassElem = elem.className;
-     elem.cacheClassTarget = target.className;
-     target.className = "code-highlighted";
-     elem.className   = "code-highlighted";
-   }
- }
- function CodeHighlightOff(elem, id)
- {
-   var target = document.getElementById(id);
-   if(elem.cacheClassElem)
-     elem.className = elem.cacheClassElem;
-   if(elem.cacheClassTarget)
-     target.className = elem.cacheClassTarget;
- }
-/*]]>*///-->
-</script>
 <html>
 	<head>
 		<title>Joe's own website - project: lowbat</title>
diff --git a/using.html b/using.html
index 7ecc991..d3a880a 100644
--- a/using.html
+++ b/using.html
@@ -12,7 +12,7 @@
  * ========================
  *
  * jozanofastora.xyz: using.html
- * Wed Apr 20 00:14:36 CEST 2022
+ * Wed Apr 20 12:52:52 CEST 2022
  * Joe
  *
  * Some of the things I use for computing
@@ -59,7 +59,10 @@
 				</p>
 				<h2>Software</h2>
 				<p>
-					<img src="img/neofetch.jpg" alt="neofetch.jpg" width="600">
+					<div class="figure">
+						<p><img src="img/neofetch.jpg" alt="neofetch.jpg" width="600"></p>
+						<p>My neofetch</p>
+					</div>
 					<ul>
 						<li>
 							<h4>Text editing</h4>
@@ -133,8 +136,16 @@
 				</p>
 				<h2>Hardware</h2>
 				<p>
-					My computer is a ThinkPad T530 and I love it. Here is
-					the hardware config:
+					My computer is a ThinkPad T530 and I love it. Unfortunately
+					I bought it used and the previous owner forgot to tell me
+					there was an ugly turtle tattooed rear side. This is my
+					only complain. It's not too visible but it's there. The deal
+					was quick, there was not much lighting and the seller opened
+					the screen right away, so I didn't see that ugly turtle
+					until I was home with my new computer.
+				</p>
+				<p>
+					Here is the hardware config:
 					<ul>
 						<li>Intel i5-3320M 2.60GHz, 4 threads</li>
 						<li>8GB RAM</li>
@@ -147,26 +158,34 @@
 					my media consumption with it so I consider myself a
 					tech-happy guy.
 				</p>
+				<div class="figure">
+					<p><img src="img/tp_turtle.jpg" alt="tp_turtle.jpg" width="450"></p>
+					<p>The ugly turtle</p>
+				</div>
 				<h3>Other notable hardware</h3>
 				<p>
-					I have a RaspberryPi 4 I received from a friend as a
+					I have a <b>RaspberryPi 4</b> I received from a friend as a
 					christmas gift. It runs FreeBSD of course. I use it to
 					learn I2C/GPIO programming with a bit of electronics. I am
 					looking for some projects for it.
-					<br>
-					I have a Casio F-91W watch gifted by a friend too so I
-					never loose time.
-					<br>
+				</p>
+				<p>
+					I have a <b>Casio F-91W</b> watch gifted by a friend too so
+					I never loose time. Adult people tend to show more respect
+					towards people wearing watches too, just like they do with
+					people with wives or kids, so there's that.
+				</p>
+				<p>
 					Last piece of hardware worth noting is my keyboard: a
 					<a href="https://mechanicalkeyboards.com/shop/index.php?l=product_list&c=169">
 						Leopold
 					</a>
-					FC900R PD with Cherry MX Brown switches. It is so
-					good I plan on buying maybe 5 of them in the future so I
+					<b>FC900R PD</b> with <b>Cherry MX Brown</b> switches. It is
+					so good I plan on buying maybe 5 of them in the future so I
 					don't need to worry and I can just use it the same model
 					for all my life. I might check some of the
-					<a href="https://www.pckeyboard.com/">Unicomp</a> Model M
-					remake when they are available again.
+					<a href="https://www.pckeyboard.com/">Unicomp</a>
+					<b>Model M</b> remakes when they are available again.
 				</p>
 			</div>
 			<footer>
-- 
cgit v1.2.3