-
-
Notifications
You must be signed in to change notification settings - Fork 526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import/Export docs have no Import information #995
Comments
Yup, this is absolutely right. The page referenced is here: https://jrnl.sh/export/ Here's some notes for what needs to go into this section if anyone feels like sending over a PR:
|
Hey, I have some text where I lost the original file, I only got the default jrnl output (with dates not in brackets and multilines using pipe) - it doesn't seem to pick that up correctly? |
@xerus2000 The default output is the "pretty" format, and is really only meant for display purposes (it has color codes, etc, that make parsing impractical). We can probably do some shell magic to fix up the pretty format to make it importable. Can you paste an example entry with the date format you use here so I can help? |
I fixed it manually with vim ;) but since it's not much different, it shouldn't be hard to also allow importing that automatically? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I was just playing around with this today while checking out #1256, and found that |
I have given a try to this import feature, and it doesn't work for other journals, only the default one.
It always gets imported to the default journal and not the one I am pointing out, which should be personal in this case. |
It does work on non-default journals, but it doesn't work on directory journals. We have a bug filed for this in #999. |
Bug Report
Environment
Docs on jrnl.sh
Current Behavior
The docs header is import and export, however they don't show any example on import at all.
The text was updated successfully, but these errors were encountered: