Peter Hill

Oh dear! Thanks for the bug report @maurerben. Would you be able to post or upload the smallest example that reproduces the issue? That will make it easier for us...

@tuncaen I think this might still be a problem. I've reopened the issue so we can track it. At the very least, it needs some tests adding to check that...

My first guess was going to be something to do with it being an M1 CPU, but this is actually on an x86, so probably not that... The other thing...

Hi @Meax5qiu , sorry for the slow reply, it's been a very busy month! Currently, the only way is use the full path, although we have a [`|url|`](https://github.com/Fortran-FOSS-Programmers/ford/wiki/Writing-Documentation#macros) macro that...

Fantastic, thanks @haraldkl !

Yes please, that would be lovely!

Yes, I think you'll need to modify both. `FortranReader` throws away non-docstring comments and normalises `predocmark/altdocmark` comments to `docmark` ones. So one thing you could do is to convert an...

Hi @ecasglez, you can make this work by adding: ``` md_extensions: markdown.extensions.toc ``` to your `doc.md` configuration file. This uses the [table of contents extension](https://python-markdown.github.io/extensions/toc/) which adds the link anchors...

It is [buried in the wiki](https://github.com/Fortran-FOSS-Programmers/ford/wiki/Project-File-Options#md_extensions), but it isn't obvious that this extension does what you want. Github-flavoured markdown does enable this behaviour by default (which is dialect of markdown...

I think with the current implementation this is basically inevitable, and it would be very difficult to fix. Instead, this could be implemented using the [markdown Extension API](https://python-markdown.github.io/extensions/api/#inlineprocessors). This might...