Oh wow, that's a very popular one!
I did not know that before.
I am gonna give it a try and compare these tools.
Thanks for the info!
cadeos 8 hours ago [-]
Great project. Any plans to let users point the CLI directly to an existing Obsidian vault for the markdown files?
dmsehuang 2 hours ago [-]
Hey cadeos,
Yes, `paper import` handles this. just point it at the folder your daily notes live in:
```
paper import <your-path-to-journals> --dry-run
```
Comment:
1. I personally keep all my Obsidian journals in a journal folder, so that's easy for me to do
2. highly recommend you to use the `--dry-run` option if you are not sure what files will be imported
Two things worth knowing.
1. It reads every `.md` and `.txt` inside that folder
2. file with no date in its name is still imported, and last modified date will become its filename in "paper".
https://github.com/jrnl-org/jrnl
Yes, `paper import` handles this. just point it at the folder your daily notes live in:
``` paper import <your-path-to-journals> --dry-run ```
Comment: 1. I personally keep all my Obsidian journals in a journal folder, so that's easy for me to do 2. highly recommend you to use the `--dry-run` option if you are not sure what files will be imported
Two things worth knowing. 1. It reads every `.md` and `.txt` inside that folder 2. file with no date in its name is still imported, and last modified date will become its filename in "paper".
You can read more about its logic in the "Importing existing notes" section on the npm page: https://www.npmjs.com/package/@rewrlution/paper-cli
Hope it works and hope you will enjoy it!
We are all ears!
Here's the link to the npm package: https://www.npmjs.com/package/@rewrlution/paper-cli
I published the CLI tool with the sourcemap enabled prev-v1.0.0
That's why you can see the source code.