Annotations for blocks that doesn't contain code.

[UltraInstinct05]

Is it possible to add code annotations feature (https://squidfunk.github.io/mkdocs-material/reference/code-blocks/#adding-annotations) to markdown fenced blocks that are not language blocks

As an example, take the following situation. Here the following is just wrapped in ``` but it doesn't define a language, but I'd still like to use code annotations (it's not code) to describe some information. The problem is, it just doesn't define any language, so there is no concept of comments.

.
└── dir_a/
    ├── dir_b # Add a code annotation here describing something special, but # is not a comment char.
    ├── file_1.py
    └── file_2.py

[UltraInstinct05]

Looks like I just forgot to read the footnotes :) Seems to be on the roadmap https://squidfunk.github.io/mkdocs-material/reference/code-blocks/#fn:1

[ewels]

Only other method I can think of which is completely general is to stay out of the code block altogether and do everything with line numbers.

For example, maybe:

```txt linenums="1"
Some code
Block here
And stuff
```
* (1) Annotation on first line
* (3) Another annotation on third line

[squidfunk]

I also already thought of adding that functionality, but that would only allow to append code annotations, not insert them arbitrarily, which is why for now I've not considered implementing this approach.

[ewels]

Could always have an optional character start point as well, using a : character?

```txt linenums="1"
Some code
Block here
And stuff
```
* (1) Annotation on first line (appended)
* (3:4) Another annotation on third line (starting after "And")

[squidfunk]

With Insiders 4.32.0, code annotations can now be placed anywhere. Material for MkDocs can be configured per-language to allow for code annotations in other lexemes than comments, e.g. strings. See the documentation on custom selectors.

[ewels]

Awesome - thank you! 👏🏻🎉

[UltraInstinct05]

Is this a bug in code annotations ? I have this example (Windows 11, Firefox Nightly, Google Chrome)

    ```sh
    dir_a/
    ├── dir_b/
    │   ├── file_1.py # (1)
    │   ├── file_2.py # (2)
    │   └── file_3.py # (2)
    ├── dir_c/
    └── ...other directories
    ```

    1. Code annotation example 1.
    2. Code annotation example 2.

Annotation 1 renders properly

Annotation 2 doesn't work

Annotation 3 renders properly

[UltraInstinct05]

It looks like I have to define separate numbers for it to not break, which actually breaks re usability.

    1. Code annotation example 1.
    2. Code annotation example 2.
    3. Code annotation example 2.

[squidfunk]

Annotations can only be referenced once, not twice. The reason for this is that the content of the annotation is moved out of the document tree right into the tooltip. No copying or anything is involved. When printed, the content is moved back into the list, so annotations are printable. In order to allow multiple uses of the same annotation, we would need to clone the node, which might lead to unpredictable results.