Commands in-line with OC ?

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.

scottalanmiller

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

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.

Now that we know it's just three back ticks before and aft, that's easier than the indent method.

DustinB3403

Really

'''
testing
'''

scottalanmiller

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

Really

'''
testing
'''

You have to know what backticks are, of course, for it to work.

DustinB3403

test

So the ``` and ```` on a individual paragraph works.

bbigford

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

test 
So the ``` and ```` on a individual paragraph works.

test using ``` before and after "test"

bbigford

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

test 
So the ``` and ```` on a individual paragraph works.

Hmm, ``` doesn't look the same as four spaces for me. Weird.

bbigford

Fully aware I'm doing this...