From mboxrd@z Thu Jan  1 00:00:00 1970
From: Samuel Wales <samologist@gmail.com>
Subject: if we operate on a subtree, perhaps we could adjust levels
Date: Wed, 26 Mar 2014 20:44:24 -0700
Message-ID: <CAJcAo8u6AB2QCkv0RBr1ghJah9KqfLbx72Z48G7xjMTdrVMpCw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46689)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <samologist@gmail.com>) id 1WT1Ex-0001x1-61
	for emacs-orgmode@gnu.org; Wed, 26 Mar 2014 23:44:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <samologist@gmail.com>) id 1WT1Ev-00043O-QY
	for emacs-orgmode@gnu.org; Wed, 26 Mar 2014 23:44:27 -0400
Received: from mail-qa0-x236.google.com ([2607:f8b0:400d:c00::236]:38686)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <samologist@gmail.com>) id 1WT1Ev-000438-Lr
	for emacs-orgmode@gnu.org; Wed, 26 Mar 2014 23:44:25 -0400
Received: by mail-qa0-f54.google.com with SMTP id w8so3203746qac.41
	for <emacs-orgmode@gnu.org>; Wed, 26 Mar 2014 20:44:25 -0700 (PDT)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

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.

comments?

samuel