From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: New Wiki Software - Please help testing :)
Date: Sun, 02 Jun 2019 23:10:14 +0100 [thread overview]
Message-ID: <5128D798-CCE6-448D-886D-A7A83702BF68@ipfire.org> (raw)
In-Reply-To: <0a7f136e0ad80124311fb81e8c57e50810587447.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
Hi,
> On 1 Jun 2019, at 13:09, ummeegge <ummeegge(a)ipfire.org> wrote:
>
> Hi all,
> am currently not really in this topic but great Michael that you
> figuring something new out :-), thanks for that.
>
> Wanted to ask if there is a possiblity for a language specific syntax
> highlighting like it was before via e.g.
> <code bash>
> code
> </code>
>
> ? Currently we have in the new wiki
>
> ```
> code
> ```
> was far as i could see in the first place…
Yes, markdown supports that too. Just write:
```bash
code
```
I did not test if our wiki highlights the syntax. If not, then the python module I am using does not support this or it isn’t switched on. In either case, let me know :)
-Michael
>
>
> Best,
>
> Erik
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/documentation
next prev parent reply other threads:[~2019-06-02 22:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 13:35 Michael Tremer
2019-05-24 10:58 ` Carlo Fusco
2019-05-24 11:07 ` Carlo Fusco
2019-05-26 10:43 ` Michael Tremer
2019-05-26 8:28 ` Matthias Fischer
2019-05-26 10:54 ` Michael Tremer
2019-05-26 10:55 ` Michael Tremer
2019-06-01 12:09 ` ummeegge
2019-06-02 22:10 ` Michael Tremer [this message]
2019-06-06 3:30 ` Jon Murphy
2019-07-16 16:34 ` Michael Tremer
2019-05-24 16:48 Jon Murphy
2019-05-24 22:03 Jon Murphy
2019-05-27 16:27 ` Michael Tremer
2019-05-27 17:10 ` Matthias Fischer
2019-05-30 14:50 ` Michael Tremer
2019-05-28 3:05 ` Jon Murphy
2019-05-30 14:51 ` Michael Tremer
[not found] <AF378EE0-6263-41AA-A6A0-5442D9C5FCC3@gmail.com>
2019-05-30 14:50 ` Michael Tremer
[not found] <630732F1-CA01-43FD-8EB5-4601C6BF3162@gmail.com>
2019-05-30 17:07 ` Michael Tremer
2019-05-30 17:22 ` Michael Tremer
[not found] <0E1A43E9-96F5-487C-8974-ED25DC70D05B@gmail.com>
2019-05-30 17:31 ` Michael Tremer
[not found] <3917C587-0660-4EA5-A997-081C3A69D045@gmail.com>
2019-05-30 18:17 ` Michael Tremer
[not found] <4BB6A887-545C-4194-B497-16E08FE82231@gmail.com>
2019-05-30 19:04 ` Michael Tremer
2019-05-30 19:23 ` Jon Murphy
2019-05-30 19:24 ` Michael Tremer
2019-05-30 19:30 ` Jon Murphy
2019-06-02 22:13 ` Michael Tremer
[not found] <2CAE7946-C451-4D11-B3C6-9C64CAFC1220@gmail.com>
2019-07-17 15:57 ` Michael Tremer
2019-07-17 22:57 ` Jon Murphy
2019-07-18 10:16 ` Michael Tremer
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=5128D798-CCE6-448D-886D-A7A83702BF68@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=documentation@lists.ipfire.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox