Code Block Content Tabs - Without Indent

[flywire]

https://squidfunk.github.io/mkdocs-material/reference/content-tabs/#grouping-code-blocks

Code blocks are one of the primary targets to be grouped, and can be considered a special case of content tabs...

The blocks are already marked. Why not optionally support existing end of block as end of tab content instead of requiring indenting?

Should this be posted to https://github.com/facelessuser/pymdown-extensions for @facelessuser ?

[facelessuser]

Because it works better with how Python Markdown parses things. And yes, this is probably not a Material question.

[facelessuser]

I'm not sure what we are referring to here as "legacy".

If we are talking about the first tab implementation that was specific to only code, then it used a special variable in code headers:

```language tab="title"
...
```

This was built into SuperFences but only worked for code blocks.

Then we introduced the Tabbed extension which could allow any content of any complexity.

=== "Title"
    paragraph

    - list
    - list
    
    > block quote

The old way was retired and we only allow the generic way. This is not code block specific and doesn't care if you have one code block many code blocks or no code blocks.

Now if we are talking Tabbed vs Tabbed with alternate_style = True, nothing changed in syntax, just output.

[flywire]

I don't suppose I'm keen to run a depreciated version. Was there a conversion process for a file formatted for the first tab implementation? My use case is many many existing and new code snippets (eg 1 or 2 [unformatted]) I want to push into tabs. Then I want to replicate the tabs for other languages.

Why? It's convenient to add code without indenting it, maybe just an include statement (possibly recalling sphinx).

[facelessuser]

Was there a conversion process for a file formatted for the first tab implementation?

Just manually changing the syntax to match the new syntax. There is no automated process.

Why? It's convenient to add code without indenting it, maybe just an include statement (possibly recalling sphinx).

I'm not sure exactly what is being asked here really. Unfortunately, I cannot change the syntax for a single user's use case. As I mentioned, part of the reason the syntax is implemented the way it is is due to Python Markdown's parser. And since it is not code block specific, I do not have a code block specific convenience approach.

[facelessuser]

It is possible that you could write your own conversion process.

[flywire]

Conversion using GNU sed on Windows:

sed '/^^```/{ s/^^/=== "Title"\n    /; :a; n; s/^^/    /; /^^    ```$/b; ba; }' file.md

Source