Hi Achim,
Achim Gratz writes:
> FWIW, I prefer the other solution since it is more general. Again, the
> content from the decryption process can be treated like an include
> (except for display rather than during export) or rather an "inline
> file", which might be worth having independently of
Bastien writes:
>> 2. Demote the whole subtree to toplevel before encryption and promote
>> into the correct level on decryption, (much in the same way that
>> includes are handled).
>
> By "correct level on decryption" you mean toplevel? This would really
> circumvent the problem.
Not sure what
Hi Samuel,
Samuel Wales writes:
> org-yank-adjusted-subtrees?
I think this would work if the yank contains only one subtree,
which will not be the case most of the times.
Still worth exploring, I'll keep this in my todo list,
--
Bastien
org-yank-adjusted-subtrees?
On 7/28/14, Bastien wrote:
> Hi Samuel and Achim,
>
> Achim Gratz writes:
>
>> Samuel Wales writes:
>>> you will notice that the decrypted subtree is actually at a higher
>>> level than its parent. this is a violation of org structure.
>>>
>>> in consequence, it can
Hi Samuel and Achim,
Achim Gratz writes:
> Samuel Wales writes:
>> you will notice that the decrypted subtree is actually at a higher
>> level than its parent. this is a violation of org structure.
>>
>> in consequence, it can silently swallow the entire rest of the file.
>>
>> this is not desi
Samuel Wales writes:
> you will notice that the decrypted subtree is actually at a higher
> level than its parent. this is a violation of org structure.
>
> in consequence, it can silently swallow the entire rest of the file.
>
> this is not desired.
>
> is there a way to fix it?
There's two ways
hi bastien,
On 4/17/14, Bastien wrote:
> Then I didn't understand what you suggested. Can you restate
> it again? Thanks,
will try.
On 3/26/14, Samuel Wales wrote:
> in maint, if you encrypt with org-crypt on an entry with children, then
> demote, then decrypt, the subtree levels do not matc
Samuel Wales writes:
> On 4/11/14, Bastien wrote:
>> That's expected. Users don't think Org is clever enough to
>> decrypt-demote-subtrees-then-re-encrypt on the fly.
>
> i was not suggesting this.
Then I didn't understand what you suggested. Can you restate
it again? Thanks,
--
Bastien
On 4/11/14, Bastien wrote:
> That's expected. Users don't think Org is clever enough to
> decrypt-demote-subtrees-then-re-encrypt on the fly.
i was not suggesting this.
Hi Samnuel,
Samuel Wales writes:
> in maint, if you encrypt with org-crypt on an entry with children, then
> demote, then decrypt, the subtree levels do not match up.
> for example, the children can end up as uncle/aunt nodes.
That's expected. Users don't think Org is clever enough to
decrypt-
in maint, if you encrypt with org-crypt on an entry with children, then
demote, then decrypt, the subtree levels do not match up.
for example, the children can end up as uncle/aunt nodes.
maybe something like these are possibilities:
1) optionally adjust subtree levels to match the location
11 matches
Mail list logo
