crash-proof emacs use

[Samuel Wales]

suppose you want to move something from one place to another.  in org,
you can often use org-refile.  that is more or less an atomic
operation.  but suppose that for whatever reason you cannot do that,
so you use traditional emacs.

which is to say you kill and then yank.  this is not stateless.  if
you have short-term memory issues [a big one] or computer issues or
get interrupted or whatever, there are possible failure states where
you lose data.

this can be detected with git, rsnapshot, zfs, auto-save files, backup
files, diff, and the like, but i was thinking, i wonder if anybody has
thought about this problem, especially the stm part, and implemented
some kind of crash-proof moving.

this is open-ended, but would mean something like, you kill some text
with a "about to move" command so that killing is not conflated with
moving, and it gets marked as "move operation started".  then you go
to the location to yank to, and you [if your stm is operating ok] yank
in the new place with a message that this is supposed to be
crash-proof.  as part of that yanking, the old text gets deleted.
this is just a silly example.

there are many flaws in that design, but it is an examlpe of something
i was wondering if anybody has thought about.  it is an issue i deal
with frequently.  detecting after the fact is ok but there are edge
cases where it is insufficient.

so it is an open-ended q about whether anybody has implemented
crash-proof moving, or follows some kind of discipline /all the time/,
or some kind of non-theoretical sw for this, and it doesn't require
detecting after the fact.

idk if this will lead to anything but perhaps there is something out
there that works really well for those who have stm issues.

-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com