- change header level when inserting trees
- start making some unit tests
- allow passing of fname and just calling
sys.POpen([args])
- how to grab stdout? need internet
pandoc -s test_data/test.md -t json -f gfm | python main.py -p -a | pandoc -f json -t gfm -s
pandoc -s test_data/test_stub_todo_item.md -t json -f gfm | python main.py --fname test_data/test_todo.md -m -i title.todo -p
pandoc -s test_data/test.md -t json -f gfm | python main.py -p -t
cat test_data/test_stub_todo_item.md | python main.py --fname test_data/test_todo.md -m -i title.todo -p
details:
-i title.todo
is the destination identifier to inject new markdown--fname test_data/test_todo.md
is the path to the existing / destination note to modify (an empty todo list in this case)-m
specifies output format as markdown
Before:
---
title: test
---
# Title
description
## TODO
foobar
Input:
# Lightgbm dask
allow multi node training
After:
---
title: test
---
# Title
description
## TODO
foobar
### Lightgbm dask
allow multi node training
note - use this to pipe
pandoc -s test_data/test_stub_todo_item.md -t json -f gfm | python main.py --fname test_data/test_todo.md -m -i title.todo -p
- gitlab style markdown, with text leading bulleted list
- should the text before be part the title of the list?
cat new_markdown.md | python main.py -f dest_fname.md -i schema_identifier -s
-s
for stdin / pipe for NEW content-f <fname>
for existing file
currently using -i <term>
arg you can use a term like title.todo
to access the second level
Hopefully something exists, if not...
Ideas:
foo.*.bar
means any number of levels to get from foo to barHtodo+
means any chars after header starting with todo- use
H
orL
for header or list
- Finish bulleted lists? Or Finish a basic useable tool