Rendered at 03:58:33 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
cadeos 18 hours ago [-]
Great project. Any plans to let users point the CLI directly to an existing Obsidian vault for the markdown files?
dmsehuang 11 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".
Do you have any plans to make it open source in the future?
dmsehuang 8 hours ago [-]
The tldr is yes, but not sure about which part will be open source and which part will remain private, and when.
The API & web app components will definitely remain private, but the CLI tool itself can be open source.
If you run ‘paper config’ today, you will still see that you can configure the “sync url” - basically that allows you to sync your content to your own hosting provider.
I spent non-trivial thought on this topic during development, but then ended up with a conclusion that I should just make it private for now to speed up feature development. Otherwise I would need to think really hard on the interface & contract design.
j4cobgarby 20 hours ago [-]
Am I missing something? How is it not open source if I can view the source code at that link?
dmsehuang 11 hours ago [-]
haha, you got it!
I published the CLI tool with the sourcemap enabled prev-v1.0.0
That's why you can see the source code.
15 hours ago [-]
sankaran458 10 hours ago [-]
Wow! now i dont have to switch beetween onenote and terminal for my notes!
dmsehuang 9 hours ago [-]
Hey sankaran458, I am so glad to see this comment, and I hope this CLI tool can truly do its work to save people’s pain points. I hope this is not “yet another” useless tool that tries to simplify the workflow.
Give it a try and let me know your feedback if there’s any!
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!
You can use ‘paper config’ to specify the working directory, then all the journals will be saved to that path.
https://github.com/jrnl-org/jrnl
We are all ears!
Here's the link to the npm package: https://www.npmjs.com/package/@rewrlution/paper-cli
The API & web app components will definitely remain private, but the CLI tool itself can be open source.
If you run ‘paper config’ today, you will still see that you can configure the “sync url” - basically that allows you to sync your content to your own hosting provider.
I spent non-trivial thought on this topic during development, but then ended up with a conclusion that I should just make it private for now to speed up feature development. Otherwise I would need to think really hard on the interface & contract design.
I published the CLI tool with the sourcemap enabled prev-v1.0.0
That's why you can see the source code.
Give it a try and let me know your feedback if there’s any!
Hope you will enjoy it!