This is somewhere between a bug and feature request.

I often like to put source references (source:/a_file) in brackets, the trouble is the ) is interpreted as part of the file (which makes sense). What would be nice is if I could delimiter the end of the source path with brackets or a character so that I don’t have to leave white space where I don’t really want to.

A workaround is using (source:/a_file@1), but this is a tiny bit misleading for readers if the reference is general.

Another nice thing would be if source references could carry link text like other references. Something like:

{source:/a_file | Mary’s astonishing code}

Thanks for your feedback Silas.

Currently, the “source:” links do not work for paths with spaces in the filenames. This would necessitate the need for some more specific markup, particularly something to delimit the end of the path. We will certainly consider this for a future release.

We may also consider adding a way to specify custom link text, however, I think that seeing the path is probably helpful in most cases here as it probably helps to give some context for where the link will go.

Yes, I would like the default link text to be the path, but occasionally would like to use link text that fits into a sentence and is not the path.

That makes sense. We will keep that in mind as we make these updates.

Thanks again for your feedback!