It is always true that the documentation can be improved. We try to follow this model for new changes:

If some chunks of explanation (say Latex or accented characters) really is useful in more than one place, then we make a single file with extension.rst_ and we include that file in the places the content should go. This means we only have one place to maintain and fix for typos or extensions even though it appears in more than one place in the docs.

Over the years we have made changes to fit this model but there are tons of places that could benefit from this treatment. Last week I added this to both grdmath and gmtmath documentation just after the description:

.. include:: RPN_info.rst_

and that file shows some relevant images and captions that discusses Reverse Polish Notation, for instance.

That include model is better than my idea. Would you mind me giving it a shot for the escape characters and consolidate that info into a single file?

@PaulWessel - After re-reading my initial post it sounds a bit harsh/aggressive – that wasn't my intention. I know how hard it can be to document things properly and then maintaining it. If you felt this way, please accept my apologies. I just saw a possible area for improvement where I don't have to rely on your work and time to improve it but could do it myself.

No worries Kristof, I have thick skin and did not even notice anything negative.

Phew. Glad to hear! Do you think it is worthwhile me going ahead with this?

Sure, I think any improvement is good.