Daniel Clemente <n142...@gmail.com> writes: > I found minor but unrelated issues, e.g. if you have an empty section like > this: > > ************* abc2 :crypt: > ************* def > > … if you rename the abc2 header, e.g. to abc, it will ask the > encryption password again, even when the contents (an empty header) > didn't change. > > Another minor and weird bug: inline blocks. The part about showing the > unencrypted contents while keeping the disk contents encrypted doesn't > seem to work with encrypted inline blocks: they're saved encrypted, > but they're displayed encrypted. In fact they can't be displayed > unencrypted even if you call org-decrypt-contents. Maybe inline > encrypted blocks aren't supported. > To test this: > ***** section > ********************** this is an inline block > :crypt: > Content. > > If you want you can split this to other threads or just ignore these > edge cases for now.
There is no such thing as "inline block" in Org syntax. The current behavior of org-crypt is because it mishandles inlinetasks in specific way. I can add support for proper inlinetasks delimited by END line, but not for what you call "blocks" - that one is actually a bug when org-crypt encrypts everything spanning between one-line inlinetask down to the next heading. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
