happy-kitchen-89482
07/18/2022, 8:24 PMhundreds-father-404
07/18/2022, 8:24 PMhappy-kitchen-89482
07/18/2022, 9:01 PMhundreds-father-404
07/18/2022, 9:46 PMhappy-kitchen-89482
07/18/2022, 9:46 PMhundreds-father-404
07/18/2022, 9:49 PMhappy-kitchen-89482
07/18/2022, 9:54 PM[block:code]
{
"codes": [
{
"code": "BLAH",
"language": "text",
"name": "FOO"
}
]
}
[/block]
hundreds-father-404
07/18/2022, 9:56 PMhappy-kitchen-89482
07/18/2022, 9:56 PMhundreds-father-404
07/18/2022, 9:56 PMbut if I create a new Code Sample block then in the raw markdown it's this:Are you using the old editor? It should not be this. It should be new style markdown
See above for what custom markdown is required in order to render those blocksNack
happy-kitchen-89482
07/18/2022, 9:57 PMhundreds-father-404
07/18/2022, 9:57 PM```python f1.py
> print()
> ```
```python f2.py
> print()
> ```may be worth trying out. I suspect they only render file names if >1 tab
happy-kitchen-89482
07/18/2022, 9:58 PMmay be worth trying out. I suspect they only render file names if >1 tab
hundreds-father-404
07/18/2022, 9:59 PMhappy-kitchen-89482
07/18/2022, 9:59 PMhundreds-father-404
07/18/2022, 9:59 PMThat would be a huge regression if trueYep, which I suspect is a bug. The readme.com team is very responsive and would likely want to fix this
happy-kitchen-89482
07/21/2022, 11:48 PMbash
./pants --level=debug ...
would have to be re-written to look like this:
[block:code]
{
"codes": [
{
"code": "./pants --level=debug ...",
"language": "bash"
}
]
}
[/block]
"hundreds-father-404
07/21/2022, 11:58 PMblock
syntax because it's so clunky and hard to read)happy-kitchen-89482
07/22/2022, 5:13 PMhundreds-father-404
07/22/2022, 5:28 PMWe can always preprocess before uploading I guess?Sort of. We right now run the readme tool directly I think. So we'd add a new step to the process
happy-kitchen-89482
07/22/2022, 5:40 PMhundreds-father-404
07/22/2022, 5:47 PM