jskinner

Sublime Merge understands submodules, but we don't expose a UI for managing them yet. This is right near the top of our priority list though.

Custom themes are supported (although not in the evaluation version), however Sublime Text themes will need to be adapted to work in Sublime Merge: there's quite a bit more to the UI here, and the controls to target are quite different. Likewise with color schemes, as long as they define the new diff scopes, color schemes can be used, however none of the existing ones will yet. Syntax definitions, on the other hand, don't need any changes, and any you have installed for Sublime Text will be picked up automatically by Sublime Merge.

Plugin support is on the roadmap, and tabs will be added if that's what the user feedback asks for.

There's no dev channel yet, but we'll be adding one soon.

Thanks for the kind words! There's some basic integration now, and we'll be adding more in the future.

Right now, Sublime Merge will pickup installed Sublime Text packages (e.g., for syntax highlighting), and will also find Sublime Text when you choose Open in Editor from within Merge (this can be customised to something else though, of course).

Sublime Merge is a Git client, and I'd list the main advantages over the alternatives as performance, and UI polish in general.

For example, when you stage a file in Sublime Merge, we internally predict the resulting change to the repository, so the changes are reflected in the UI immediately, while the operation is actually happening asynchronously. In contrast, other Git clients can take seconds before being able to stage a second file.

Hi HN - Jon Skinner here, I made Sublime Text and Sublime Merge, alongside the rest of the Sublime HQ programming team - Will, Dylan and Benjamin. Let me know if you have any questions!

Edit: there's also the announcement blog post, at https://www.sublimetext.com/blog/articles/sublime-merge

As far as I'm aware it is. If you know of an implementation done before 2008 I'd love to know about it.

No, it wasn't. I believe TextMate had a feature where you could edit multiple lines at once, but it was part of a column selection mode, it certainly wasn't free form multiple selections.

Multiple Selections were one of the earliest core features built for Sublime Text, and weren't inspired from other software. I don't think TextMate existed when I implemented this.

This is correct, Sublime Text hasn't officially hit "3.0", but the current builds of Sublime Text 3 have been the reccomended versions to use for quite a while now, hence why the front page points to 3 rather than 2.

When 3.0 is out, there will be a blog post about it.

Sublime Text 1 used OpenGL (1.1 only, hence no GLEW) and Direct3D, while 2 and 3 are mostly software only.

While Sublime Text 2 and 3 do use Skia, only a tiny fraction of its functionality is actually used, just for rasterizing lines and blitting images. Font rendering is done by using the underlying platform APIs to do the glyph rasterisation.

http://www.sublimetext.com/forum is a better place for this, but as a stopgap you can disable file indexing via the index_files setting. You can also find out more about what indexing is taking place by entering sublime.log_indexing(True) in Sublime Text's console.

Two. Next hire will also be an engineer.

Since February this year, Sublime HQ has been a 3 person company.

You can find out the (highlighted) differences between the in-memory buffer and the on disk version one via "Show Unsaved Changes" on the context menu.

I touched on this in another reply: http://news.ycombinator.com/item?id=4532495, with the short answer being unusably high memory usage.

From memory PNG doesn't compress as well as you may intuitively think in this scenario, with the resulting files being around 3X the size.

I initially tried something along these lines. However even with small animations, you end up with files that while small on disk, consume a large amount of memory after they've been decompressed, resulting in browsers refusing to load them.

Indeed!

Next thing I'll find out that you actually can get a JavaScript callback when a GIF has finished animating.

I didn't, no. I'd be interested in seeing the result, given that video codecs aren't optimised for lossless encoding.

In truth, I didn't want to get into the quagmire of real video formats, and producing something that works everywhere.

Based on my hazy understanding of the animated GIF file format, I believe that what I ended up with is very similar to animated GIFs, from a high level at least (i.e., a collection of frames, each of which containing multiple rectangles where the frame differs from the previous one). I have no idea why the animated gif encoders I tried did such a poor job size wise, it looked as if none of them even tried to find the minimal set of changes from one frame to another. I didn't spend too long looking, as 8-bit color was always going to be a show stopper.

I got inspired to finally write this up after seeing the discussion today about Apple's use of a similar technique.

Code is available at https://github.com/sublimehq/anim_encoder, although you'll undoubtedly need to do some wrangling to use it for your own projects.

By default, the appropriate syntax highlighting will be set on the file the first time it gets saved.

If you press ctrl+d one time too many, you can use Soft Undo (ctrl+u / command+u) to step backwards. Soft Undo undoes selection commands as well as modifying commands, as opposed to regular undo, which undoes modifying commands only.

It sounds like Paste and Indent is what you're after: Command+Shift+V, or some users prefer to just bind this to Command+V, a la TextMate.

While I did try to be compatible with TextMate key bindings where possible, I believe only a handful of the key bindings mentioned in the article are actually common between the two.

A few more handy ones:

Line Manipulation:

  Select Line (press again to select subsequent lines): Command+L / Ctrl+L
  Split multi-line selection into multiple selections, one per line:
    Command+Shift+L / Ctrl+Shift+L
  Delete to BOL: Command+Delete / Ctrl+Shift+Backspace
  Delete to EOL: Control+K / Ctrl+K,Ctrl+K or Ctrl+Shift+Delete
  Delete Line: Control+Shift+K / Ctrl+Shift+K
  Insert Newline After: Command+Return / Ctrl+Enter
  Insert Newline Before: Command+Shift+Return / Ctrl+Shift+Enter

Multiple Selections:

  Add next occurrence of current word to selection: Command+D / Ctrl+D
  Select all occurrences of current word: Control+Command+G / Alt+F3
  Undo through selection changes: Command+U / Ctrl+U

These issues are best addressed on the Sublime Text forum, but for the first one at least, .py files in a subdirectory under a package won't be loaded as plugins, so you can place libraries there (this is done for Packages/Default/send2trash, for example).

Some of these issues arise because SublimeCodeIntel triggers the auto-complete prompt automatically, which it wasn't designed for. I'm planning to rework the auto-complete system at some point to make it more appropriate for this scenario.

Vintage Mode is implemented entirely via key bindings and a few plugins (which come as commented python source). Everything is customisable, there are some details at http://www.sublimetext.com/docs/2/vintage.html

Vintage Mode supports cit, and ci' directly. For normal editing, there are equivalents like Expand Selection to Tag (Command+Shift+A / Ctrl+Shift+A)

There are a few ways to add folders:

- Drag a folder onto the window from Finder/Explorer

- File/Open Folder to open a folder in a new window

- Project/Add Folder to Project to add an additional folder to the current window

- Via the command line

btw, you can use "File/Clone File" menu item to get a new view into the current file.