Peter Hill
Peter Hill
Along with the original developer @cmacmackin, I'm one of the maintainers on [FORD](https://github.com/Fortran-FOSS-Programmers/ford), a Fortran documentation generator, and our parsing module is starting to get a bit old and creaky....
If point is at the end of a line containing an existing key-value pair, f90-namelist-insert-key-value inserts the new pair at the beginning of the line, instead of on a new...
The regexp `^ *[^!]` matches comment lines that begin with whitespace.
Maybe we should jump to the end of file/end of current namelist and insert a new one there?
Some features to be added for the rewrite ### Tidying up - [x] Sort out colours in print statements (fixed in f965d613b2b3508d4266c738a96369790023b5c4) - [ ] Sort out depends by file/module...
[This line][1] explicitly ignores headers ending in ".hxx", even though they are included in the [list of header extensions][2]. Is this done on purpose? Forgive me if I'm being dim,...
Thanks for the great tool! I'm using it on a few projects, and one thing that's bugging me is the very noisy output when `fprettify` encounters a long line: ```...
I'd quite like to start using some Python 3.8 features, notably assignment expressions ("walrus operator"). This would mean dropping support for Python 3.7, which is end of life (EOL) next...
There are three functions in `utils.py` that add Ford-specific features to the markdown: - `sub_macros`: replace `|aliases|` with literal text - `sub_notes`: replace `@notes` with `div` element boxes - `sub_links`:...
FORD links like `[[module:subroutine]]` in a triple-backtick code block get parsed as links rather than raw text. MVCE: foo.f90: ```Fortran subroutine foo end subroutine foo ``` config.md: --- src_dir: ....