From: Samuel Wales <email@example.com>
Subject: if we operate on a subtree, perhaps we could adjust levels
Date: Wed, 26 Mar 2014 20:44:24 -0700 [thread overview]
Message-ID: <CAJcAo8u6AB2QCkv0RBr1ghJah9KqfLbx72Z48G7xjMTdrVMpCw@mail.gmail.com> (raw)
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
of the header at time of decryption. this is similar
to how org-yank behaves. it would have to re-encrypt
if you encrypt, demote, decrypt, encrypt.
2) optionally put the subtree in an org source block so
that it is no longer an active subtree (can't search
headlines in agenda, they are not where they belong, can't export
as part of parent, have to edit with c-c ')
3) restrict the function to only operate on body text
(can't do subtrees).
4) status quo (allow outline corruption at user's risk).
5) a combination.
maybe there are more possibilities.
next reply other threads:[~2014-03-27 3:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 3:44 Samuel Wales [this message]
2014-04-11 9:07 ` if we operate on a subtree, perhaps we could adjust levels Bastien
2014-04-17 9:43 ` Samuel Wales
2014-04-17 10:12 ` Bastien
2014-06-09 4:54 ` Samuel Wales
2014-06-09 5:54 ` Achim Gratz
2014-07-28 15:05 ` Bastien
2014-07-28 19:08 ` Samuel Wales
2014-07-29 14:30 ` Bastien
2014-07-29 16:03 ` Achim Gratz
2014-07-29 21:32 ` Bastien
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).