Re: [NTG-context] contextproject script (was: Typesetting Markdown - Part 8)

28 Apr 2020

...
Am 28.04.2020 um 16:12 schrieb Jan-Erik Hägglöf :
...
28 apr. 2020 kl. 09:33 skrev Henning Hraban Ramm :
Yes, the naming is completely up to you.
I use:
project_something.tex
env_something.tex
prd_oneissue.tex
c_onechapter.tex
That’s also what my script supports as default:
https://github.com/fiee/tools/blob/master/contextproject.py
...
Is there a running example ? I’m not sure how to fill in the commandline
1) Have a look at https://wiki.contextgarden.net/Project_structure

2) To avoid the whole name, I set:
alias mkprj='python3 ~/workspace/tools/contextproject.py'

3) 
$ mkprj --help
Usage: contextproject.py [options]
(env > prj > prd > cmp)
Provide all names without prefix and suffix!

ConTeXt project management  (c) 2009-2019 by Henning Hraban Ramm, fiëé
visuëlle

Options:
  --version             show program's version number and exit
  -h, --help            show this help message and exit
  -m FILETYPE, --mode=FILETYPE
                        create which type of file?
  -c NAME, --component=NAME, --cmp=NAME
                        create component file
  -p NAME, --product=NAME, --prd=NAME
                        create or set product file
  -j NAME, --project=NAME, --prj=NAME
                        create or set project file
  -e NAME, --environment=NAME, --env=NAME
                        create or set environment file
  -i FILENAME, --template=FILENAME, --ini=FILENAME
                        use non-default initial template file
  -d DIRNAME, --directory=DIRNAME, --dir=DIRNAME
                        project path
  -C DIRNAME, --component_directory=DIRNAME, --cmpdir=DIRNAME
                        path for component files below project path

4) Create files in the order environment, project, product, component(s)
i.e.
# Create empty environment (it lacks the project name; I do this manually, copying from another project):
$ mkprj -e something
# Create the project file:
$ mkprj -e something -j something
# Create a product and insert it in project:
$ mkprj -j something -p first
# Create a component dir for product "first" and add a component:
$ mkprj -j something -p first -C first -c author

If there’s a component.ini, product.ini etc. it will get used as a template for that level.

There are a few bugs in the output, e.g. in the first call you can’t set the project name, and in the second it won’t create an environment if it’s missing. If you leave out the project when you create a component, the name gets an additional prefix. -m is mostly useless, and I never use -d.
I should fix that, but these are just minor annoyances.

Have fun!

Hraban