Nathan Sobo 3150785db2 Ensure we never deserialize two instances of the same buffer ...

We might have two edit sessions pointing to the same buffer, for
example if we have a split pane… So when we deserialize a buffer, we
always need to check that we don't already have an instance of that
buffer on the project. If we do, then we've already deserialized it
once so we don't need to worry about the saved text.

We still have a problem when deserializing previously unsaved buffers,
because we can't use the path to identify them.

2013-04-02 15:45:16 -06:00

..

app

Ensure we never deserialize two instances of the same buffer

2013-04-02 15:45:16 -06:00

fixtures

Remove unused test.tmbundle

2013-03-26 17:35:44 -06:00

stdlib

Rename singleTrailingNewline to ensureSingleTrailingNewline

2013-04-01 10:44:34 -07:00

atom-reporter.coffee

Use node's require instead of internal require

2013-03-12 10:38:05 -07:00

jasmine-focused.coffee

Move jasmine-focused to spec folder

2013-03-20 18:36:55 -07:00

jasmine-helper.coffee

Move jasmine-helper from vendor/ to spec/

2013-03-20 18:38:19 -07:00

spec-bootstrap.coffee

Log error when no stack exists

2013-04-02 14:40:30 -07:00

spec-helper.coffee

Throw error instead of string

2013-04-02 14:40:55 -07:00

spec-suite.coffee

Measure spec suite require time

2013-03-15 09:09:56 -06:00

time-reporter.coffee

Use node's require instead of internal require

2013-03-12 10:38:05 -07:00