I think, this was mentioned before somewhere but couldn't find it anymore.
I work with many open files at once which have the same name and are only differentiated by their path. So the list of open files result in being 5x product.py, complete.py etc..
It would be nice to see the end of the path within the empty space either on the left or on the right side of the filename.

For example on the left:
…api/input/collector/product.py
…ox/restapi/abstract/product.py

For example on the right:
product.py - …api/input/collector/
product.py - …ox/restapi/abstract/

The path should be shown in a lighter/transparent color so that the filename is prominent.

PS I prefer the variant on the right.

Why is it that the self.view.add_regions method triggers the on_selection_modified event?

How can I access the folders in the sidebar from a plugins perspective? I want to get all the paths in order to find files within them with my own algo.

For example I do this:
* Create a new window.
* Load 3 files into the pane.
* Switch to a 2 pane layout.
* Move one file into the other pane.
* Switch back to the 1 pane layout.
* Switch back to the 2 pane layout.

I wish that it would remember that I moved that file into the second pane before.

When copying e.g. the Python/Python.sublime-build file into my User folder I get two entries for Python and "Automatic" takes the original one instead of my user defined one.
It would be better, that my user defined build would just overwrite the original one so that "Automatic" would use my own settings.

One cannot see which tab triggers have been defined when browsing the snippets menu. It would be nice to see them there, too.

Currently I often work with 3 panes (1 col, 3 rows). It would be nice to be able to collapse/minimize them by clicking on the resize handle. I've seen that double clicking seems to restore the size to the original one defined in the layout. By using alt+double click it could collapse.
Of course this would only work properly when not using layouts like quad pane.

I've written center_view_on_line.py. Today I wanted to refactor it 'cause it behaved strangely in some cases. Now I'm trying to come up with an algorithm to center the visible region over the current line or selection. I've got the final row numbers and could translate them into a proper region. If I compare the visible region I get by scrolling there manually and the target region my script calculates they seem to be nearly identical. But the view scrolls somewhere else - often the cursor is at the top of the screen. When querying the visible region again the coords are totally off.

Some vars I work with:
visible_region = (366, 998) # manually centered view
selection = [26, 26] # cursor in line w/o selection
region = [26, 26] # in this case same as selection
visible_region = [16, 36] # first row, last row from above
size = 2099 # self.view.size()
region_size = 0 # diff between region end and begin
visible_size = 20 # diff between last and first row
begin = 16 # calculated first row
end = 36 # calculated last row
target_region = (366, 946) # calculated for self.view.show()
target_region = [16, 36] # translated into first, last row
visible_region = (603, 1351) # region I get after self.view.show()

Any idea?