fixed admonition inner markdown from HTML

This commit is contained in:
Bastian de Byl
2019-12-12 12:38:38 -05:00
parent 7f347f63fe
commit a34c181d08
3 changed files with 18 additions and 20 deletions

View File

@@ -95,20 +95,15 @@ For an STM32F0 project, the context of the `.clang_complete` file would be:
<sub>The above assumes that `libopencm3` is also places within the project <sub>The above assumes that `libopencm3` is also places within the project
directory</sub> directory</sub>
## Example
{{% admonition warning Note %}} {{% admonition warning Note %}}
There is a strange issue that is encountered with non-working completion for new There is a strange issue that is encountered with non-working completion for new
header include statements. header include statements. The workaround for this includes running `M-x irony-server-kill`after new header
<br/> additions to your current working file. Irony's server is clever enough to
<br/> restart itself after a completion request is triggered via `TAB` so this is a
The workaround for this includes running <code>M-x irony-server-kill</code> fairly uninvolved workaround.
after new header additions to your current working file. Irony's server is
clever enough to restart itself after a completion request is triggered via
<code>TAB</code> so this is a fairly uninvolved workaround.
{{% /admonition %}} {{% /admonition %}}
## Example
{{< img src="/static/img/emacs-clang-libopencm3/completion.png" {{< img src="/static/img/emacs-clang-libopencm3/completion.png"
sub="Completion" >}} sub="Completion" >}}

View File

@@ -80,8 +80,8 @@ Once the signature has been verified, the CA can be moved over to
`/usr/share/ca-certificates` to update the list of trusted CA certificates. Do `/usr/share/ca-certificates` to update the list of trusted CA certificates. Do
this via: this via:
+ `sudo update-ca-trust` (_Arch_) + **ArchLinux:** `sudo update-ca-trust`
+ `sudo update-ca-certificates` (_Debian/Ubuntu, RHEL_) + **Debian/Ubuntu, RHEL:** `sudo update-ca-certificates`
{{% admonition tip "CA Path" %}} {{% admonition tip "CA Path" %}}
@@ -93,21 +93,24 @@ On my system the full path to the CA certs is:
Two following parameters should be added to your `~/.gnupg` configuration files: Two following parameters should be added to your `~/.gnupg` configuration files:
### GnuPG Versions >2.1 ### GnuPG Versions >2.1
{{% admonition note "gpg.conf" %}} {{% admonition note "gpg.conf" %}}
```apacheconf ```
keyserver hkps://hkps.pool.sks-keyservers.net keyserver hkps://hkps.pool.sks-keyservers.net
``` ```
{{% /admonition %}} {{% /admonition %}}
{{% admonition note "dirmngr.conf" %}} {{% admonition note "dirmngr.conf" %}}
```apacheconf ```
hkp-cacert /etc/ca-certificates/path/to/CA.pem hkp-cacert /etc/ca-certificates/path/to/CA.pem
``` ```
{{% /admonition %}} {{% /admonition %}}
### GnuPG Versions <2.1 ### GnuPG Versions <2.1
{{% admonition note "gpg.conf" %}} {{% admonition note "gpg.conf" %}}
```apacheconf ```
keyserver hkps://hkps.pool.sks-keyservers.net keyserver hkps://hkps.pool.sks-keyservers.net
keyserver-options ca-cert-file=/path/to/CA/sks-keyservers.netCA.pem keyserver-options ca-cert-file=/path/to/CA/sks-keyservers.netCA.pem
``` ```

View File

@@ -14,11 +14,11 @@ series: turn on the lights!
<!--more--> <!--more-->
{{% admonition info "Note to Windows Users" %}} {{% admonition warning "Windows Users" %}}
This series of write-ups assumes the reader is on a Linux operating This series of write-ups assumes the reader is on a Linux operating
system. Windows users <i>can</i> utilize the <a system. Windows users _can_ utilize the [**Windows Subsystems for
href="https://docs.microsoft.com/en-us/windows/wsl/install-win10"><b>Windows Linux**](https://docs.microsoft.com/en-us/windows/wsl/install-win10) though your
Subsystems for Linux</b></a> though your mileage may vary! mileage may vary!
{{% /admonition %}} {{% /admonition %}}
# Straight to the Chase # Straight to the Chase
@@ -113,7 +113,7 @@ Makefile's variables of things you may want to change:
{{% admonition info "Naming Convention" %}} {{% admonition info "Naming Convention" %}}
As a note to the reader: below I will not refer to the GPIO port or pins using As a note to the reader: below I will not refer to the GPIO port or pins using
the <code>#define</code> friendly names from above. This is purely for the sake the `#define` friendly names from above. This is purely for the sake
of clarity in hopes of avoiding confusion. of clarity in hopes of avoiding confusion.
{{% /admonition %}} {{% /admonition %}}