From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Porter Subject: Re: New feature? Remove duplicate subheadings, preserving order Date: Wed, 03 Jan 2018 03:39:52 -0600 Message-ID: <871sj7uvpz.fsf@alphapapa.net> References: <87a7xxx5c5.fsf@nicolasgoaziou.fr> <87tvw5cu5t.fsf@nicolasgoaziou.fr> <87mv1wvr70.fsf@alphapapa.net> <87r2r8w73n.fsf@alphaville.usersys.redhat.com> <87608jv18i.fsf@alphapapa.net> <87373n2w3v.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35082) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWfWr-0008Io-Hr for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 04:40:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eWfWo-00086G-Es for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 04:40:09 -0500 Received: from [195.159.176.226] (port=43985 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eWfWo-00085Y-7Y for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 04:40:06 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1eWfUm-0003nU-SQ for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 10:38:00 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Ihor Radchenko writes: > Is there any possible way to prevent it more reliably? > > I am aware of org-catch-invisible-edits, but this is obviously not > enough. Does it make sense to generate some kind of subtree based diff > after each change, so that user can review all recent changes in org > files? That's a good question. If you want to be max-paranoid, I guess you should put all your Org files in git, and review and commit all changes with magit. For certain things that might make sense (e.g. I do that with readme files in published projects), but for my personal Org files, that would feel like a burden to me. I do store my personal Org files in git, but I don't review the changes manually. I commit the changes automatically with a cron job and when my "emacs-raise-or-run" script raises or minimizes the Emacs window. If I ever need to review the changes, I can use magit or gitk. If you add this to your .git/config file in a git repo of Org files, it uses Org heading lines as diff headers, which helps when reviewing changes: [diff "org"] xfuncname = "^\\*+ +.*$"