1.2.4: prevent overwriting of data when encrypting/decrypting

This adds checks to the encrypt and decrypt functions to prevent these
operations from overwriting newer files.

Case 1:

if file A.gpg is to be decrypted, but there's already a file A that is
newer than A.gpg, this indicates that the user has made some
modifications to A, and this should not be overwritten.

Case 2:

if A is to be encrypted but A.gpg exists and is newer than A, it
indicates that a newer version of A has been encrypted at some point.
Encrypting A now to create A.gpg would be a lossy conversion, since data
in the newer A.gpg may be lost.

1.2.3: anthology generation bugfix for encrypted journals

• I forgot that to generate an anthology, one needs all the journal entries---so they must be decrypted.

Full Changelog: 1.2.2...1.2.3

1.2.2: more encryption related improvements

Full Changelog: 1.2.1...1.2.2

1.2.1: bugfix release

Full Changelog: 1.2.0...1.2.1

1.2.0: Add encryption support

This release includes encryption support. It's quite a large hammer---it simply encrypts all files before committing. This also means that you must first decrypt files before editing them or viewing them. The script also does this.

Encryption support is optional. Most of us don't need to encrypt our research journals. However, I realised that some may want to do this. Some may even be using this for their personal journals, and there encryption may be more important.

Encryption is done using GPG, so you will need to generate a public/private key for yourself and keep it safe. (Search the web on how to do this, plenty of posts explain it very well).

Full Changelog: 1.0.0...1.2.0