AW t-online.de> writes:
> Dear John,
>
> thank you. I simply changed "read_only" to "crypt" in the functions you
> developed. This functions prevent a change of encrypted text, which I
think is
> really an improvment.
This is awesome. But I have a follow-up questions.
This function marks m
Am Montag, 24. August 2015, 20:42:01 schrieb AW:
> Am Sonntag, 23. August 2015, 19:54:51 schrieb John Kitchin:
> > I am not sure if you put the comment on this post:
> > http://kitchingroup.cheme.cmu.edu/blog/2014/09/13/Make-some-org-sections-r
> > ea d-only/
> >
> > but it is possible to setup a
Am Sonntag, 23. August 2015, 19:54:51 schrieb John Kitchin:
> I am not sure if you put the comment on this post:
> http://kitchingroup.cheme.cmu.edu/blog/2014/09/13/Make-some-org-sections-rea
> d-only/
>
> but it is possible to setup a hook that makes headings read-only. You
> could do that for he
I am not sure if you put the comment on this post:
http://kitchingroup.cheme.cmu.edu/blog/2014/09/13/Make-some-org-sections-read-only/
but it is possible to setup a hook that makes headings read-only. You
could do that for headings tagged crypt, for example.
AW writes:
> I'm using org-crypt. All
If it helps, though aside from the question, all GPG lines (except the last 2)
are 64 chars(if memory serves). A little scripting and decryption should be
plausible (possible in reasonable time), especially if chars were only added
and not deleted/changed.
On August 23, 2015 2:31:26 PM PDT, AW
I'm using org-crypt. All text below a heading with the tag :crypt: becomes
encrypted with saving the file and looks like this:
-BEGIN PGP MESSAGE-
Version: GnuPG v2
hQEOAxn9DjwjX2oYEAQAgLl/58dss1VVgmRb1rGIaNV2I5P+smcDjhWa5/arTMPE
9wjxHUpU/HSflCwnV5609H3J9ZSVubCpaUbV3Da0jnDUJuljFbSqapRym1
