晋太元中，武陵人捕鱼为业。缘溪行，忘路之远近。忽逢桃花林，夹岸数百步，中无杂树，芳草鲜美，落英缤纷。渔人甚异之，复前行，欲穷其林。 　　林尽水源，便得一山，山有小口，仿佛若有光。便舍船，从口入。初极狭，才通人。复行数十步，豁然开朗。土地平旷，屋舍俨然，有良田、美池、桑竹之属。阡陌交通，鸡犬相闻。其中往来种作，男女衣着，悉如外人。黄发垂髫，并怡然自乐。 　　见渔人，乃大惊，问所从来。具答之。便要还家，设酒杀鸡作食。村中闻有此人，咸来问讯。自云先世避秦时乱，率妻子邑人来此绝境，不复出焉，遂与外人间隔。问今是何世，乃不知有汉，无论魏晋。此人一一为具言所闻，皆叹惋。余人各复延至其家，皆出酒食。停数日，辞去。此中人语云：“不足为外人道也。”(间隔 一作：隔绝) 　　既出，得其船，便扶向路，处处志之。及郡下，诣太守，说如此。太守即遣人随其往，寻向所志，遂迷，不复得路。 　　南阳刘子骥，高尚士也，闻之，欣然规往。未果，寻病终。后遂无问津者。 .
Prv8 Shell
Server : Apache
System : Linux srv.rainic.com 4.18.0-553.47.1.el8_10.x86_64 #1 SMP Wed Apr 2 05:45:37 EDT 2025 x86_64
User : rainic ( 1014)
PHP Version : 7.4.33
Disable Function : exec,passthru,shell_exec,system
Directory :  /proc/thread-self/root/usr/share/doc/environment-modules/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : //proc/thread-self/root/usr/share/doc/environment-modules/CONTRIBUTING.txt
Contributing
************

Thank you for considering contributing to Modules!


Support questions
=================

Please use the modules-interest mailing list for questions. Do not use
the issue tracker for this.


Asking for new features
=======================

Please submit your new feature wishes first to the modules-interest
mailing list. Discussion will help to clarify your needs and sometimes
the wanted feature may already be available.


Reporting issues
================

* Describe what you expected to happen.

* If possible, include a minimal, complete, and verifiable example
  to help us identify the issue.

* Describe what actually happened. Run the "module" command in "--
  debug" mode and include all the debug output obtained in your
  report.

* Provide the current configuration and state of your Modules
  installation by running the "module config --dump-state" command.

* Provide the name and content of the modulefiles you try to
  manipulate.


Submitting patches
==================

* Whether your patch is supposed to solve a bug or add a new
  feature, please include tests. In case of a bug, explain clearly
  under which circumstances it happens and make sure the test fails
  without your patch.

* If you are not yet familiar with the "git" command and GitHub,
  please read the don't be afraid to commit tutorial.


Start coding
------------

* Create a branch to identify the issue or feature you would like to
  work on

* Using your favorite editor, make your changes, committing as you
  go.

* Comply to the coding conventions of this project.

* Include tests that cover any code changes you make. Make sure the
  test fails without your patch.

* Run the tests and verify coverage.

* Push your commits to GitHub and create a pull request.


Running the tests
-----------------

Run the basic test suite with:

   make test

This only runs the tests for the current environment. Travis-CI and
AppVeyor will run the full suite when you submit your pull request.


Running test coverage
---------------------

Generating a report of lines that do not have test coverage can
indicate where to start contributing or what your tests should cover
for the code changes you submit.

Run "make test COVERAGE=y" which will automatically setup the Nagelfar
Tcl code coverage tool in your "modules" development directory. Then
the full testsuite will be run in coverage mode and a "modulecmd-
test.tcl_m" annotated script will be produced:

   make test COVERAGE=y
   # then open modulecmd-test.tcl_m and look for ';# Not covered' lines


Building the docs
-----------------

Build the docs in the "doc" directory using Sphinx:

   cd doc
   make html

Open "_build/html/index.html" in your browser to view the docs.

Read more about Sphinx.


Coding conventions
------------------

* Maximum line length is 78 characters

* Use 3 spaces to indent code (do not use tab character)

* Adopt Tcl minimal escaping style

* Procedure names: "lowerCameCase"

* Variable names: "nocaseatall"

* Curly brace and square bracket placement:

     if {![info exists ::g_already_report]} {
        set ::g_already_report 1
     }


Emacs settings for coding conventions
-------------------------------------

This is an example emacs configuration that adheres to the first two
coding conventions.  You may wish to add this to your ".emacs" or
".emacs.d/" to modify your tcl-mode:

   (add-hook 'tcl-mode-hook
      (lambda ()
        (setq indent-tabs-mode nil)
        (setq tcl-indent-level 3)
        (setq tcl-continued-indent-level 3)
        (font-lock-add-keywords nil '(("^[^\n]\\{79\\}\\(.*\\)$" 1
                                       font-lock-warning-face prepend)))))


Submitting installation recipes
===============================

* If you want to share your installation tips and tricks, efficient
  ways you have to write or organize your modulefiles or some
  extension you made to the "module" command please add a recipe to
  the cookbook section of the documentation.

* Create a directory under "doc/example" and put there the extension
  code or example modulefiles your recipe is about.

* Describe this recipe through a reStructuredText document in
  "doc/source/cookbook". It is suggested to have an *Implementation*,
  an *Installation* and an *Usage example* sections in that document
  to get as much as possible the same document layout across recipes.

* Submit a patch with all the above content.

haha - 2025