Would it not make more sense to automatically reopen the file with the new name? Or at least make it an option?
provide a way to flatten sidebar tree structure so it only includes directories with files, like intellij
some projects have an annoying amount of directories, without files, just more directories to navigate down till you get to files.
intellij and some other editors.
provide a way to flatten the directory tree. so instead we have a list of shortened dir names for those dirs that contain src files.
allow a view with a list like structure:
Of course I'm not syncing the session because it would make no sense.
My entire professional career I've been looking for two things. A webhost with a great panel and a truly great editor.
[trying to autocomplete: "Commit"]
Which will also show the location of the function or the variable you are looking to autocomplete.
A while ago I asked this question on StackOverflow:
Code Completion that would access the filesystem would be very helpful, not alone for Images, but also for css/js files and so on...
Now I would like to ask this here. Is there anything planned towards this, are there existing plugins that are doing something like this?
Tabs become pretty much unusable once there are too many open. You can't read the text, and the close box goes away. And if the close box is still there, I find myself clicking it by accident because the tab is too small.
I'm used to using Eclipse, and I like how they limit the number of tabs shown based on how much space is available. This way, you can always read the beginning of the file name, and the close box is always visible. When there are more tabs that can be show, a little menu shows up on the right. The menu shows the "shown" tabs in bold", and the ones that can't be shown are normal. You can then show a tab by selecting it from the list, and another visible one will take its place.
Larger version of the screenshot available here: https://dl.dropbox.com/u/4830253/sublimetext_python_syntax.png
TextMate behaves the same in all cases. If compatibility is more important than solving the problem, so be it. However, I would suggest solving those problems by:
1. supporting punctuation.separator.parameters.python for function calls and punctuation.separator.tuple.python/punctuation.separator.set.python for the respective data structures
2. adding punctuation.section.block.begin.python analogical to punctuation.section.class.begin.python
3. identifying asterisks in function definitions as keyword.operator.arithmetic.python OR adding keyword.operator.unpacking.python
Customer support service by UserEcho