all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "David (World) Reitter" <david.reitter@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Collaborative editing and persistently tracking changes
Date: Fri, 18 Sep 2009 11:56:45 -0700 (PDT)	[thread overview]
Message-ID: <7a3be365-3f19-4e9f-b302-c95722996a5d@s6g2000vbp.googlegroups.com> (raw)
In-Reply-To: slrnhag104.fam.joostkremers@j.kremers4.news.arnhem.chello.nl

On Sep 9, 3:38 pm, Joost Kremers <joostkrem...@yahoo.com> wrote:

> > I would need a combination of highlight-changes-mode and a way to save  
> > and load the change history of a buffer into a file, just like MS Word  
> > does it (with the new open docx format).
>
> highlight-changes-mode uses text properties to track changes. the elisp manual
> describes a theoretical method of saving text properties to a file:

Right, but even then you'd only save the properties and not the
semantics (unless track-changes uses only properties, which it may
well do).

Upon loading changes in, you should be able to accept / reject each
change.
And of course I'd like to see who made the change.

Basically, MS Word does a good job.  It also merges changes, something
even modern version control systems can't do well enough (since they
are line-oriented).

I think this is a huge omission on the part of GNU Emacs...


  reply	other threads:[~2009-09-18 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6324.1252515940.2239.help-gnu-emacs@gnu.org>
2009-09-09 19:38 ` Collaborative editing and persistently tracking changes Joost Kremers
2009-09-18 18:56   ` David (World) Reitter [this message]
2009-09-09 17:05 David Reitter
2009-09-09 17:57 ` Andreas Politz
2009-09-10 13:21 ` Andreas Röhler
2009-09-10 17:53   ` David Reitter

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7a3be365-3f19-4e9f-b302-c95722996a5d@s6g2000vbp.googlegroups.com \
    --to=david.reitter@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.