I think that the bug description contains a vital clue to both the issue and (IMO) the solution.
Both the OP and myself think of 'verbatim' in terms of *blocks*... in fact, it sooo does not make sense to me that verbatim might be applied to *part* of a line that I had to test it before writing this comment.
Relatedly, I think the issue with the leading space is actually a workaround to satisfy the wiki markup parser, which would not like "<verbatim><whitespace>"... so we use "<whitespace><verbatim>".
Particularly if you take into account any workflow which might need to get *BACK* verbatim output (e.g. from the *.txt file, like log entries, etc)... the correct implementation should be to manage verbatim regions as *blocks* instead of spans.
I also checked, and using a three-single-quote (on their own line) *DOES* currently yield a block quote; with a side effect of indentation... but (at a wiki-source level) it *already-works* as expected! :)
That means that the only real issue, IMO, is that the verbatim tool uses the two-single quotes rather than the whole-block-of-lines block quote.
I think that the bug description contains a vital clue to both the issue and (IMO) the solution.
Both the OP and myself think of 'verbatim' in terms of *blocks*... in fact, it sooo does not make sense to me that verbatim might be applied to *part* of a line that I had to test it before writing this comment.
Relatedly, I think the issue with the leading space is actually a workaround to satisfy the wiki markup parser, which would not like "<verbatim> <whitespace> "... so we use "<whitespace> <verbatim> ".
Particularly if you take into account any workflow which might need to get *BACK* verbatim output (e.g. from the *.txt file, like log entries, etc)... the correct implementation should be to manage verbatim regions as *blocks* instead of spans.
I also checked, and using a three-single-quote (on their own line) *DOES* currently yield a block quote; with a side effect of indentation... but (at a wiki-source level) it *already-works* as expected! :)
That means that the only real issue, IMO, is that the verbatim tool uses the two-single quotes rather than the whole-block- of-lines block quote.