Super+N open new window and Super+T new tab
In order to stick with default OSbehavior and also improve the usability of creating new files I suggest assigning:
Super+N -> Open new window (like it does on textmate, finder, etc..)
Super+T -> Go to file/New file (Create new tab showing the current panel with a couple of teaks)
To open a file, it would work as usually:
Create new tab, type the name of the file, press return.
Create new tab and press esc to dismiss the overlay.
As an enhanced behavior, the user could instead of pressing esc, type the name of the newfile+folder (somefolder/example.css) and press enter. If no folder is specified (example.css), the file would be created next to the previously displayed file. This would spare the user of having to save the file manually in order to have syntax features or having to deal with the save file dialog.
All this could be complemented by a Create New File entry on the show_files overlay (the one which appears when you press super+t)
Build command, Build window crash
Hello I am experiencing a problem with most recent version of sublime 2. My build system (nmake) used to work just fine with previous version, but now it sometimes works and sometimes does not. When it does not work, it opens an empty dockedbuild window at the bottom, but does not show any build steps ~ text, errors etc. I know build is going on, just text is not shown. Also, when text is not shown and I click in a window with my mouse, sublime crashes. When build is going and text is shown and I click, everything is fine.
Thanks.
find.use_selected_text in ST2
Automatically highlight references to symbol under cursor
leaving full screen crashes
File dirty marker doesn't update on save when buffer has multiple views
Build 2032 on Mac OS X.
* Choose vertical two pane layout.
* Open a file in group 1.
* Switch to group 2. Open the same file there using Goto Anything. The same buffer now appears in two tabs, one in each group.
* Make some changes to the buffer. A "file dirty" marker asterisk appears in both tabs.
* Save the buffer. The asterisk disappears in the tab that was active when the save command was issued, but it remains in the other tab.
Typing "e" does not advance to next word in command mode
access to all shortcuts via api
access to all shortcuts via api. This can be used to create suggestions for shortcuts as we type. or can be used to create plugin
Vintage text objects do not work with <> brackets
Highlight multiple cursor(s) out-of-view
When you have multiple cursors/selections which are not in the current view (i.e. you scrolled away from them) it might easily happen that you type away without noticing, that you actually modify multiple places at once. It would be nice to have a clear warning when an additional cursor is not currently visible. For example by showing one or two of these cursors (in their respective scope; i.e. the line they are in) at the top or bottom (depending on where they are in relation to your current view) of the editing window.
Real-time debuging
Sublime text should be able to spot errors in real-time like Java does and offer a few solutions and why it is an error for all major languages.
Create an option to make bottom dialogs span code area width only (and not span project view)
- Easier to switch/focus attention (especially for people with bad eyesight).
- More height for the project view.
"File open" dialog doesn't show all files
Open opening "Find", use currently selected text as "Find what"
I'd prefer to click a "Reset" button in the "Find dialog" in cases where the text for which i'm looking isn't highlighted, than focus the document, copy, paste to "Find What" before I can search
Improved Locked Document Editing
Problems arise from the following set of steps:
- Open a locked document
- Make edits to the document
- Save -> Get Error about document being locked
The issue is getting the file unlocked painlessly so the user can save the edits made up to this point. I realize there are plugins that exist to auto-checkout files in source control, but this is an orthogonal issue. For example, if the checkout/unlock operation fails, the user is stranded with edits that cannot be saved.
Possible resolutions include:
- Let the user drag the document icon (in OSX) in the window bar to another application to copy the file path. As of step 2 above it is greyed out and cannot be dragged without undoing the edits.
- Prevent the user from making edits in step 2 until the file has been unlocked. This is how other editors like BBEdit and Xcode behave. This would also be the point at which version control plugins would want to attempt to check out the file.
- The ability to overwrite the locked file during step 3. Some kind of dialog to either cancel the edit or unlock the document. This would be a fallback option in the event a plugin failed to checkout/unlock the document, so the user could still save the edits (they would, of course, be on the hook for checking out the file manually.)
- The ability to get the full path of the frontmost document quickly copied to the clipboard so it can be pasted in another application to checkout/unlock the locked file, making step 3 succeed.
Customer support service by UserEcho