-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
perhaps one more suggestion:
Examples:

Is there a way to make the module command show different parts of this
depending on whether you say
module spider
or module help?
And for
module spider
Is there a chance that
module spider blabla foe examples only shows which versions of blabla
are available whereas
module spider blabla1.2 shows additional information for version 1.2?
Usually it is a too much information if
module spider blabla
not only shows what blabla is and which versions are avaialble but
also the complete description of one of the versions. I even do not
know how the version is chosen.
Inge Gutheil

On 02/10/17 16:40, Markus Geimer wrote:
> Hi all,
>
> Following up on my proposal for extended package documentation
> options sent to the list recently [1], I have a question to the
> community. During the hackathon part of the User Group Meeting, I
> implemented the proposal (cfr. [2]) for `module help`.  Now, the
> question came up which of the information should also be included
> in the `whatis` output and how.  Would something in key/value
> style, like
>
> Description: Bla bla Usage: More bla Homepage: http://foo.org
> Documentation: $EBROOTFOO/some/path Documentation: http://some.url
> Support: [email protected] Contact: Jim Admin Contact: Jane Admin
> Extensions: ext1-0.1, ext2-42.7
>
> work for the community?
>
> Looking forward to your feedback.
>
> Markus
>
>
> [1]
> https://www.mail-archive.com/[email protected]/msg03050.html
>
>
[2] https://github.com/hpcugent/easybuild-framework/pull/2113
>
> -- Dr. Markus Geimer Juelich Supercomputing Centre Institute for
> Advanced Simulation Forschungszentrum Juelich GmbH 52425 Juelich,
> Germany
>
> Phone:  +49-2461-61-1773 Fax:    +49-2461-61-6656 E-Mail:
> [email protected] WWW:    http://www.fz-juelich.de/jsc
>
>
> ------------------------------------------------------------------------------------------------
>
>
-
------------------------------------------------------------------------------------------------
> Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft:
> Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr.
> HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen
> Huthmacher Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt
> (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof.
> Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt
> ------------------------------------------------------------------------------------------------
>
>
-
------------------------------------------------------------------------------------------------
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJYosc2AAoJEAMTTHwPbmtK+gkP/jgDtFpxmJ66/Me3qxyLlPA+
Bl8SaDw1Uf1n3OmwHc+fisiojtj5nXPfcNPgpz5XJT/UomJiz8gqntVsPgugF/PI
X42E9WPMnfe/vpJy+1FaoFnVQkblN/2hctKTBmlrkbChZrdRDcbuHKt47HfAwrds
85+3TtnIrQzT6yqJhfiD/e46mihtxDDXlDVJyIeTKSccV0CgEgAqNyjg6x2T0+pO
b3Apz3w+j5LM12UoT6A3Uxhwrn2SJthOfZEdjVc+uUWol62ti2mCjJgv1kW5p6+G
/3RXIfiKJFpZCPCr4pTFBDYM0cjYTwhLqoDC58h24fUazcEIBgWirIbFU9SVMbSX
lB+vBqmeGr16b+BuyXj+1J8TUw0ZUqT1E/a5CLr3XfTHXuEDVEAFlVGmXk3Nt/ee
vAvfDnP+dswadWLZpgWYpK/+FYCT3G8DXOmsQ+5pMBMJTHIwdmijCeZxBgSG/u6I
aNwqH/8ZVF6p24K/y9IAIYvum5zPxjcOpc+8WWFY4xHg4Nsj2eUmoJtlcaQgH8LT
zcY9L16Oz9p4Jv23QjXE2qc2HOcXfMh5BxCXLMKYeIy8h3YZ+XWSjlx9NBnktEvO
7deITf/rIz3zrQ63yWobXvty8s/Q3nxTWRYjb+rlIK6av8VDQrvfiNQGqTfta26D
dv7NV4faG29VBdqe22/Y
=QSSP
-----END PGP SIGNATURE-----


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to