Axel Kohlmeyer

> Just to add to this, the current approach for building the docs also requires access to the internet...there is no (offline) way to provide the necessary packages to the...

@lubbersnick can you please check this out?

@chemshift thanks for your submission. I think part of the solution is that you are using Python 3.10.5. There have been issues with sub-interpreters for multiple 3.10.x versions that also...

This has been sitting for over a month now without any followup or other reaction. Since it doesn't look like it won't make much of a difference anyway, I am...

This has been inactive for a while. Are there any updates?

> @akohlmey @sjplimp Did anybody had a look at these issues? Is there a chance that any of these will be fixed in not too distant future? @antonpeshkov Please understand...

> yes, this is great idea. I know we've made this reference on a handful of doc pages, but nothing systematic. Given the suggested syntax, I think it would best...

> @rbberger Do you want to write a Python script to scan the example dirs for style commands, and auto-add these one-liners to doc/*.rst files? Not so sure about this...

> We could make them link to the folder/files on GitHub. E.g. > > > Example input scripts available: [examples/VISCOSITY](https://github.com/lammps/lammps/tree/master/examples/VISCOSITY), [examples/KAPPA](https://github.com/lammps/lammps/tree/master/examples/KAPPA) > > That way we don't have to have...

> @akohlmey @jtclemm > Also were those input script names going to be links? Is that easy/possible? I don't see a clean way to link those inputs. The GitHub master...