From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ihor Radchenko Subject: Re: New feature? Remove duplicate subheadings, preserving order Date: Wed, 03 Jan 2018 16:19:00 +0800 Message-ID: <87373n2w3v.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me> References: <87a7xxx5c5.fsf@nicolasgoaziou.fr> <87tvw5cu5t.fsf@nicolasgoaziou.fr> <87mv1wvr70.fsf@alphapapa.net> <87r2r8w73n.fsf@alphaville.usersys.redhat.com> <87608jv18i.fsf@alphapapa.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59073) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eWeHL-00046O-U1 for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 03:20:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eWeHH-0001XD-A0 for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 03:20:03 -0500 Received: from mail-io0-x234.google.com ([2607:f8b0:4001:c06::234]:39042) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eWeHH-0001Wz-4b for emacs-orgmode@gnu.org; Wed, 03 Jan 2018 03:19:59 -0500 Received: by mail-io0-x234.google.com with SMTP id g70so1327965ioj.6 for ; Wed, 03 Jan 2018 00:19:58 -0800 (PST) In-Reply-To: <87608jv18i.fsf@alphapapa.net> 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: Adam Porter , emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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? Ihor Adam Porter writes: > Nick Dokos writes: > >> There be dragons. >> >> The problem is that some things happen invisibly and far away from >> where you are, so you don't know about it and you don't find out for a >> couple of weeks. Undo and automatic backups are useless in that case. >> >> That *has* happened: there have been multiple postings in the ML about >> such problems. Whenever it has happened, the devs have always modified >> org to make it safer: that is the prudent thing to do and the correct >> course of action IMO. >> >> Hell hath no fury like an orgmode user who lost part of his/her >> precious org file because of an errant keystroke a month ago and was >> not aware of the loss until it was too late. > > Indeed. Maybe I'm just paranoid, but having worked with Org code a bit, > I still wonder sometimes if I have ever accidentally wiped out a subtree > without noticing. Would I ever notice that it's missing? Even if it's > stored in git or a backup, how can I restore something that I don't know > needs restoring? > > Some of this is simply the nature of computers, I think--a keystroke > here, a blink of the eye there, and poof, the data is gone. If the > point is in one buffer when my fingers press C-c C-x C-w, but my eyes > are in another buffer, does the subtree still get deleted? :) > > And despite how great Emacs and Org are, this is one area in which their > power may make them more vulnerable to such issues. Their use of global > state and special variables also makes unintended consequences easier to > achieve. > > This is why I think we should always be very careful. Org is nothing if > we can't trust it to keep our data safe! :) > > =2D-=20 Ihor Radchenko, PhD Student Singapore University of Technology and Design, 8 Somapah Road Singapore 487372 Email: yantar92@gmail.com, ihor_radchenko@mymail.sutd.edu.sg Tel: +6584017977 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEERZAHPFbUe3JemmzmZHB2Kn2hHYsFAlpMkfQACgkQZHB2Kn2h HYsmrQgAixCAvYNOysS/mVMu/3HqTcFFEqnmtepmh+OUmUsAiWf4ags4FtDeWCYY yrfYxjayBjEjt/Pf2e1hjYltluTXotqCfNUWyp+OqvxYRscInGSDSelsy5hopKSD fT3yaVyKjQ6bgClLrMAXhRz7BGxVzsA19uher5e4A4+YQr/x8SuPnVcNnkjHONkI 5FNs1yiVepdXr2Tkmaw1SrBnk1Puy5IybUdKd3IctgSDL4xfrC56mN5CuvGVAMdk LF7silnZXnYl/0kAMLph8Kp1GKdJf4Uh6wirXQVvLTOFcuk/FBBFznt6hwmvwRnY g7sPa1J14Y1LYPEtYGs70pQDKNMJuQ== =6aHc -----END PGP SIGNATURE----- --=-=-=--