Morten Piibeleht

Yep, working on that :slightly_smiling_face:

Also `\u2029`: http://timelessrepo.com/json-isnt-a-javascript-subset _Technically_, in ECMAScript 2019 (10th edition), it is no longer necessary, since [the standard now allows U+2028 and U+2029 in strings](https://www.ecma-international.org/ecma-262/10.0/index.html#sec-literals-string-literals). But it's probably better to err...

No, it's not an `iframe`, it is a copy. But we could try to experiment with an `iframe` (and maybe have a small UI indicator saying that "hey, we're just...

> I think for example all SciML-internal packages that are “at home” in this MultiDoc do not necessarily need that indicator but external ones would? Yeah, I assume that `https://docs.sciml.ai/`...

Here's a rough mockup of what I had in mind (the colors might only work in dark mode): https://mortenpi.eu/mockups/sciml-ferrite/  A couple of potential issues that popped into my head...

> @mortenpi a minimal feature that we would need next is the ability to link to external docstring canonical locations, so for example I could have `Normal` link over to...

Alright, new approach (since checking whether the user has modified `CMAKE_Fortran_FLAGS` wasn't reliable): * We still automatically append `-fno-automatic` to `CMAKE_Fortran_FLAGS` _if_ we detect that it's `gfortran`. * With `ifort`...

Ok, this is actually cool. With a proper Intel `ifort`+MKL+MPI installation, just doing ``` FC=ifort BLA_VENDOR=Intel10_64lp_seq ./configure.sh ``` seems to automatically configure a CMake build that uses MKL (via `FindBLAS`)...

Are you saying that you're actually getting a compilation error with unmodified GRASP here? Because I can't really replicate that.

What's the `gfortran` version? It might be that it has become more picky about what it does and doesn't allow.