mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-05-10 16:48:31 +02:00
Documentation on DayOne integration
This commit is contained in:
parent
fd0d35e151
commit
370e703d11
2 changed files with 16 additions and 1 deletions
|
@ -5,6 +5,7 @@ Changelog
|
||||||
|
|
||||||
* [Fixed] A bug where jrnl would not go into compose mode
|
* [Fixed] A bug where jrnl would not go into compose mode
|
||||||
* [Improved] Each journal can have individual settings
|
* [Improved] Each journal can have individual settings
|
||||||
|
* [New] Integrates seamlessly with DayOne
|
||||||
|
|
||||||
### 0.3.2 (July 5, 2012)
|
### 0.3.2 (July 5, 2012)
|
||||||
|
|
||||||
|
|
16
README.md
16
README.md
|
@ -1,7 +1,9 @@
|
||||||
jrnl
|
jrnl
|
||||||
====
|
====
|
||||||
|
|
||||||
*jrnl* is a simple journal application for your command line. Journals are stored as human readable plain text files - you can put them into a Dropbox folder for instant syncinc and you can be assured that your journal will still be readable in 2050, when all your fancy iPad journal applications will long be forgotten.
|
*jrnl* is a simple journal application for your command line. Journals are stored as human readable plain text files - you can put them into a Dropbox folder for instant syncing and you can be assured that your journal will still be readable in 2050, when all your fancy iPad journal applications will long be forgotten.
|
||||||
|
|
||||||
|
*jrnl* also plays nice with the fabulous [DayOne](http://dayoneapp.com/) and can read and write directly from and to DayOne Journals.
|
||||||
|
|
||||||
Optionally, your journal can be encrypted using the [256-bit AES](http://en.wikipedia.org/wiki/Advanced_Encryption_Standard).
|
Optionally, your journal can be encrypted using the [256-bit AES](http://en.wikipedia.org/wiki/Advanced_Encryption_Standard).
|
||||||
|
|
||||||
|
@ -154,6 +156,18 @@ The configuration file is a simple JSON file with the following options.
|
||||||
>
|
>
|
||||||
> Or use the built-in prompt or an external editor to compose your entries.
|
> Or use the built-in prompt or an external editor to compose your entries.
|
||||||
|
|
||||||
|
### DayOne Integration
|
||||||
|
|
||||||
|
Using your DayOne journal instead of a flat text file is dead simple - instead of pointing to a text file, set the `"journal"` key in your `.jrnl_conf` to point to your DayOne journal. This is a folder ending with `.dayone`, and it's located at
|
||||||
|
|
||||||
|
* `~/Library/Application Support/Day One/` by default
|
||||||
|
* `~/Dropbox/Apps/Day One/` if you're syncing with Dropbox and
|
||||||
|
* `~/Library/Mobile Documents/5U8NS4GX82~com~dayoneapp~dayone/Documents/` if you're syncing with iCloud.
|
||||||
|
|
||||||
|
Instead of all entries being in a single file, each entry will live in a separate `plist` file. You can also star entries when you write them:
|
||||||
|
|
||||||
|
jrnl -star yesterday: Lunch with @Arthur
|
||||||
|
|
||||||
### Multiple journal files
|
### Multiple journal files
|
||||||
|
|
||||||
You can configure _jrnl_ to use with multiple journals (eg. `private` and `work`) by defining more journals in your `.jrnl_config`, for example:
|
You can configure _jrnl_ to use with multiple journals (eg. `private` and `work`) by defining more journals in your `.jrnl_config`, for example:
|
||||||
|
|
Loading…
Add table
Reference in a new issue