D - test
- Vladimir Panteleev (1/1) Feb 17 2012 test
- Kevin Bowling (3/4) Feb 29 2012 Test
- Nick (1/1) Apr 16 2012 let's test if this is working!
- Alexandr Druzhinin (2/3) May 15 2012 yet another test
- Dejan Lekic (4/7) May 25 2012 Definitely works. :)
- tytower (4/4) Aug 11 2012 This popped up on my desk today
- r_m_r (2/3) Nov 28 2012 test
- Vladimir Panteleev (2/5) Dec 06 2012 viagra-test-123
- Chad Joan (4/5) Jan 27 2013 I'm testing what my posts from the web-interface look like so I
- Chad Joan (3/8) Jan 27 2013 Can I distort my email address and still get gravatar pic?
- Chad Joan (3/12) Jan 27 2013 Oh well, my email address gets spammed plenty anyways.
- Dejan Lekic (6/7) Aug 02 2013
- Vladimir Panteleev (2/3) Aug 24 2013
- Vladimir Panteleev (2/3) Aug 24 2013
- viagra-test-123 (3/4) Aug 26 2013 Testing spam filter
- viagra-test-123 (1/5) Aug 26 2013
- viagra-test-123 (2/9) Jan 02 2014 Testing CAPTCHA
- viagra-test-123 (1/12) Jan 02 2014
- viagra-test-123 (1/15) Jan 02 2014
- ag0aep6g (1/1) Mar 07 2018 test
- Vladimir Panteleev (3/4) Dec 21 2013 Test posting from k3.1azy.net
- Vladimir Panteleev (3/4) Dec 23 2013 Mod test
- Vladimir Panteleev (19/36) Dec 30 2013 DFeed-wrapped:
-
Vladimir Panteleev
(11/11)
Jan 03 2014
On Mon, 30 Dec 2013 23:15:37 -0000, Vladimir Panteleev
- Vladimir Panteleev (3/4) Mar 12 2014 Spring test
- Vladimir Panteleev (3/7) Apr 26 2014 Highlight test
- Vladimir Panteleev (3/4) Jan 15 2015 test
- Vladimir Panteleev (3/7) Jan 15 2015 test
- Vladimir Panteleev (2/3) Jan 22 2015
- Vladimir Panteleev (4/22) May 07 2015 1234567890
- Vladimir Panteleev (2/11) May 14 2015 1234567890
- Vladimir Panteleev (10/10) May 15 2015 This is a very very very very very very very very very very long
- Vladimir Panteleev (10/10) May 17 2015 This is a very very very very very very very very very very long
- Vladimir Panteleev (8/8) May 17 2015 aaa bbbbbbbbbbbbbbbbbbbb ccc
- Baz (7/16) May 23 2015 see:
- Vladimir Panteleev (1/1) May 24 2015 test
- Vladimir Panteleev (3/4) May 28 2015 Test
- Vladimir Panteleev (3/7) Jun 02 2015 Test
- Vladimir Panteleev (2/10) Oct 21 2015 Test
- Vladimir Panteleev (3/15) Oct 21 2015 Test
- Vladimir Panteleev (40/56) Mar 23 2016 -----BEGIN PGP SIGNED MESSAGE-----
- Vladimir Panteleev (3/4) Jan 31 2017 Flood test
- Vladimir Panteleev (3/7) Jan 31 2017 Flood test
- Vladimir Panteleev (3/11) Jan 31 2017 Flood test
- Vladimir Panteleev (3/15) Jan 31 2017 [url]spam test[/url]
- Vladimir Panteleev (3/19) Jan 31 2017 [url]http://example.com[/url]
- Vladimir Panteleev (3/23) Jan 31 2017 [url]http://example.com[/url]
- ketmar (2/20) Feb 20 2017 so...
- ketmar (3/4) Feb 04 2017 test reply...
- Vladimir Panteleev (1/1) Jun 16 2017 test
- Heinz (3/4) Jun 17 2017 spam
- Vladimir Panteleev (3/4) Jun 19 2017 test
- Vladimir Panteleev (3/7) Feb 01 2018 test
- Vladimir Panteleev (3/7) Feb 01 2018 test
- Vladimir Panteleev (3/4) Feb 03 2018 Test
- John Doe (8/9) Apr 24 2018 This is normal forum post.
- John Doe (3/4) Apr 24 2018 games pirate furniture stores animation protein documents
- John Doe (3/4) Apr 24 2018 games pirate furniture stores animation protein documents
- John Doe (3/4) Apr 24 2018 games pirate furniture stores animation protein documents
- John Doe (3/4) Oct 18 2018 games pirate furniture stores animation protein documents
- John Doe (7/8) Apr 24 2018 This is also a normal forum post.
- Test (3/4) Jun 02 2018 Test
- Test user (2/6) Jun 02 2018 Test!
- Vladimir Panteleev (2/6) Jun 14 2018 Test
- Test user (3/10) Jun 14 2018 Test
- Vladimir Panteleev (3/4) Apr 03 2019 Test
- Vladimir Panteleev (3/7) Apr 03 2019 Test
- Vladimir Panteleev (3/11) Apr 03 2019 Test
- Vladimir Panteleev (4/16) Mar 31 2021 Test
- Vladimir Panteleev (3/4) Mar 31 2021
- Vladimir Panteleev (3/4) Apr 01 2021 test*test*test
- Petar Kirov [ZombineDev] (143/153) Apr 02 2021 ---
- Petar Kirov [ZombineDev] (248/250) Apr 02 2021 # GitLab Flavored Markdown test
- Petar Kirov [ZombineDev] (165/172) Apr 02 2021 ### Emoji
- Petar Kirov [ZombineDev] (310/337) Apr 02 2021 ### Task lists
- Petar Kirov [ZombineDev] (443/456) Apr 02 2021 ### Inline HTML
- Vladimir Panteleev (9/13) Jun 17 2021 | A | B
- Vladimir Panteleev (12/16) Jun 17 2021 - foo
- Vladimir Panteleev (3/4) Feb 16 2022 Test
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTest
Feb 29 2012
17.04.2012 3:38, Nick написал:let's test if this is working!yet another test
May 15 2012
Alexandr Druzhinin wrote:17.04.2012 3:38, Nick написал:Definitely works. :) -- http://dejan.lekic.orglet's test if this is working!yet another test
May 25 2012
This popped up on my desk today Test Test Yes seems to be OK Hi all
Aug 11 2012
On 02/17/2012 05:46 PM, Vladimir Panteleev wrote:testtest
Nov 28 2012
On Wednesday, 28 November 2012 at 10:25:59 UTC, r_m_r wrote:On 02/17/2012 05:46 PM, Vladimir Panteleev wrote:viagra-test-123testtest
Dec 06 2012
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testI'm testing what my posts from the web-interface look like so I can make my mail client match.
Jan 27 2013
On Sunday, 27 January 2013 at 20:30:38 UTC, Chad Joan wrote:On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Can I distort my email address and still get gravatar pic? Probably too late now <g>testI'm testing what my posts from the web-interface look like so I can make my mail client match.
Jan 27 2013
On 01/27/2013 03:31 PM, Chad Joan wrote:On Sunday, 27 January 2013 at 20:30:38 UTC, Chad Joan wrote:Oh well, my email address gets spammed plenty anyways. Here goes thunderbird.On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Can I distort my email address and still get gravatar pic? Probably too late now <g>testI'm testing what my posts from the web-interface look like so I can make my mail client match.
Jan 27 2013
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:test<iframe width="600" height="570" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="" id="na635110182987120077"></iframe><script type="text/javascript">document.getElementById("na635110182987120077").src="http://www.netmarketshare.com/report.aspx?qprid=10"+String.fromCharCode(38)+"qptimeframe=Q"+String.fromCharCode(38)+"qpsp=58"+String.fromCharCode(38)+"qpch=350"+String.fromCharCode(38)+"qpdt=1"+String.fromCharCode(38)+"qpct=3"+String.fromCharCode(38)+"qpcustomd=0"+String.fromCharCode(38)+"qpcid=fw126135"+String.fromCharCode(38)+"qpf=16"+String.fromCharCode(38)+"qpwidth=600"+String.fromCharCode(38)+"qpdisplay=1111"+String.fromCharCode(38)+"qpmr=10"+String.fromCharCode(38)+"site="+window.location.hostname</script>
Aug 02 2013
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:test
Aug 24 2013
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:test
Aug 24 2013
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTesting spam filter
Aug 26 2013
On Monday, 26 August 2013 at 15:06:56 UTC, viagra-test-123 wrote:On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTesting spam filter
Aug 26 2013
On Monday, 26 August 2013 at 16:24:09 UTC, viagra-test-123 wrote:On Monday, 26 August 2013 at 15:06:56 UTC, viagra-test-123 wrote:Testing CAPTCHAOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTesting spam filter
Jan 02 2014
On Friday, 3 January 2014 at 02:33:37 UTC, viagra-test-123 wrote:On Monday, 26 August 2013 at 16:24:09 UTC, viagra-test-123 wrote:On Monday, 26 August 2013 at 15:06:56 UTC, viagra-test-123 wrote:Testing CAPTCHAOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTesting spam filter
Jan 02 2014
On Friday, 3 January 2014 at 02:34:02 UTC, viagra-test-123 wrote:On Friday, 3 January 2014 at 02:33:37 UTC, viagra-test-123 wrote:On Monday, 26 August 2013 at 16:24:09 UTC, viagra-test-123 wrote:On Monday, 26 August 2013 at 15:06:56 UTC, viagra-test-123 wrote:Testing CAPTCHAOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTesting spam filter
Jan 02 2014
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTest posting from k3.1azy.net
Dec 21 2013
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testMod test
Dec 23 2013
DFeed-wrapped: 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 Quoted 80 chars:3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 903 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 903 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 90Quoted 100 chars:3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 903 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 903 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 9 1 3 5 7 90
Dec 30 2013
On Mon, 30 Dec 2013 23:15:37 -0000, Vladimir Panteleev <vladimir thecybershadow.net> wrote: 60 chars: 012345678901234567890123456789012345678901234567890123456789 012345678901234567890123456789012345678901234567890123456789 012345678901234567890123456789012345678901234567890123456789 012345678901234567890123456789012345678901234567890123456789 80 chars: 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901234567890123456789012345678901234567890123456789
Jan 03 2014
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testSpring test
Mar 12 2014
On Wednesday, 12 March 2014 at 21:13:03 UTC, Vladimir Panteleev wrote:On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Highlight testtestSpring test
Apr 26 2014
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testtest
Jan 15 2015
On Thursday, 15 January 2015 at 13:14:02 UTC, Vladimir Panteleev wrote:On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testtesttest
Jan 15 2015
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:test
Jan 22 2015
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:test1234567890234567890123456789034567890234567890456789034567890567890456789067890567890789067890890789090890090
May 07 2015
123456789034567890123456789056789034567890789056789090789090
May 14 2015
This is a very very very very very very very very very very long string. This is a very very very very very very very very very very long string. This is a very very very very very very very very very very long string. This is a very very very very very very very very very very long string. This is a very very very very very very very very very very long string.
May 15 2015
This is a very very very very very very very very very very long string. This is a very very very very very very very very very very long string. This is a very very very very very very very very very very long string. This is a very very very very very very very very very very long string. This is a very very very very very very very very very very long string.
May 17 2015
aaa bbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccc
May 17 2015
On Monday, 18 May 2015 at 04:42:31 UTC, Vladimir Panteleev wrote:aaa bbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb ccc aaa bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb cccsee: in an editor this less than 80 chars, http://i.imgur.com/Oo3TaKN.png but on the forum the code is warpped: http://forum.dlang.org/post/nlndlssjdpeewqwoxyud forum.dlang.org This could be improved.
May 23 2015
tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10
May 25 2015
tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 fills a single web interface editor line.
May 25 2015
On Monday, 25 May 2015 at 13:18:32 UTC, sdf wrote: tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 tokenis10 is a single line but is warped at 60 chars. Is it by design ? (20 chars right margin!).
May 25 2015
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTest
May 28 2015
On Thursday, 28 May 2015 at 16:15:25 UTC, Vladimir Panteleev wrote:On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:TesttestTest
Jun 02 2015
On Tuesday, 2 June 2015 at 22:15:01 UTC, Vladimir Panteleev wrote:On Thursday, 28 May 2015 at 16:15:25 UTC, Vladimir Panteleev wrote:TestOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:TesttestTest
Oct 21 2015
On Thursday, 22 October 2015 at 04:46:07 UTC, Vladimir Panteleev wrote:On Tuesday, 2 June 2015 at 22:15:01 UTC, Vladimir Panteleev wrote:TestOn Thursday, 28 May 2015 at 16:15:25 UTC, Vladimir Panteleev wrote:TestOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:TesttestTest
Oct 21 2015
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Thursday, 22 October 2015 at 04:46:54 UTC, Vladimir Panteleev wrote:On Thursday, 22 October 2015 at 04:46:07 UTC, Vladimir Panteleev wrote:One two three one two three one two three one two three one two three one two three one two three one two three one two three one two three one two three. // Round floating point numbers import std.algorithm, std.conv, std.functional, std.math, std.regex, std.stdio; alias round = pipe!(to!real, std.math.round, to!string); static reFloatingPoint = ctRegex!`[0-9]+\.[0-9]+`; void main() { // Replace anything that looks like a real // number with the rounded equivalent. stdin .byLine .map!(l => l.replaceAll!(c => c.hit.round) (reFloatingPoint)) .each!writeln; } -----BEGIN PGP SIGNATURE----- Version: Mailvelope v1.3.6 Comment: https://www.mailvelope.com wsFcBAEBCAAQBQJW82eVCRDxWiRxCu7B+gAAhjIP+wXL5HDHRhukr70lySj7 ohe70Kf8/SSqSOkeb1xmfTYVIu4dySCeGFJ3v3wCwymk9J+a+cL9P9Glw8T/ yw7uFFU7nI/Qbme/WXT5b06D66mvp+BSrrljZS/4aHDiOOg4f/+lrncVpUiF 1dws0k2txRIBHfIQ88eUz7Pnj8Tv4rv32XBFHek3FbfFQb6Jpi0NREqYDD8v WzDc26aZH7RzQCw7QUAdIVfr1S+D7cm844P6ulfiykTm7BddhT9mjSdRHG5n Ldk5ZQvEqUOWhWS/1CVFwZqE6RKWVxynOMCb4o7SzBW3YUokWicNPR+uEvqp vvpMWqxOXhaGx8ZAgc/8BxUuUB7qCINIifyo8hhsfhssnChGyox7OcZs5rf4 th8uanfJnmhYBd1qNpR4ZODIA9f2nKRm0dTbUQRz08rlzux02sKv2ogaIvTG kqazBLR3m7l1lJc73/7CVkMGYApm69iCxldchncGHC/2Z95+/OUEmijwYZVu aeg53HJK7HhMeGpviCoRXcOsQ9mgtY++ESAdhJKpDDbVDiUO/TrVJ4Pk5Mh+ jgV5YD9Gt2PvDYlVZgNRZCJMrJqC5fDVIPMF3JnsRAz4L+V70zrJpwe9Fdn5 9+WKtXW3Uyx7c51MPMfGrIEo3Vr7tm7hUy5tjiX4Svi5wIL/M+Jh36GO2GEc fGzA =fTno -----END PGP SIGNATURE-----On Tuesday, 2 June 2015 at 22:15:01 UTC, Vladimir Panteleev wrote:TestOn Thursday, 28 May 2015 at 16:15:25 UTC, Vladimir Panteleev wrote:TestOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:TesttestTest
Mar 23 2016
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testFlood test
Jan 31 2017
On Tuesday, 31 January 2017 at 14:20:33 UTC, Vladimir Panteleev wrote:On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Flood testtestFlood test
Jan 31 2017
On Tuesday, 31 January 2017 at 14:25:59 UTC, Vladimir Panteleev wrote:On Tuesday, 31 January 2017 at 14:20:33 UTC, Vladimir Panteleev wrote:Flood testOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Flood testtestFlood test
Jan 31 2017
On Tuesday, 31 January 2017 at 14:26:19 UTC, Vladimir Panteleev wrote:On Tuesday, 31 January 2017 at 14:25:59 UTC, Vladimir Panteleev wrote:[url]spam test[/url]On Tuesday, 31 January 2017 at 14:20:33 UTC, Vladimir Panteleev wrote:Flood testOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Flood testtestFlood test
Jan 31 2017
On Tuesday, 31 January 2017 at 14:27:38 UTC, Vladimir Panteleev wrote:On Tuesday, 31 January 2017 at 14:26:19 UTC, Vladimir Panteleev wrote:[url]http://example.com[/url]On Tuesday, 31 January 2017 at 14:25:59 UTC, Vladimir Panteleev wrote:[url]spam test[/url]On Tuesday, 31 January 2017 at 14:20:33 UTC, Vladimir Panteleev wrote:Flood testOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Flood testtestFlood test
Jan 31 2017
On Tuesday, 31 January 2017 at 14:28:33 UTC, Vladimir Panteleev wrote:On Tuesday, 31 January 2017 at 14:27:38 UTC, Vladimir Panteleev wrote:[url]http://example.com[/url]On Tuesday, 31 January 2017 at 14:26:19 UTC, Vladimir Panteleev wrote:[url]http://example.com[/url]On Tuesday, 31 January 2017 at 14:25:59 UTC, Vladimir Panteleev wrote:[url]spam test[/url]On Tuesday, 31 January 2017 at 14:20:33 UTC, Vladimir Panteleev wrote:Flood testOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Flood testtestFlood test
Jan 31 2017
Vladimir Panteleev wrote:On Tuesday, 31 January 2017 at 14:28:33 UTC, Vladimir Panteleev wrote:so...On Tuesday, 31 January 2017 at 14:27:38 UTC, Vladimir Panteleev wrote:[url]http://example.com[/url]On Tuesday, 31 January 2017 at 14:26:19 UTC, Vladimir Panteleev wrote:[url]http://example.com[/url]On Tuesday, 31 January 2017 at 14:25:59 UTC, Vladimir Panteleev wrote:[url]spam test[/url]On Tuesday, 31 January 2017 at 14:20:33 UTC, Vladimir Panteleev wrote:Flood testOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Flood testtestFlood test
Feb 20 2017
On Fri, 17 Feb 2012 14:16:06 +0200, Vladimir Panteleev <vladimir thecybershadow.net> wrote:testtest reply...
Feb 04 2017
On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:testspam
Jun 17 2017
On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:testtest
Jun 19 2017
On Tuesday, 20 June 2017 at 00:27:45 UTC, Vladimir Panteleev wrote:On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:testtesttest
Feb 01 2018
On Tuesday, 20 June 2017 at 00:27:45 UTC, Vladimir Panteleev wrote:On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:testtesttest
Feb 01 2018
On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:testTest
Feb 03 2018
On Saturday, 3 February 2018 at 09:23:23 UTC, Vladimir Panteleev wrote:On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:TesttestTest
Feb 03 2018
On Saturday, 3 February 2018 at 09:23:23 UTC, Vladimir Panteleev wrote:On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:Test 2testTest
Feb 03 2018
On Saturday, 3 February 2018 at 09:23:23 UTC, Vladimir Panteleev wrote:On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:Test 3testTest
Feb 03 2018
On Saturday, 3 February 2018 at 09:23:23 UTC, Vladimir Panteleev wrote:On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:Test 4testTest
Feb 03 2018
On Saturday, 3 February 2018 at 09:23:23 UTC, Vladimir Panteleev wrote:On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:Test 5testTest
Feb 03 2018
On Saturday, 3 February 2018 at 09:23:23 UTC, Vladimir Panteleev wrote:On Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:Test 6testTest
Feb 03 2018
On Saturday, 3 February 2018 at 11:01:18 UTC, P V wrote:On Saturday, 3 February 2018 at 09:23:23 UTC, Vladimir Panteleev wrote:TestOn Saturday, 17 June 2017 at 01:26:54 UTC, Vladimir Panteleev wrote:Test 6testTest
Feb 21 2018
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testThis is normal forum post. void main() { import std.stdio; writeln("Hello, world!"); }
Apr 24 2018
On Wednesday, 25 April 2018 at 05:11:35 UTC, John Doe wrote:This is normal forum post.games pirate furniture stores animation protein documents citizenship
Apr 24 2018
On Wednesday, 25 April 2018 at 05:11:35 UTC, John Doe wrote:This is normal forum post.games pirate furniture stores animation protein documents citizenship
Apr 24 2018
On Wednesday, 25 April 2018 at 05:11:35 UTC, John Doe wrote:This is normal forum post.games pirate furniture stores animation protein documents citizenship
Apr 24 2018
On Wednesday, 25 April 2018 at 05:35:55 UTC, John Doe wrote:[...]games pirate furniture stores animation protein documents citizenship
Oct 18 2018
On Wednesday, 25 April 2018 at 05:11:35 UTC, John Doe wrote:This is normal forum post.This is also a normal forum post. void main() { import std.stdio; writeln("Hello, world!"); }
Apr 24 2018
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTest
Jun 02 2018
On Sunday, 3 June 2018 at 01:42:35 UTC, Test wrote:On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:Test!testTest
Jun 02 2018
On Sunday, 3 June 2018 at 01:42:35 UTC, Test wrote:On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:TesttestTest
Jun 14 2018
On Thursday, 14 June 2018 at 09:25:41 UTC, Vladimir Panteleev wrote:On Sunday, 3 June 2018 at 01:42:35 UTC, Test wrote:TestOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:TesttestTest
Jun 14 2018
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTest
Apr 03 2019
On Wednesday, 3 April 2019 at 19:01:20 UTC, Vladimir Panteleev wrote:On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:TesttestTest
Apr 03 2019
On Wednesday, 3 April 2019 at 19:05:37 UTC, Vladimir Panteleev wrote:On Wednesday, 3 April 2019 at 19:01:20 UTC, Vladimir Panteleev wrote:TestOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:TesttestTest
Apr 03 2019
On Wednesday, 3 April 2019 at 19:46:00 UTC, Vladimir Panteleev wrote:On Wednesday, 3 April 2019 at 19:05:37 UTC, Vladimir Panteleev wrote:Test <script>test</script>On Wednesday, 3 April 2019 at 19:01:20 UTC, Vladimir Panteleev wrote:TestOn Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:TesttestTest
Mar 31 2021
On Thursday, 1 April 2021 at 06:12:26 UTC, Vladimir Panteleev wrote:<script>test</script><script>test</script>
Mar 31 2021
On Thursday, 1 April 2021 at 06:35:11 UTC, Vladimir Panteleev wrote:[snip]test*test*test
Apr 01 2021
On Thursday, 1 April 2021 at 07:26:52 UTC, Vladimir Panteleev wrote:On Thursday, 1 April 2021 at 06:35:11 UTC, Vladimir Panteleev wrote:--- Compare this with the output of https://markdown-it.github.io/ --- ___ --- *** Enable typographer option to see result. (c) (C) (r) (R) (tm) (TM) (p) (P) +- test.. test... test..... test?..... test!.... !!!!!! ???? ,, -- --- "Smartypants, double quotes" and 'single quotes' **This is bold text** __This is bold text__ *This is italic text* _This is italic text_ ~~Strikethrough~~[snip]test*test*testBlockquotes can also be nested...Unordered + Create a list by starting a line with `+`, `-`, or `*` + Sub-lists are made by indenting 2 spaces: - Marker character change forces new list start: * Ac tristique libero volutpat at + Facilisis in pretium nisl aliquet - Nulla volutpat aliquam velit + Very easy! Ordered 1. Lorem ipsum dolor sit amet 2. Consectetur adipiscing elit 3. Integer molestie lorem at massa 1. You can use sequential numbers... 1. ...or keep all the numbers as `1.` Start numbering with offset: 57. foo 1. bar Inline `code` Indented code // Some comments line 1 of code line 2 of code line 3 of code Block code "fences" ``` Sample text here... ``` Syntax highlighting ``` js var foo = function (bar) { return bar++; }; console.log(foo(5)); ``` | Option | Description | | ------ | ----------- | | data | path to data files to supply the data that will be passed into templates. | | engine | engine to be used for processing templates. Handlebars is the default. | | ext | extension to be used for dest files. | Right aligned columns | Option | Description | | ------:| -----------:| | data | path to data files to supply the data that will be passed into templates. | | engine | engine to be used for processing templates. Handlebars is the default. | | ext | extension to be used for dest files. | [link text](http://dev.nodeca.com) [link with title](http://nodeca.github.io/pica/demo/ "title text!") Autoconverted link https://github.com/nodeca/pica (enable linkify to see) ![Minion](https://octodex.github.com/images/minion.png) ![Stormtroopocat](https://octodex.github.com/images/stormtroopocat.jpg "The Stormtroopocat") Like links, Images also have a footnote style syntax ![Alt text][id] With a reference later in the document defining the URL location: [id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat" The killer feature of `markdown-it` is very effective support of [syntax plugins](https://www.npmjs.org/browse/keyword/markdown-it-plugin). https://github.com/markdown-it/markdown-it-emoji)...by using additional greater-than signs right next to each other......or with spaces between arrows.Classic markup: :wink: :crush: :cry: :tear: :laughing: :yum: Shortcuts (emoticons): :-) :-( 8-) ;)see [how to change output](https://github.com/markdown-it/markdown-it-emoji#change-output) with twemoji. https://github.com/markdown-it/markdown-it-sub) / [Superscript](https://github.com/markdown-it/markdown-it-sup) - 19^th^ - H~2~O https://github.com/markdown-it/markdown-it-ins) ++Inserted text++ https://github.com/markdown-it/markdown-it-mark) ==Marked text== [Footnotes](https://github.com/markdown-it/markdown-it-footnote) Footnote 1 link[^first]. Footnote 2 link[^second]. Inline footnote^[Text of inline footnote] definition. Duplicated footnote reference[^second]. [^first]: Footnote **can have markup** and multiple paragraphs. [^second]: Footnote text. lists](https://github.com/markdown-it/markdown-it-deflist) Term 1 : Definition 1 with lazy continuation. Term 2 with *inline markup* : Definition 2 { some code, part of Definition 2 } Third paragraph of definition 2. _Compact style:_ Term 1 ~ Definition 1 Term 2 ~ Definition 2a ~ Definition 2b [Abbreviations](https://github.com/markdown-it/markdown-it-abbr) This is HTML abbreviation example. It converts "HTML", but keep intact partial entries like "xxxHTMLyyy" and so on. *[HTML]: Hyper Text Markup Language containers](https://github.com/markdown-it/markdown-it-container) ::: warning *here be dragons* :::
Apr 02 2021
On Friday, 2 April 2021 at 10:33:46 UTC, Petar Kirov [ZombineDev] wrote:[..]Compare with https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md --- stage: Create group: Source Code info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments" type: reference, howto --- This Markdown guide is **valid only for the GitLab internal Markdown rendering system for entries and files**. It is **not** valid for the [GitLab documentation website](https://docs.gitlab.com) or the [GitLab main website](https://about.gitlab.com), as they both use [Kramdown](https://kramdown.gettalong.org) as their Markdown engine. The documentation website uses an extended Kramdown gem, [GitLab Kramdown](https://gitlab.com/gitlab-org/gitlab_kramdown). Consult the [GitLab Kramdown Guide](https://about.gitlab.com/handbook/markdown-guide/) for a complete Kramdown reference. NOTE: We encourage you to view this document as [rendered by GitLab itself](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md). GitLab uses "GitLab Flavored Markdown". It extends the [CommonMark specification](https://spec.commonmark.org/current/) (which is based on standard Markdown) in several ways to add more features. It was inspired by [GitHub Flavored Markdown](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax). You can use GitLab Flavored Markdown in the following areas: - Comments - Issues - Merge requests - Milestones - Snippets (the snippet must be named with a `.md` extension) - Wiki pages - Markdown documents inside repositories - Epics **(ULTIMATE)** You can also use other rich text files in GitLab. You might have to install a dependency to do so. Please see the [`gitlab-markup` gem project](https://gitlab.com/gitlab-org/gitlab-markup) for more information. - In GitLab version 11.8, the [Redcarpet Ruby library](https://github.com/vmg/redcarpet) was removed. All issues and comments, including those from pre-11.1, are now processed using the [CommonMark Ruby Library](https://github.com/gjtorikian/commonmarker). - GitLab versions 11.3 and greater use CommonMark to process wiki pages and Markdown files (`*.md`) in repositories. - GitLab versions 11.1 and greater use the [CommonMark Ruby Library](https://github.com/gjtorikian/commonmarker) for Markdown processing of all new issues, merge requests, comments, and other Markdown content in the GitLab system. The documentation website migrated its Markdown engine [from Redcarpet to Kramdown](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests/108) in October 2018. You may have older issues, merge requests, or Markdown documents in your repository that relied upon nuances of the GitLab RedCarpet version of Markdown. Because CommonMark uses slightly stricter syntax, these documents may now appear differently after the transition to CommonMark. For example, numbered lists with nested lists may render incorrectly: ```markdown 1. Chocolate - dark - milk ``` To correct their rendering, add a space to each nested item to align the `-` with the first character of the top list item (`C` in this case): ```markdown 1. Chocolate - dark - milk ``` 1. Chocolate - dark - milk We flag any significant differences between Redcarpet and CommonMark Markdown in this document. If you have many Markdown files, it can be tedious to determine if they display correctly or not. You can use the [`diff_redcarpet_cmark`](https://gitlab.com/digitalmoksha/diff_redcarpet_cmark) tool to generate a list of files and the differences between how RedCarpet and CommonMark render the files. It indicates if any changes are needed. `diff_redcarpet_cmark` is not an officially supported product. GitLab makes full use of the standard (CommonMark) formatting, but also includes more helpful features for GitLab users. It makes use of [new Markdown features](#new-gitlab-flavored-markdown-extensions), not found in standard Markdown: - [Color chips written in HEX, RGB or HSL](#colors) - [Diagrams and flowcharts](#diagrams-and-flowcharts) - [Emoji](#emoji) - [Front matter](#front-matter) - [Inline diffs](#inline-diff) - [Math equations and symbols written in LaTeX](#math) - [Special GitLab references](#special-gitlab-references) - [Task Lists](#task-lists) - [Table of Contents](#table-of-contents) - [Wiki specific Markdown](#wiki-specific-markdown) It also has [extended Markdown features](#standard-markdown-and-extensions-in-gitlab), without changing how standard Markdown is used: | Standard Markdown | Extended Markdown in GitLab | | ------------------------------------- | ------------------------- | | [blockquotes](#blockquotes) | [multi-line blockquotes](#multiline-blockquote) | | [code blocks](#code-spans-and-blocks) | [colored code and syntax highlighting](#colored-code-and-syntax-highlighting) | | [emphasis](#emphasis) | [multiple underscores in words](#multiple-underscores-in-words-and-mid-word-emphasis) | [headers](#headers) | [linkable Header IDs](#header-ids-and-links) | | [images](#images) | [embedded videos](#videos) and [audio](#audio) | | [line breaks](#line-breaks) | [more line break control](#newlines) | | [links](#links) | [automatically linking URLs](#url-auto-linking) | If this section isn't rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#colors). It's possible to have color written in HEX, RGB, or HSL format rendered with a color indicator. Supported formats (named colors are not supported): - HEX: `` `#RGB[A]` `` or `` `#RRGGBB[AA]` `` - RGB: `` `RGB[A](R, G, B[, A])` `` - HSL: `` `HSL[A](H, S, L[, A])` `` Color written inside backticks is followed by a color "chip": ```markdown - `#F00` - `#F00A` - `#FF0000` - `#FF0000AA` - `RGB(0,255,0)` - `RGB(0%,100%,0%)` - `RGBA(0,255,0,0.3)` - `HSL(540,70%,50%)` - `HSLA(540,70%,50%,0.3)` ``` - `#F00` - `#F00A` - `#FF0000` - `#FF0000AA` - `RGB(0,255,0)` - `RGB(0%,100%,0%)` - `RGBA(0,255,0,0.3)` - `HSL(540,70%,50%)` - `HSLA(540,70%,50%,0.3)` It's possible to generate diagrams and flowcharts from text in GitLab using [Mermaid](https://mermaidjs.github.io/) or [PlantUML](https://plantuml.com). It's also possible to use [Kroki](https://kroki.io) to create a wide variety of diagrams.[Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/15107) in GitLab 10.3.Visit the [official page](https://mermaidjs.github.io/) for more details. The [Mermaid Live Editor](https://mermaid-js.github.io/mermaid-live-editor/) helps you learn Mermaid and debug issues in your Mermaid code. Use it to identify and resolve issues in your diagrams. To generate a diagram or flowchart, write your text inside the `mermaid` block: ````markdown ```mermaid graph TD; A-->B; A-->C; B-->D; C-->D; ``` ```` ```mermaid graph TD; A-->B; A-->C; B-->D; C-->D; ``` Subgraphs can also be included: ````markdown ```mermaid graph TB SubGraph1 --> SubGraph1Flow subgraph "SubGraph 1 Flow" SubGraph1Flow(SubNode 1) SubGraph1Flow -- Choice1 --> DoChoice1 SubGraph1Flow -- Choice2 --> DoChoice2 end subgraph "Main Graph" Node1[Node 1] --> Node2[Node 2] Node2 --> SubGraph1[Jump to SubGraph1] SubGraph1 --> FinalThing[Final Thing] end ``` ```` ```mermaid graph TB SubGraph1 --> SubGraph1Flow subgraph "SubGraph 1 Flow" SubGraph1Flow(SubNode 1) SubGraph1Flow -- Choice1 --> DoChoice1 SubGraph1Flow -- Choice2 --> DoChoice2 end subgraph "Main Graph" Node1[Node 1] --> Node2[Node 2] Node2 --> SubGraph1[Jump to SubGraph1] SubGraph1 --> FinalThing[Final Thing] end ``` To make PlantUML available in GitLab, a GitLab administrator needs to enable it first. Read more in [PlantUML & GitLab](../administration/integration/plantuml.md). To make Kroki available in GitLab, a GitLab administrator needs to enable it first. Read more in the [Kroki integration](../administration/integration/kroki.md) page.
Apr 02 2021
On Friday, 2 April 2021 at 10:47:55 UTC, Petar Kirov [ZombineDev] wrote:On Friday, 2 April 2021 at 10:33:46 UTC, Petar Kirov [ZombineDev] wrote:If this section isn't rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#emoji). ```markdown Sometimes you want to :monkey: around a bit and add some :star2: to your :speech_balloon:. Well we have a gift for you: :zap: You can use emoji anywhere GitLab Flavored Markdown is supported. :v: You can use it to point out a :bug: or warn about :speak_no_evil: patches. And if someone improves your really :snail: code, send them some :birthday:. People :heart: you for that. If you're new to this, don't be :fearful:. You can join the emoji :family:. All you need to do is to look up one of the supported codes. Consult the [Emoji Cheat Sheet](https://www.emojicopy.com) for a list of all supported emoji codes. :thumbsup: ``` Sometimes you want to \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/imag s/emoji/monkey.png" width="20px" height="20px" style="display:inline;margin:0;border: 0"> around a bit and add some \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/ima es/emoji/star2.png" width="20px" height="20px" style="display:inline;margin:0;border: 0"> to your \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/images/emoji speech_balloon.png" width="20px" height="20px" style="display:inline;margin:0;border: 0">. Well we have a gift for you: \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/i ages/emoji/zap.png" width="20px" height="20px" style="display:inline;margin:0;border: 0">You can use emoji anywhere GitLab Flavored Markdown is supported. \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets images/emoji/v.png" width="20px" height="20px" style="display:inline;margin:0;border: 0"> You can use it to point out a\<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/i ages/emoji/bug.png" width="20px" height="20px" style="display:inline;margin:0;border: 0"> or warn about \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/images/emoj /speak_no_evil.png" width="20px" height="20px" style="display:inline;margin:0;border: 0"> patches. If someone improves your really \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/ima es/emoji/snail.png" width="20px" height="20px" style="display:inline;margin:0;border: 0"> code, send them some \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/images emoji/birthday.png" width="20px" height="20px" style="display:inline;margin:0;border: 0">. People \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/ima es/emoji/heart.png" width="20px" height="20px" style="display:inline;margin:0;border: 0"> you for that. If you're new to this, don't be \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/image /emoji/fearful.png" width="20px" height="20px" style="display:inline;margin:0;border: 0">. You can join the emoji \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/imag s/emoji/family.png" width="20px" height="20px" style="display:inline;margin:0;border: 0">. All you need to do is to look up one of the supported codes. Consult the [Emoji Cheat Sheet](https://www.webfx.com/tools/emoji-cheat-sheet/) for a list of all supported emoji codes. \<img src="https://gitlab.com/gitlab-org/gitlab-foss/raw/master/app/assets/images emoji/thumbsup.png" width="20px" height="20px" style="display:inline;margin:0;border: 0"> The emoji example above uses hard-coded images for this documentation. Rendered emoji in GitLab may appear different depending on the OS and browser used. Most emoji are natively supported on macOS, Windows, iOS, Android, and fall back on image-based emoji where there is no support. \<!-- vale gitlab.Spelling = NO --> On Linux, you can download [Noto Color Emoji](https://www.google.com/get/noto/help/emoji/) to get full native emoji support. Ubuntu 18.04 (like many modern Linux distributions) has this font installed by default. \<!-- vale gitlab.Spelling = YES -->[..]Compare with https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md[Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/23331) in GitLab 11.6.Front matter is metadata included at the beginning of a Markdown document, preceding its content. This data can be used by static site generators such as [Jekyll](https://jekyllrb.com/docs/front-matter/), [Hugo](https://gohugo.io/content-management/front-matter/), and many other applications. When you view a Markdown file rendered by GitLab, any front matter is displayed as-is, in a box at the top of the document. The HTML content displays after the front matter. To view an example, you can toggle between the source and rendered version of a [GitLab documentation file](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/README.md). In GitLab, front matter is only used in Markdown files and wiki pages, not the other places where Markdown formatting is supported. It must be at the very top of the document and must be between delimiters, as explained below. The following delimiters are supported: - YAML (`---`): ```yaml --- title: About Front Matter example: language: yaml --- ``` - TOML (`+++`): ```toml +++ title = "About Front Matter" [example] language = "toml" +++ ``` - JSON (`;;;`): ```json ;;; { "title": "About Front Matter" "example": { "language": "json" } } ;;; ``` Other languages are supported by adding a specifier to any of the existing delimiters. For example: ```php ---php $title = "About Front Matter"; $example = array( 'language' => "php", ); --- ``` If this section isn't rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#inline-diff). With inline diff tags you can display `{+ additions +}` or `[- deletions -]`. The wrapping tags can be either curly braces or square brackets: ```markdown - {+ addition 1 +} - [+ addition 2 +] - {- deletion 3 -} - [- deletion 4 -] ``` ![Inline diff as rendered by the GitLab interface](img/inline_diff_01_v13_3.png) --- However, the wrapping tags can't be mixed: ```markdown - {+ addition +] - [+ addition +} - {- deletion -] - [- deletion -} ``` If your diff includes words in `` `code` `` font, make sure to escape each backtick `` ` `` with a backslash `\`, otherwise the diff highlight don't render correctly: ```markdown - {+ Just regular text +} - {+ Text with `backticks` inside +} - {+ Text with escaped \`backticks\` inside +} ``` ![Inline diff with mixed formatting, as rendered by the GitLab interface](img/inline_diff_02_v13_3.png) If this section is not rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#math). It's possible to have math written with LaTeX syntax rendered using [KaTeX](https://github.com/KaTeX/KaTeX). Math written between dollar signs `$` are rendered inline with the text. Math written inside a [code block](#code-spans-and-blocks) with the language declared as `math`, are rendered on a separate line: ````markdown This math is inline $`a^2+b^2=c^2`$. This is on a separate line ```math a^2+b^2=c^2 ``` ```` This math is inline $`a^2+b^2=c^2`$. This is on a separate line ```math a^2+b^2=c^2 ``` _Be advised that KaTeX only supports a [subset](https://katex.org/docs/supported.html) of LaTeX._ This also works for the Asciidoctor `:stem: latexmath`. For details, see the [Asciidoctor user manual](https://asciidoctor.org/docs/user-manual/#activating-stem-support).
Apr 02 2021
On Friday, 2 April 2021 at 10:49:38 UTC, Petar Kirov [ZombineDev] wrote:On Friday, 2 April 2021 at 10:47:55 UTC, Petar Kirov [ZombineDev] wrote:If this section isn't rendered correctly, [view it in GitLab itself](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#task-lists). You can add task lists anywhere Markdown is supported, but only issues, merge requests, and comments support clicking to toggle the boxes. In other places, you must edit the Markdown manually to change the status by adding or removing an `x` inside the square brackets. To create a task list, add a specially-formatted Markdown list. You can use either unordered or ordered lists: ```markdown - [x] Completed task - [ ] Incomplete task - [ ] Sub-task 1 - [x] Sub-task 2 - [ ] Sub-task 3 1. [x] Completed task 1. [ ] Incomplete task 1. [ ] Sub-task 1 1. [x] Sub-task 2 ``` - [x] Completed task - [ ] Incomplete task - [ ] Sub-task 1 - [x] Sub-task 2 - [ ] Sub-task 3 1. [x] Completed task 1. [ ] Incomplete task 1. [ ] Sub-task 1 1. [x] Sub-task 2 --- All standard Markdown formatting should work as expected in GitLab. Some standard functionality is extended with additional features, without affecting the standard usage. If a functionality is extended, the new option is listed as a sub-section. Use a blockquote to highlight information, such as a side note. It's generated by starting the lines of the blockquote with `>`: ```markdownOn Friday, 2 April 2021 at 10:33:46 UTC, Petar Kirov [ZombineDev] wrote:[..]Compare with https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.mdBlockquotes help you emulate reply text. This line is part of the same quote.Quote break.This is a very long line that is still quoted properly when it wraps. Keep writing to make sure this line is long enough to actually wrap for everyone. You can also *add* **Markdown** into a blockquote.```Blockquotes help you emulate reply text. This line is part of the same quote.Quote break.This is a very long line that is still quoted properly when it wraps. Keep writing to make sure this line is long enough to actually wrap for everyone. You can also *add* **Markdown** into a blockquote.If this section isn't rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#multiline-blockquote). GitLab Flavored Markdown extends the standard Markdown by also supporting multi-line blockquotes fenced by `>>>`: ```markdownIf you paste a message from somewhere else that spans multiple lines, you can quote that without having to manually prepend `>` to every line!```If you paste a message from somewhere else that spans multiple lines, you can quote that without having to manually prepend `>` to every line!You can highlight anything that should be viewed as code and not standard text. Inline code is highlighted with single backticks `` ` ``: ```markdown Inline `code` has `back-ticks around` it. ``` Inline `code` has `back-ticks around` it. --- To achieve a similar effect for a larger code example, you can: - Fence an entire block of code with triple backticks (```` ``` ````). - Fence an entire block of code with triple tildes (`~~~`). - Indent it four or more spaces. ````markdown ```python def function(): #indenting works just fine in the fenced code block s = "Python code" print s ``` Using 4 spaces is like using 3-backtick fences. ```` ```plaintext ~~~ Tildes are OK too. ~~~ ``` The three examples above render as: ```python def function(): #indenting works just fine in the fenced code block s = "Python code" print s ``` ```plaintext Using 4 spaces is like using 3-backtick fences. ``` ```plaintext Tildes are OK too. ``` If this section isn't rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#colored-code-and-syntax-highlighting). GitLab uses the [Rouge Ruby library](http://rouge.jneen.net/) for more colorful syntax highlighting in code blocks. For a list of supported languages visit the [Rouge project wiki](https://github.com/rouge-ruby/rouge/wiki/List-of-supported-languages-and-lexers). Syntax highlighting is supported only in code blocks, so you can't highlight inline code. To fence and apply syntax highlighting to a block of code, append the code language to the opening code declaration, three back-ticks (```` ``` ````) or three tildes (`~~~`): ````markdown ```javascript var s = "JavaScript syntax highlighting"; alert(s); ``` ```python def function(): #indenting works just fine in the fenced code block s = "Python syntax highlighting" print s ``` ```ruby require 'redcarpet' markdown = Redcarpet.new("Hello World!") puts markdown.to_html ``` ``` No language indicated, so no syntax highlighting. s = "There is no highlighting for this." But let's throw in a \<b>tag\</b>. ``` ```` The four examples above render as: ```javascript var s = "JavaScript syntax highlighting"; alert(s); ``` ```python def function(): #indenting works just fine in the fenced code block s = "Python syntax highlighting" print s ``` ```ruby require 'redcarpet' markdown = Redcarpet.new("Hello World!") puts markdown.to_html ``` ```plaintext No language indicated, so no syntax highlighting. s = "There is no highlighting for this." But let's throw in a \<b>tag\</b>. ``` There are multiple ways to emphasize text in Markdown. You can italicize, bold, strikethrough, and combine these emphasis styles together. Strikethrough is not part of the core Markdown standard, but is part of GitLab Flavored Markdown. Examples: ```markdown Emphasis, aka italics, with *asterisks* or _underscores_. Strong emphasis, aka bold, with double **asterisks** or __underscores__. Combined emphasis with **asterisks and _underscores_**. Strikethrough uses two tildes. ~~Scratch this.~~ ``` Emphasis, aka italics, with *asterisks* or _underscores_. Strong emphasis, aka bold, with double **asterisks** or __underscores__. Combined emphasis with **asterisks and _underscores_**. Strikethrough uses two tildes. ~~Scratch this.~~ If this section isn't rendered correctly, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#multiple-underscores-in-words). Avoid italicizing a portion of a word, especially when you're dealing with code and names that often appear with multiple underscores. GitLab Flavored Markdown extends the standard Markdown standard by ignoring multiple underlines in words, to allow better rendering of Markdown documents discussing code: ```markdown perform_complicated_task do_this_and_do_that_and_another_thing but_emphasis is_desired _here_ ``` perform_complicated_task do_this_and_do_that_and_another_thing but_emphasis is_desired _here_ --- If you wish to emphasize only a part of a word, it can still be done with asterisks: ```markdown perform*complicated*task do*this*and*do*that*and*another thing ``` perform*complicated*task do*this*and*do*that*and*another thing Footnotes add a link to a note that are rendered at the end of a Markdown file. To make a footnote, you need both a reference tag and a separate line (anywhere in the file) with the note content. Regardless of the tag names, the relative order of the reference tags determines the rendered numbering. Reference tags can use letters and other characters. Avoid using lowercase `w` or an underscore (`_`) in footnote tag names until [this bug](https://gitlab.com/gitlab-org/gitlab/-/issues/24423) is resolved. \<!-- Do not edit the following codeblock. It uses HTML to skip the Vale ReferenceLinks test. --> \<pre class="highlight">\<code>A footnote reference tag looks like this: [^1] This reference tag is a mix of letters and numbers. [^footnote-42] [^1]: This is the text inside a footnote. [^footnote-42]: This is another footnote. \</code>\</pre> A footnote reference tag looks like this:[^1] This reference tag is a mix of letters and numbers.[^footnote-42] \<!-- Do not delete the single space before the [^1] and [^footnotes] references below. These are used to force the Vale ReferenceLinks check to skip these examples. --> [^1]: This is the text inside a footnote. [^footnote-42]: This is another footnote. ```markdown Alternatively, for H1 and H2, an underline-ish style: Alt-H1 ====== Alt-H2 ------ ``` GitLab Flavored Markdown extends the standard Markdown standard so that all Markdown-rendered headers automatically get IDs, which can be linked to, except in comments. On hover, a link to those IDs becomes visible to make it easier to copy the link to the header to use it somewhere else. The IDs are generated from the content of the header according to the following rules: 1. All text is converted to lowercase. 1. All non-word text (such as punctuation or HTML) is removed. 1. All spaces are converted to hyphens. 1. Two or more hyphens in a row are converted to one. 1. If a header with the same ID has already been generated, a unique incrementing number is appended, starting at 1. Example: ```markdown ``` Would generate the following link IDs: 1. `this-header-has-spaces-in-it` 1. `this-header-has-a-in-it` 1. `this-header-has-unicode-in-it-한글` 1. `this-header-has-spaces-in-it-1` 1. `this-header-has-spaces-in-it-2` 1. `this-header-has-3-5-in-it-and-parentheses` Note that the emoji processing happens before the header IDs are generated, so the emoji is converted to an image which is then removed from the ID. Create a horizontal rule by using three or more hyphens, asterisks, or underscores: ```markdown Three or more hyphens, --- asterisks, *** or underscores ___ ```
Apr 02 2021
On Friday, 2 April 2021 at 10:59:09 UTC, Petar Kirov [ZombineDev] wrote:On Friday, 2 April 2021 at 10:49:38 UTC, Petar Kirov [ZombineDev] wrote:To see the second example of Markdown rendered in HTML, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#inline-html). You can also use raw HTML in your Markdown, and it usually works pretty well. See the documentation for HTML::Pipeline's [SanitizationFilter](https://github.com/jch/html-pipeline/blob/v2.12.3/lib/html/pipeline/sanitization_filter.rb#L42) class for the list of allowed HTML tags and attributes. In addition to the default `SanitizationFilter` allowlist, GitLab allows `span`, `abbr`, `details` and `summary` elements. ```html <dl> <dt>Definition list</dt> <dd>Is something people use sometimes.</dd> <dt>Markdown in HTML</dt> <dd>Does *not* work **very** well. HTML <em>tags</em> do <b>work</b>, in most cases.</dd> </dl> ``` <dl> <dt>Definition list</dt> <dd>Is something people use sometimes.</dd> <dt>Markdown in HTML</dt> <dd>Does *not* work **very** well. HTML <em>tags</em> do <b>work</b>, in most cases.</dd> </dl> --- It's still possible to use Markdown inside HTML tags, but only if the lines containing Markdown are separated into their own lines: ```html <dl> <dt>Markdown in HTML</dt> <dd>Does *not* work **very** well. HTML tags work, in most cases.</dd> <dt>Markdown in HTML</dt> <dd> Does *not* work **very** well. HTML tags work, in most cases. </dd> </dl> ``` <!-- The example below uses HTML to force correct rendering on docs.gitlab.com, Markdown is fine in GitLab. --> <dl> <dt>Markdown in HTML</dt> <dd>Does *not* work **very** well. HTML tags work, in most cases.</dd> <dt>Markdown in HTML</dt> <dd> Does <em>not</em> work <b>very</b> well. HTML tags work, in most cases. </dd> </dl> To see the second Markdown example rendered in HTML, [view it in GitLab](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#details-and-summary). Content can be collapsed using HTML's [`<details>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details) and [`<summary>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary) tags. For example, collapse a long log file so it takes up less screen space. ```html <p> <details> <summary>Click this to collapse/fold.</summary> These details <em>remain</em> <strong>hidden</strong> until expanded. <pre><code>PASTE LOGS HERE</code></pre> </details> </p> ``` <p> <details> <summary>Click this to collapse/fold.</summary> These details <em>remain</em> <strong>hidden</strong> until expanded. <pre><code>PASTE LOGS HERE</code></pre> </details> </p> --- Markdown inside these tags is also supported. NOTE: If your Markdown isn't rendering correctly, try adding `{::options parse_block_html="true" /}` to the top of the page, and add `markdown="span"` to the opening summary tag like this: `<summary markdown="span">`. Remember to leave a blank line after the `</summary>` tag and before the `</details>` tag, as shown in the example: ````html <details> <summary>Click this to collapse/fold.</summary> These details _remain_ **hidden** until expanded. ``` PASTE LOGS HERE ``` </details> ```` <!-- The example below uses HTML to force correct rendering on docs.gitlab.com, Markdown works correctly in GitLab. --> <details> <summary>Click this to collapse/fold.</summary> These details <em>remain</em> <b>hidden</b> until expanded. <pre><code>PASTE LOGS HERE</code></pre> </details> A line break is inserted (a new paragraph starts) if the previous text is ended with two newlines, like when you hit <kbd>Enter</kbd> twice in a row. If you only use one newline (hit <kbd>Enter</kbd> once), the next sentence remains part of the same paragraph. Use this approach if you want to keep long lines from wrapping, and keep them editable: ```markdown Here's a line for us to start with. This longer line is separated from the one above by two newlines, so it is a *separate paragraph*. This line is also a separate paragraph, but... These lines are only separated by single newlines, so they *do not break* and just follow the previous lines in the *same paragraph*. ``` Here's a line for us to start with. This longer line is separated from the one above by two newlines, so it is a *separate paragraph*. This line is also a separate paragraph, but... These lines are only separated by single newlines, so they *do not break* and just follow the previous lines in the *same paragraph*. GitLab Flavored Markdown adheres to the Markdown specification in how [paragraphs and line breaks are handled](https://spec.commonmark.org/current/). A paragraph is one or more consecutive lines of text, separated by one or more blank lines (two newlines at the end of the first paragraph), as [explained above](#line-breaks). Need more control over line breaks or soft returns? Add a single line break by ending a line with a backslash, or two or more spaces. Two newlines in a row create a new paragraph, with a blank line in between: ```markdown First paragraph. Another line in the same paragraph. A third line in the same paragraph, but this time ending with two spaces.{space}{space} A new line directly under the first paragraph. Second paragraph. Another line, this time ending with a backslash.\ A new line due to the previous backslash. ``` There are two ways to create links, inline-style and reference-style: <!-- Do not edit the following codeblock. It uses HTML to skip the Vale ReferenceLinks test. --> <pre class="highlight"><code>- This is an [inline-style link](https://www.google.com) - This is a [link to a repository file in the same directory](index.md) - This is a [relative link to a readme one directory higher](../README.md) - This is a [link that also has title text](https://www.google.com "This link takes you to Google!") Using header ID anchors: - This links to [a section on a different Markdown page, using a - This links to [a different section on the same page, using a Using references: - This is a [reference-style link, see below][Arbitrary case-insensitive reference text] - You can [use numbers for reference-style link definitions, see below][1] - Or leave it empty and use the [link text itself][], see below. Some text to show that the reference links can follow later. https://www.mozilla.org/en-US/ https://slashdot.org https://www.reddit.com </code></pre> - This is an [inline-style link](https://www.google.com) - This is a [link to a repository file in the same directory](index.md) - This is a [relative link to a README one directory higher](../README.md) - This is a [link that also has title text](https://www.google.com "This link takes you to Google!") Using header ID anchors: - This links to [a section on a different Markdown page, using a - This links to [a different section on the same page, using a Using references: <!-- The example below uses in-line links to pass the Vale ReferenceLinks test. Do not change to reference style links. --> - This is a [reference-style link, see below](https://www.mozilla.org/en-US/) - You can [use numbers for reference-style link definitions, see below](https://slashdot.org) - Or leave it empty and use the [link text itself](https://www.reddit.com), see below. Some text to show that the reference links can follow later. NOTE: Relative links do not allow the referencing of project files in a wiki page, or a wiki page in a project file. The reason for this is that a wiki is always in a separate Git repository in GitLab. For example, `[I'm a reference-style link](style)` points the link to `wikis/style` only when the link is inside of a wiki Markdown file. GitLab Flavored Markdown auto-links almost any URL you put into your text: ```markdown - https://www.google.com - https://www.google.com - ftp://ftp.us.debian.org/debian/ - smb://foo/bar/baz - irc://irc.freenode.net/ - http://localhost:3000 ``` <!-- vale gitlab.Spelling = NO --> - <https://www.google.com> - <https://www.google.com> - <ftp://ftp.us.debian.org/debian/> - <smb://foo/bar/baz> - <irc://irc.freenode.net/> - <http://localhost:3000> <!-- vale gitlab.Spelling = YES --> Ordered and unordered lists can be created. For an ordered list, add the number you want the list to start with, like `1.`, followed by a space, at the start of each line for ordered lists. After the first number, it does not matter what number you use, ordered lists are numbered automatically by vertical order, so repeating `1.` for all items in the same list is common. If you start with a number other than `1.`, it uses that as the first number, and count up from there. Examples: ```markdown 1. First ordered list item 2. Another item - Unordered sub-list. 1. Actual numbers don't matter, just that it's a number 1. Ordered sub-list 1. Next ordered sub-list item 4. And another item. ``` <!-- The "2." and "4." in the example above are changed to "1." below, to match the style standards on docs.gitlab.com. See https://docs.gitlab.com/ee/development/documentation/styleguide/index.html#lists --> 1. First ordered list item 1. Another item - Unordered sub-list. 1. Actual numbers don't matter, just that it's a number 1. Ordered sub-list 1. Next ordered sub-list item 1. And another item. For an unordered list, add a `-`, `*` or `+`, followed by a space, at the start of each line for unordered lists, but you should not use a mix of them. ```markdown Unordered lists can: - use - minuses They can also: * use * asterisks They can even: + use + pluses ``` <!-- The "*" and "+" in the example above are changed to "-" below, to match the style standards on docs.gitlab.com. See https://docs.gitlab.com/ee/development/documentation/styleguide/index.html#lists --> Unordered lists can: - use - minuses They can also: - use - asterisks They can even: - use - pluses --- If a list item contains multiple paragraphs, each subsequent paragraph should be indented to the same level as the start of the list item text. Example: ```markdown 1. First ordered list item Second paragraph of first item. 1. Another item ``` 1. First ordered list item Second paragraph of first item. 1. Another item --- If the paragraph of the first item is not indented with the proper number of spaces, the paragraph appears outside the list, instead of properly indented under the list item. Example: ```markdown 1. First ordered list item Paragraph of first item. 1. Another item ``` 1. First ordered list item Paragraph of first item. 1. Another item CommonMark and GitLab Flavored Markdown don't support the Redcarpet superscript syntax ( `x^2` ). Use the standard HTML syntax for superscripts and subscripts: ```html The formula for water is H<sub>2</sub>O while the equation for the theory of relativity is E = mc<sup>2</sup>. ``` <!-- vale gitlab.Spelling = NO --> The formula for water is H<sub>2</sub>O while the equation for the theory of relativity is E = mc<sup>2</sup>. <!-- vale gitlab.Spelling = YES --> Tables are not part of the core Markdown spec, but they are part of GitLab Flavored Markdown. 1. The first line contains the headers, separated by "pipes" (`|`). 1. The second line separates the headers from the cells, and must contain three or more dashes. 1. The third, and any following lines, contain the cell values. - You **can't** have cells separated over many lines in the Markdown, they must be kept to single lines, but they can be very long. You can also include HTML `<br>` tags to force newlines if needed. - The cell sizes **don't** have to match each other. They are flexible, but must be separated by pipes (`|`). - You **can** have blank cells. Example: ```markdown | header 1 | header 2 | header 3 | | --- | ------ |----------| | cell 1 | cell 2 | cell 3 | | cell 4 | cell 5 is longer | cell 6 is much longer than the others, but that's ok. It eventually wraps the text when the cell is too large for the display size. | | cell 7 | | cell 9 | ``` | header 1 | header 2 | header 3 | | --- | ------ |----------| | cell 1 | cell 2 | cell 3 | | cell 4 | cell 5 is longer | cell 6 is much longer than the others, but that's ok. It eventually wraps the text when the cell is too large for the display size. | | cell 7 | | cell 9 | Additionally, you can choose the alignment of text in columns by adding colons (`:`) to the sides of the "dash" lines in the second row. This affects every cell in the column: ```markdown | Left Aligned | Centered | Right Aligned | Left Aligned | Centered | Right Aligned | | :--- | :---: | ---: | :----------- | :------: | ------------: | | Cell 1 | Cell 2 | Cell 3 | Cell 4 | Cell 5 | Cell 6 | | Cell 7 | Cell 8 | Cell 9 | Cell 10 | Cell 11 | Cell 12 | ``` | Left Aligned | Centered | Right Aligned | Left Aligned | Centered | Right Aligned | | :--- | :---: | ---: | :----------- | :------: | ------------: | | Cell 1 | Cell 2 | Cell 3 | Cell 4 | Cell 5 | Cell 6 | | Cell 7 | Cell 8 | Cell 9 | Cell 10 | Cell 11 | Cell 12 | [In GitLab itself](https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md#tables), the headers are always left-aligned in Chrome and Firefox, and centered in Safari. You can use HTML formatting to adjust the rendering of tables. For example, you can use `<br>` tags to force a cell to have multiple lines: ```markdown | Name | Details | |------|---------| | Item1 | This is on one line | | Item2 | This item has:<br>- Multiple items<br>- That we want listed separately | ``` | Name | Details | |------|---------| | Item1 | This is on one line | | Item2 | This item has:<br>- Multiple items<br>- That we want listed separately | You can use HTML formatting in GitLab itself to add [task lists](#task-lists) with checkboxes, but they do not render properly on `docs.gitlab.com`: ```markdown | header 1 | header 2 | |----------|----------| | cell 1 | cell 2 | | cell 3 | <ul><li> - [ ] Task one </li><li> - [ ] Task two </li></ul> |On Friday, 2 April 2021 at 10:47:55 UTC, Petar Kirov [ZombineDev] wrote:On Friday, 2 April 2021 at 10:33:46 UTC, Petar Kirov [ZombineDev] wrote:[..]Compare with https://gitlab.com/gitlab-org/gitlab/blob/master/doc/user/markdown.md
Apr 02 2021
On Thursday, 1 April 2021 at 07:26:52 UTC, Vladimir Panteleev wrote:On Thursday, 1 April 2021 at 06:35:11 UTC, Vladimir Panteleev wrote:| A | B | C | |----------------------------------|-------------------------------|----| | A | B | C | | A | B | C |[snip]test*test*test
Jun 17 2021
On Thursday, 1 April 2021 at 07:26:52 UTC, Vladimir Panteleev wrote:On Thursday, 1 April 2021 at 06:35:11 UTC, Vladimir Panteleev wrote:- foo - bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar - baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz baz[snip]test*test*test
Jun 17 2021
On Friday, 17 February 2012 at 12:16:06 UTC, Vladimir Panteleev wrote:testTest
Feb 16 2022