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
2013-02-19 10:02:09 -07:00
2012-09-30 15:00:45 -07:00
2013-03-05 14:32:51 -08:00
2012-10-18 16:00:14 -07:00
2013-03-24 19:54:14 +08:00
2013-02-05 12:03:56 -08:00
2013-03-29 14:13:46 -07:00
2013-02-25 16:11:13 -08:00
2013-02-11 09:31:16 -08:00
2013-04-02 08:28:30 -07:00
2013-03-28 10:09:29 -04:00
💄
2013-03-04 22:07:22 -08:00

Atom — Futuristic Text Editing

atom

Check out our documentation on the docs tab.

Building from source

Requirements

  • Mountain Lion
  • The Setup™ or Boxen
  • Xcode (available in the App Store)

Installation

  1. gh-setup atom

  2. cd ~/github/atom && rake install

Description
No description provided
Readme 447 MiB
Languages
JavaScript 88.3%
Less 8.7%
CoffeeScript 2.8%
Shell 0.1%