public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: New wiki - images and syntax highlighting
Date: Sat, 17 Aug 2019 12:17:42 +0200	[thread overview]
Message-ID: <6d9fe27e99aac1c90c4c748eb65de32b803e2b65.camel@ipfire.org> (raw)
In-Reply-To: <5d556e63543f636e511993db234f64e92fdb156b.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

Hi all,
just another one on the syntax highlighting.

If an initscript will be code tagged with a simple

```
#!/bin/sh
script content
```

the wiki shows the line numbers and get out of the format. This could
be fixed with the syntax bash highlighting like it is known

```bash
#!/bin/sh
script content
```

May this helps to find some bugs there.

Best,

Erik



On Fr, 2019-08-16 at 19:56 +0200, ummeegge wrote:
> Hi all,
> tried to fix a couple of wikis now and have some questions.
> 
> 1) In the old wiki was a picture manager which i currently miss in
> the
> new one. How could be overseen which pictures are available to delete
> unused ones or upload new ones or relink existing ones ?
> 
> 2) The syntax highlighting seems to be a little buggy. 
> a) For example a
> 
> ```bash
> ...
> ...
> 
> ```
> marks sometimes bash commands (in that specific case 'cd') in red,
> the
> same command in another bash code tag in regular white, it seems a
> little inconsitent.
> 
> b) Also in the same bash code highlighting sometimes line numbers
> appears and the whole code block get out of the format.
> 
> c) Also in the same bash code highlighting some numbers e.g.
> '192.168'
> disappears cause it uses the page background color. May this happens
> also with perl or another language which i haven´t checked until now.
> 
> 
> Some things from here.
> 
> Best,
> 
> Erik
> 
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> https://lists.ipfire.org/mailman/listinfo/documentation


      reply	other threads:[~2019-08-17 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 17:56 ummeegge
2019-08-17 10:17 ` ummeegge [this message]

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=6d9fe27e99aac1c90c4c748eb65de32b803e2b65.camel@ipfire.org \
    --to=ummeegge@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