Help with Intel oneAPI documentation in Emacs/Eclipse

[Hongyi]

Intel provides the wonderful “Intel® Fortran Compiler Classic and Intel® Fortran Compiler Developer Guide and Reference” here, a.k.a., the HTML (F1 Help) documentation.

But the official instructions for using this documentation are only for Microsoft Visual Studio. So, I wonder if anyone here has experience with this HTML (F1 Help) Intel oneAPI Documentation to facilitate the Fortran development in Emacs/eclipse.

Regards,
HZ

[Hongyi]

The above official HTML (F1 Help) documentation webpage is located here:

Download Documentation: Intel® Compiler (Current and Previous)

[Aurelius_Nero]

Sorry to necro this, but you can refer to these threads (also you could use vterm in emacs side by side of your code if you want):

Emacs tip exchange

It seems we have a decent contingent of Emacs users in this group, so let’s pool together our knowledge! Use this thread to post customizations/elisp snippets/packages that you find useful. This thread can also be a place to ask questions and troubleshoot issues you encounter with Emacs generally, fortran-mode, f90-mode, or any Fortran-adjacent packages.

Fully-featured Fortran setup for Linux/Mac in Emacs (Intel Fortran support included!)

Hi everyone, we here from the Doom Emacs project recently completed its brand-new Fortran Module. Out of the box, it automatically supports: Integration with fpm. LSP support via fortls. Auto-formatting via fprettier. (Optional) Intel Fortran! (Otherwise gfortran is the default). This should provide a fully-featured, modern Fortran setup for anyone on Linux or MacOS. The Intel support is especially important, given how much of a pain its installation / editor integration has been outside of t…

[Hongyi]

@Aurelius_Nero

also you could use vterm in emacs side by side of your code if you want

What is the role of vterm here? I still haven’t figured it out.

[Aurelius_Nero]

if you don’t want to use the built in feature of the doom Emacs module to compile and run your code or you want to use vanilla Emacs. You can run vterm (which is a terminal emulator) in an emacs buffer, and do it manually like :

<compiler>  <tags> <filename> -o <output_file>

Point is you can have your code and the terminal(vterm) side by side in Emacs and it functions like an IDE (I guess).