Undo per user

[seanonthenet]

Am I missing a setting / feature to enable undo per user and not the collective changes?

Apologies if this is already a logged issue.

[shipstar]

+1 Not sure how technically difficult this is, but it's certainly surprising and sometimes confusing.

[sebinievas]

Wow this sucks! I almost purchased this for our whole team as a replacement to Coda until I was unable to undo per user. It scared the living hell out of me! Please let me know if this gets fixed and I will purchase right away.

[shipstar]

@snievas Just to be clear -- this wasn't a deal breaker for us. Most of the time, there were only two of us collaborating on the same file at the same time, usually taking turns typing. In that use case, the undo per user wasn't a major issue.

The only place where we ran into trouble was if two of us were both saying, "Here's how I think this might work" in different parts of the same file, then comparing our solutions. Undoing would sometimes result in strange behavior, although we always noticed right away.

There are certainly some rough edges with Floobits, but it's by far the best solution I've used for remote collaboration that allows each developer to use their own machine/editor/environment.

[micalexander]

+1 Sorry @shipstar I have to agree with @snievas. I currently work in an environment where we have team members that are in another state so shared collaboration is a must. It is absolutely unintuitive for another team member to be able to undo your changes made to a file.

With an "Undo per user" feature implemented, it would allow for two people to work on the same file simultaneously with out interfering with the other persons work allowing for a more productive environment.

This feature it the one thing that keeps our company ball and chained to Coda.

Come on Floobits, please set us free!

[ggreer]

Sorry, but this is really, really hard to do. I don't know of any editor with a plugin API that lets you say, "Make this change to the buffer, but don't put it in the undo stack."

We'd basically have to override undo in each editor, then re-implement undo behavior from scratch. That includes all kinds of little things you typically don't notice, like undoing a word at a time instead of each letter typed. (TextMate 1.5 was notorious for getting this behavior incorrect.)

We use Floobits to develop Floobits, so we run into this issue from time to time. It's mildly annoying, but there's not much we can do about it. Sorry. :(

[theFroh]

How about an option to require two undos, or notify if you're undoing an action that wasn't your own?