From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Samuel Falvo II <sam.falvo@gmail.com>,
Libre-RISCV General Development
<libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Markdown on the wiki?
Date: Wed, 15 Jul 2020 11:05:01 +0100
Message-ID: <CAPweEDySjucO9pRDOCYmnaeTtoE2RFpo6+++hTskGiLMWBtsow@mail.gmail.com> (raw)
In-Reply-To: <CAEz=somu-i6og_eQZ51WbbLSe8spGAzEHiXUiDAY6=gdx1vFOg@mail.gmail.com>
On Wed, Jul 15, 2020 at 2:40 AM Samuel Falvo II <sam.falvo@gmail.com> wrote:
>
> Hi Luke,
>
> I wrote up a summary of what I've learned by reviewing the source
> code. But, when I view the notes that I've written[1],
> https://libre-soc.org/Documentation/notes_on_formal_proofs/
excellent. i'll find a location for it. thank you for creating that page.
> the formatting
> of fixed-width code snippets enclosed in `backticks` results in the
> snippets being on a completely new HTML division, as if I'd written
> ```backticks``` instead.
yes. there's a bug where fixed-width code following bullet-points
does not get marked up as fixed-width. to sort that i had to change
the css:
https://libre-soc.org/local.css
> Is this a limitation of ikiWiki that cannot be easily fixed?
no - it's just a matter of someone having the time to properly investigate.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next parent reply index
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEz=somu-i6og_eQZ51WbbLSe8spGAzEHiXUiDAY6=gdx1vFOg@mail.gmail.com>
2020-07-15 10:05 ` Luke Kenneth Casson Leighton [this message]
2020-07-15 10:47 ` Luke Kenneth Casson Leighton
2020-07-15 17:12 ` Luke Kenneth Casson Leighton
2020-07-18 1:19 ` Samuel Falvo II
2020-07-18 2:39 ` Luke Kenneth Casson Leighton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPweEDySjucO9pRDOCYmnaeTtoE2RFpo6+++hTskGiLMWBtsow@mail.gmail.com \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.org \
--cc=sam.falvo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git