Browse Source

fix line breaks and some left-over html tags

max.mehl 4 months ago
parent
commit
70e56508d8
No account linked to committer's email address

+ 0
- 4
config.toml View File

@@ -7,10 +7,6 @@ theme = [ "hugo-sustain", "hugo-cloak-email", "hugo-mastodon-comments", "hugo-sn
7 7
 codeFences = true
8 8
 style = "emacs"
9 9
 
10
-[blackfriday]
11
-# preserves linebreaks, and transforms to <br />
12
-extensions = [ "" ]
13
-
14 10
 [permalinks]
15 11
   blog = "/blog/:year/:slug"
16 12
 

+ 1
- 1
content/blog/2014-01-mounting-a-sftp-storage-in-gnu-linux.md View File

@@ -90,7 +90,7 @@ Now that you know how (and that) the system works, we will make it easier. Of co
90 90
 Host server1
91 91
   HostName server1.net
92 92
   Port 22
93
-  User client</pre>
93
+  User client
94 94
 ```
95 95
 
96 96
 Save it and try to use this shortcut. It also works for normal SSH connection like ‚_ssh server1_‚. For the _Host_ variable, you could use any name you can remember easily, for instance _privateserver_.

+ 2
- 2
content/blog/2016-02-switching-my-code-from-gitweb-to-gogs.md View File

@@ -24,14 +24,14 @@ Host src.mehl.mx
24 24
   HostName src.mehl.mx
25 25
   User your-username
26 26
   IdentityFile ~/.ssh/id_rsa_gogs
27
-  IdentitiesOnly yes</pre>
27
+  IdentitiesOnly yes
28 28
 ```
29 29
 
30 30
 This forces your client to use the Gogs-specific SSH key for every connection to [src.mehl.mx](https://src.mehl.mx) – and not the default one for this IP/server. However, this is only a problem for you as the administrator, not for other users. It took some time for me to find that out :)
31 31
 
32 32
 **Update**: It’s best to use the built-in server if you cannot create a separate user for Gogs and if you depend on using the default `~/.ssh/authorized_keys` file for other use cases than gogs (e.g. to log in). The problems lies in Gogs behaviour: sometimes it rewrites the `authorized_keys` file without being asked to do so, and as a result you cannot log into the user’s account anymore via SSH! To make the solution easy for you, here’s the excerpt of my `custom/conf/app.ini` file:
33 33
 
34
-```ini
34
+```text
35 35
 [server]
36 36
 START_SSH_SERVER = true
37 37
 SSH_PORT     = ${DEDICATED_SSH_PORT_FOR_GOGS}

+ 4
- 2
content/blog/2016-11-build-fsfe-websites-locally.md View File

@@ -43,7 +43,9 @@ git clone https://src.mehl.mx/mxmehl/fsfe-local-build.git ~/subversion/fsfe/loca
43 43
 
44 44
 Now we take care of `trunk`. In case you already have a copy of `trunk` on your computer, you can use this location, but please do a `svn up` beforehand and be sure that the output of `svn status` is empty (so no new or modified files on your side). If you don’t have `trunk` yet, download the repository to the proposed location:
45 45
 
46
-<pre class="lang:default highlight:0 decode:true">svn --username $YourFSFEUsername co https://svn.fsfe.org/fsfe-web/trunk ~/subversion/fsfe/fsfe-web/trunk</pre>
46
+```bash
47
+svn --username $YourFSFEUsername co https://svn.fsfe.org/fsfe-web/trunk ~/subversion/fsfe/fsfe-web/trunk
48
+```
47 49
 
48 50
 ### 2. Build full website
49 51
 
@@ -106,7 +108,7 @@ Now you can test whether the webserver is correctly configured. To start a tempo
106 108
 lighttpd -Df ~/subversion/fsfe/local-build/lighttpd-fsfe.conf
107 109
 ```
108 110
 
109
-Until you press Ctrl+C, you should be able to open your local FSFE website in any browser using the URL http://localhost:5080. For example, open the URL <http://localhost:5080/contribute/contribute.en.html> in your browser. You should see basically the same website as the original [fsfe.org website][5]. If not, double-check the paths, if the lighttpd process is still running, or if the full website build is already finished.
111
+Until you press Ctrl+C, you should be able to open your local FSFE website in any browser using the URL `http://localhost:5080`. For example, open the URL `http://localhost:5080/contribute/contribute.en.html` in your browser. You should see basically the same website as the original [fsfe.org website][5]. If not, double-check the paths, if the lighttpd process is still running, or if the full website build is already finished.
110 112
 
111 113
 ### 4. Single page build script
112 114
 

+ 1
- 1
content/blog/2017-02-i-love-astroid-ilovefs.md View File

@@ -17,7 +17,7 @@ You cannot imagine how long I’ve waited to write this blog post. Normally I’
17 17
 
18 18
 {{< figure src="/img/blog/astroid-ilovefs.jpg" class="text-center medium" caption="Hugo and me declaring our love to astroid" >}}
19 19
 
20
-_**Update February 2018**: Meanwhile I have <a href="https://src.mehl.mx/mxmehl/mail-config">published my mail config</a> incl. astroid, notmuch, offlineimap etc. It is a rather complicated and special setup but perhaps it will help you._
20
+_**Update February 2018**: Meanwhile I have [published my mail config](https://src.mehl.mx/mxmehl/mail-config) incl. astroid, notmuch, offlineimap etc. It is a rather complicated and special setup but perhaps it will help you._
21 21
 
22 22
 Okay, maybe I’ll add two or three words to explain why I am so grateful to the authors of this awesome Free Software application. Firstly, I should note that until ~6 months ago I have used Thunderbird – extended with lots of add-ons but still a mail user agent that most of you will know. But with each new email and project it became obvious to me that I have to find a way to organise my tenthousands of mails in a better way: not folder-based but tag-based, but not to the expense of overview and comfort.
23 23
 

+ 9
- 9
content/contact.md View File

@@ -3,15 +3,15 @@ title: Contact
3 3
 page: true
4 4
 ---
5 5
 
6
-Email FSFE: {{< cloakemail address="max.mehl@fsfe.org" >}}<br />
7
-Email private: {{< cloakemail address="mail@mehl.mx" >}}<br />
8
-XMPP: {{< cloakemail address="max.mehl@jabber.fsfe.org" protocol="xmpp" >}}<br />
6
+Email FSFE: {{< cloakemail address="max.mehl@fsfe.org" >}}\
7
+Email private: {{< cloakemail address="mail@mehl.mx" >}}\
8
+XMPP: {{< cloakemail address="max.mehl@jabber.fsfe.org" protocol="xmpp" >}}
9 9
 
10
-Mastodon: [@mxmehl@mastodon.social](https://mastodon.social/@mxmehl)<br />
11
-Twitter: [@mxmehl](https://twitter.com/mxmehl)<br />
12
-Weblog: [mehl.mx/blog](/blog)<br />
13
-Diaspora: [mxmehl@diasp.eu](https://diasp.eu/u/mxmehl)<br />
14
-LinkedIn: [mxmehl ](https://linkedin.com/in/mxmehl)<br />
10
+Mastodon: [@mxmehl@mastodon.social](https://mastodon.social/@mxmehl)\
11
+Twitter: [@mxmehl](https://twitter.com/mxmehl)\
12
+Weblog: [mehl.mx/blog](/blog)\
13
+Diaspora: [mxmehl@diasp.eu](https://diasp.eu/u/mxmehl)\
14
+LinkedIn: [mxmehl](https://linkedin.com/in/mxmehl)
15 15
 
16
-GnuPG: [0x371E2E92](https://up.mehl.mx/mehl-current.pub.asc)<br />
16
+GnuPG: [0x371E2E92](https://up.mehl.mx/mehl-current.pub.asc)\
17 17
 OMEMO: [OMEMO Fingerprints](https://up.mehl.mx/mehl-omemo.asc)

+ 4
- 6
content/impressum.md View File

@@ -10,13 +10,11 @@ sitemap_hide: true
10 10
 
11 11
 Angaben gemäß § 5 TMG:
12 12
 
13
-Max Mehl
14
-Singener Straße 35a
15
-78256 Steißlingen
16
-E-Mail: {{< cloakemail address="mail@mehl.mx" >}}
13
+Max Mehl\
14
+Singener Straße 35a\
15
+78256 Steißlingen\
16
+E-Mail: {{< cloakemail address="mail@mehl.mx" >}}\
17 17
 Telefon: +49 7738 2031061
18
-Ust-ID: DE280794669
19
-
20 18
 
21 19
 ## Haftungsausschluss:
22 20
 

Loading…
Cancel
Save