Thank you for taking the time to answer.
I know I can name chunks, I should have named the chunks in my example to make what I want more visible.
In the link you refer about chunk labels you can read:
Chunk labels are mainly used in filenames of plots and cache. If the label of a chunk is missing, a default one of the form
unnamed-chunk-i will be generated, where
i is incremental. I strongly recommend that you only use alphanumeric characters (
0-9 ) and dashes (
- ) in labels, because they are not special characters and will surely work for all output formats. Other characters, spaces and underscores in particular, may cause trouble in certain packages, such as bookdown ."
You are suggesting I use long form descriptive text as the label name of a chunk.
This is not a good solution.
What I want is to separate my code from the commenting of my code.
Also, I use code folding to hide complexity.
A long form comment on the second line on the chunk could replace the entire first line.
This would hide more of the complexity and increase readibility a lot.
Also, the Folding functionality could be expanded even further to be even more useful, especially in Rmarkdown contexts - you can use Rstudio as an outlining tool; Fold structures and then reorder them with drag and drop. If the Folding works as I suggest, you can drag and drop the entire line up and down to reorder your document, instead of copy+paste and make sure the icon representing the folded text stays where it should.
(EDIT: I'll edit my first comment later to put all pictures in to one, and clafiry what I'm suggesting as a feature)