Commands in-line with OC ?

bbigford

One thing I haven't really asked about MangoLassi, is about commands in-line with your post... There's no "code" section like there is in Spiceworks. Does the site just handle it for you and I need to put in special characters? Cause I've tried just copy and paste but haven't gotten any results that makes it look good, and distinguishable. It ends up coming out looking just like everything else I'm typing (black text on a white background). Example of what I'm talking about is @scottalanmiller's recent post on Guac.

tiagom

I use three spaces. Likely more then one way to do it.

like so

bbigford

@tiagom said in Commands in-line with OC ?:

I use three spaces. Likely more then one way to do it.
like so

I guess I don't understand that one about 3 spaces... cause looking through your text in a quote, between 'like' and 'so' there is a single space, with 5 spaces before 'like'.

bbigford

@tiagom said in Commands in-line with OC ?:

I use three spaces. Likely more then one way to do it.
like so

test test

Weird... if you start with 4 spaces (I couldn't get 3 to do anything), it'll work out. There's multiple ways to do it though?

Danp

Markdown reference

Jstear

As Dan stated, you can use markdown in the discussions.

bbigford

@Danp said in Commands in-line with OC ?:

Markdown reference

Oh that's nice... I'll bookmark that. Thanks!

scottalanmiller

It's four spaces before for inline and three backticks on the line before and after a block. Both of these do code style formatting.

dafyre

@scottalanmiller said in Commands in-line with OC ?:

It's four spaces before for inline and three backticks on the line before and after a block. Both of these do code style formatting.

Also, three ~ (tilde) in a row.

Romo

@dafyre said in Commands in-line with OC ?:

@scottalanmiller said in Commands in-line with OC ?:

It's four spaces before for inline and three backticks on the line before and after a block. Both of these do code style formatting.

Also, three ~ (tilde) in a row.

testing ~~~

They work indeed!

bbigford

@Romo said in Commands in-line with OC ?:

@dafyre said in Commands in-line with OC ?:

@scottalanmiller said in Commands in-line with OC ?:

It's four spaces before for inline and three backticks on the line before and after a block. Both of these do code style formatting.

Also, three ~ (tilde) in a row.
testing ~~~
They work indeed!

If you use them at the beginning, in place of spaces, looks like it'll just blank out your reply...

alex.olynyk

This post is deleted!

DustinB3403

DustinB3403

Yea putting in ~~~ just hides it.

alex.olynyk

testing

Romo

@BBigford said in Commands in-line with OC ?:

@Romo said in Commands in-line with OC ?:
@dafyre said in Commands in-line with OC ?:

@scottalanmiller said in Commands in-line with OC ?:

It's four spaces before for inline and three backticks on the line before and after a block. Both of these do code style formatting.

Also, three ~ (tilde) in a row.
testing ~~~
They work indeed!
If you use them at the beginning, in place of spaces, looks like it'll just blank out your reply...

I believe that is because it expects the optional language identifier for syntax highlighting.

dafyre

Hmm... I've never had that problem with mine... but I usually only use it when I'm posting code blocks... ie:

<?PHP
echo "Hello world!";
?>

alex.olynyk

[root@nextcloud ~]# ip a | grep eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    inet 192.168.128.241/24 brd 192.168.128.255 scope global dynamic eth0
[root@nextcloud ~]#
[root@nextcloud ~]# ip r
default via 192.168.128.254 dev eth0  proto static  metric 100
192.168.128.0/24 dev eth0  proto kernel  scope link  src 192.168.128.241  metric 100
[root@nextcloud ~]#

alex.olynyk

Thanks to everyone who contributed in this thread. Very helpful.

DustinB3403

Another really simple way to do this would be to use Notepad++ and just indent the entire code space.

Copy it from notepad++ and paste it to ML.