Output as markdown

Hi,

I’m not sure if it is a Cody problem or a GPT-4o problem :frowning:

I tried to let Cody optimize my Readme.md file, but the output isn’t in Markdown format. I usually chat with it and ask: “Optimize the readme.md. output in Markdown format” with the readme.md as context. It then starts to print the result in Markdown, but after a few lines, it switches back to the usual output.

Is there a way to get a readme.md in markdown format?

Ralph

It’s a rendering problem. It outputs the markdown in code blocks (as it uses markdown itself for all its formatting), but then it inserts code blocks in the markdown output and the formatter gets confused between what’s intended to be display formatting and what’s part of the readme.

Copy the entire response with the button at the bottom and paste it into an empty file, your full content should be there.

I don’t have a copy button for the whole response. Only the code blocks have a copy button :frowning:

Actually, I can copy all manually, but I lose all the markdown formatting and have to add them after pasting.

Strange, you’re right I’m not seeing it now either, but I do see a banner saying “Cody updated to v1.26”. Maybe they removed it? I hope it comes back soon, it’s very much needed especially in situations like this.

I will let the product team know. Thanks for reporting!

2 Likes

@ralph-bergmann I know it’s been a while but wanted to close the loop. We now have a copy and apply button.

Zight 2024-10-12 at 9.02.21 AM.png

The Copy and Apply buttons help only with copying the code in the code block. But the more serious problem is that after the ```…``` code block, Cody might have included more output intended to be included in the file that it was creating, or whatever, but all that following content ends up outside the code block, and looks fine if the text was markdown, but it is not copyable as markdown source. Copy-pasting that content as plain text requires that I (or an AI) reformat the text as markdown source.

The problem is caused by the incorrectly parsing the final “```”, which ends the code block itself rather than ending the block of text that was supposed to be embedded inside the code block. In the example above, after the “Install required plugins” item, the “```sh …” block should be terminated with another “```”, and then item 2 would be next, etc.

Hey @dlaliberte

This is a known issue to the team and already reported here on GitHub

This is a tricky implementation to recognize nested triple backticks in the response message in a MarkDown formatted block.

Thank you for reporting this issue and sorry for the inconvenience.

1 Like