fz0x1/HPI
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

link using heading instead of id

Browse source
This commit is contained in:
Sean Breckenridge 2021-04-11 00:50:44 -07:00
parent cabdddee23
commit 2d6dc17903
2 changed files with 1 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

3
doc/MODULE_DESIGN.org
View file

@ -55,9 +55,6 @@ Not all HPI Modules are currently at that level of complexity -- some are simple
A related concern is [[*An Extendable module structure][how to structure namespace packages]] to allow users to easily extend them, and how this conflicts with single file modules. If a module is converted from a single file module to a namespace with multiple files, it seems this is a breaking change, see [[https://github.com/karlicoss/HPI/issues/89][#89]] for an example of this. A related concern is [[*An Extendable module structure][how to structure namespace packages]] to allow users to easily extend them, and how this conflicts with single file modules. If a module is converted from a single file module to a namespace with multiple files, it seems this is a breaking change, see [[https://github.com/karlicoss/HPI/issues/89][#89]] for an example of this.
* Adding new modules * Adding new modules
:PROPERTIES:
:CUSTOM_ID: addingmodules
:END:
As always, if the changes you wish to make are small, or you just want to add a few modules, you can clone and edit an editable install of HPI. See [[file:SETUP.org::*Adding/modifying modules][adding/modifying modules]] As always, if the changes you wish to make are small, or you just want to add a few modules, you can clone and edit an editable install of HPI. See [[file:SETUP.org::*Adding/modifying modules][adding/modifying modules]]

3
doc/SETUP.org
View file

@ -464,5 +464,4 @@ Also check out [[https://beepb00p.xyz/myinfra.html#hpi][my personal infrastructu
# TODO eh. doesn't even have to be in 'my' namespace?? need to check it # TODO eh. doesn't even have to be in 'my' namespace?? need to check it
- The "proper way" (unless you want to contribute to the upstream) is to create a separate file hierarchy and add your module to =PYTHONPATH=. - The "proper way" (unless you want to contribute to the upstream) is to create a separate file hierarchy and add your module to =PYTHONPATH=.
See [[file:MODULE_DESIGN.org::#addingmodules][MODULE_DESIGN/adding modules]] for more information See [[file:MODULE_DESIGN.org::*Adding new modules][MODULE_DESIGN/adding modules]] for more information