2 votes
 
If you do a Find and replace on a single file, you get options to "find", "replace", "find all" and "replace all". This means you can interactively review every replacement that is going to happen in a file.


However, if you do Find and replace across files, you only get "find" and "replace" (which are implicitly "find all" and "replace all"). This means you can't interactively review changes -- you have to make all the possible changes, then go back and review them.

It would be nice if the feature set of find and replace on a single file were also available over multiple files.

5 votes
 
If you have a large project (thousands of files) and/or a complex search regex, the UX for Find and Replace across files is a black hole. When you press the "replace" button, nothing seems to happen. So you press it again. And again. Then, a few minutes later, three dialogs pop up asking you if you want to replace N instances across M files. In the interim, there is no feedback that anything is being done.


There needs to be some sort of obvious visual feedback to indicate that search and replace is actually working.

0 votes
 
The OSX command line tool to open files/directories has a "-n" flag to open in a new window. However, using this flag will cause an existing open project window to be brought to the foreground.


To reproduce:

  1. Start ST2, open a project (say, P1)
  2. Minimize that project to the taskbar
  3. subn -n <P2 directory>


Window containing P1 is unminimized before the window for P2 is created. 
0 votes
 
Build #2036 added the current project name to the titlebar text under OSX. 


However, when the project has no open files, the titlebar reverts to the default "Sublime Text 2" title, omitting the project title. If you have multiple projects open, and each project window has no open files, it is not possible to differentiate minimized project windows.

1 vote
 
When adding a folder to a project, it is added in a "closed" state. The first action will almost always be to open that folder. The default expansion state of a newly added project folder should be to open the top level (i.e., if I add folder Foo, I should see all the files and subfolders of Foo without needing to manually expand the folder).
222 votes
 
The project tree (under OSX) can only be interacted with using the mouse. You can't give the project tree focus and navigate or open files using the keyboard.
 
COMPLETED
Jon Skinner
updated 1 year ago
This was added in 2139
119 votes
 
This would make it easier to open existing ST2 projects using the Finder.
 
COMPLETED
Jon Skinner
updated 1 year ago
This was added in 2165
15 votes
 
Ok, themes can be customized, but in terms of first impressions -- I found it difficult to see the tab outlines against the background, especially for non-selected tabs.
4 votes
 
The direction of the animation when a folder is expanded seems completely wrong to me. This is completely cosmetic, and it may be a personal taste thing, but 'slide in from top' or 'slide in from left' makes a lot more sense to me conceptually than 'slide in from right'. Expanding a directory is a "show you the things that were hidden under here" operation, not a "pull in content from over there" operation.
261 votes
 
Adding small, simple icons to project tree entries would make it easier to visually differentiate between folders and files. Making folder names bold would be an added bonus.

© 2009-2013 UserEcho, LLC. All rights reserved.
English (EN)