Sublime Text 2 is a text editor for OS X, Linux and Windows, currently in beta.

  1. Forum: General
+3

Code folding doesn't work properly

Henrique Boaventura vor 13 Jahren • aktualisiert von Felipe Prenholato vor 13 Jahren • 1
Code folding on PHP classes doesn't work properly. When the hotkey to fold is hit, it folds the entirely class, even if you're inside a method or a condition/lood block.
+3

system level dialogs should support keyboard "Don't save" "d" and "Cancel" "c"

kjayne vor 13 Jahren • 0


keyboard d or c should sould to trigger the respective buttons
+3

Open a directory, as it was a project.

Zic vor 13 Jahren • 0

 Open a directory, as it was a project. Listing files and dirs in sidebar. Without saving any project file, if the user haven't made changes that need to be saved in a project settings file.

+3

Remember tab positions when switching viewports

Abhishek Rastogi vor 13 Jahren • 0
When switching from a split view to a single view, or a quad view, have the tabs remember which group they belonged to... When you have 3 tabs on the right, and 4 on the left, and you need the screen space for a second, you switch to a single pane mode, they all get grouped together... When you switch back, the tabs all stay clumped in one group... :-(
+3

Treat panels as tabs

Nilium vor 12 Jahren • 0

So, this is an "it'd be nice" request (meaning it's possibly unreasonable or poorly thought out): it'd be nice to treat all panels — output panels, find results panels, the console, etc. as regular tabs. That way they can be moved around, don't take up a whole enormous chunk of the bottom of the window all the time, and otherwise behave as expected rather than as these strange, unique things. They could be read-only tabs for all it matters, the point is just to make sure they operate on the same level as regular tabs.

One issue here would be where to put a new output panel, then, in which case a layout option might need to be added to say "this is the spot where new panels go." So, for instance, if you had the following (note: the new property is "panel_location"):

{
  "caption": "Layout: 1 by 2",
  "command": "set_layout",
  "args":
  {
    "cols": [0.0, 0.5, 1.0],
    "rows": [0.0, 0.5, 1.0],
    "cells": [
      [0, 0, 1, 2],
      [1, 0, 2, 1],
      [1, 1, 2, 2]
    ],
    "panel_location": [ 1, 0 ]
  }
}

Where "panel_location" would specify the default location of new panels using [column, row] (or [x, y]), which refers to the closest column and row that the layout can match (or just specifying a point in percentages [based on the cols/rows properties] that falls inside a given layout region). This is slightly hackey though and would probably break once the layout changes, requiring some sane default.

Another way of handling it would be to add a preference that specifies a corner to add the panel to and then find the layout region in that corner, sending the panel to it. This would work better for folks who change their layout frequently. Optionally, it could also create a new layout region, but I figure that would also have to have an associated preference, so who knows.

At any rate, right now, the fixed panel location is something of a hindrance, especially given that we're pretty much only seeing widescreen displays and panels take up the entire width of a window, thereby wasting a lot of space. So, again, it'd be nice to be able to move around panels and treat them like tabs. If nothing else, it would be nice to see them at least work in a way that's a lot less obtrusive.

+3

A brief description of the function may be good

Hari K T vor 13 Jahren • aktualisiert vor 13 Jahren • 0
A brief description of the function may be good :) , so we know in autocompletion whether we are looking for the same or not.
+3

Tooltips for Find appear below bottom of the screen

Daniel Matarazzo vor 13 Jahren • 0
On OS X, if the window reaches the bottom of the screen the tooltips for buttons in the Find box appear offscreen.
+3

on_selection_modified is invoked only with the first view, not the view whose selection was modified

glyph vor 13 Jahren • aktualisiert vor 13 Jahren • 0
I expected that in my event listener, on_selection_modified(view) would take the view whose selection was modified.

However, as per the API documentation, "many of these events are triggered by the buffer underlying the view, and thus the method is only called once, with the first view as the parameter".  So on_selection_modified is just invoked with whatever the open view happens to be.  However, this does not seem accurate: my understanding is that the selection is a property of the view, not the buffer.  (This is borne out by the fact that different View objects with the same buffer_id() will return different values from sel().)

This means that plugins such as SublimeLinter will only show me errors in the leftmost pane that happens to have a particular file open.

Worse, I can't find a way to quickly find all other open views so that I can easily update them, other than scanning through every view open in the non-current group, looking for matching buffer_id()s.
+3

Setting to auto resize Open File sidebar based on file name or folder

Jacob Hayes vor 11 Jahren • 0

Add a setting to make the Open File sidebar automatically resize when opening/renaming files and folders. Instead of having to double click on the sidebar's outline to resize, it would do so automatically.


To extend this, could add another setting to set the max width either in pixels or maybe % of workspace.

+3

Custom Extension Syntax Highlighting Mode

Austin Condiff vor 13 Jahren • 0
It would be nice to associate a certain extension with a certain syntax highlighting mode. For example, I'd like to associate .css.php files with the css mode.


Customer support service by UserEcho