Nope.
Under HTML, insert a new tag (Ctrl+Alt+W) type ‘div’ say, then press Tab. Closing tag now jumps
Nope.
Under HTML, insert a new tag (Ctrl+Alt+W) type ‘div’ say, then press Tab. Closing tag now jumps
Yeah, HTML tags are worse than before. The closing tag jumps back a tab when the cursor is between the opening and closing tag and you press enter.
The PHP indentation is very annoying now, because I have to correct it every time manually.
Before when typing {:
[code] function count($table, $field)
{
}
[/code]
Now:
[code] function count($table, $field)
{
}[/code]
It’d be nice to be able to implement indentation as a plugin (possibly through sublime_plugin.EventListener).
There’s a frustrating quirk with Python now (not sure, but don’t remember seeing it before), probably with other languages too:
You start with something like this (| = cursor):
class Foo:
def foo(self):
pass|
If you press enter, cursor moves to the next line aligned at the start of “pass”, which is to be expected. Now suppose you want to write another function: you press backspace to move the cursor 1 indent back, press enter and it jumps back to “pass” level again:
[code]class Foo:
def foo(self):
pass
|
[/code]
While you could teach yourself to press enter first and then de-indent, the editor should probably keep in mind that I explicitly decreased the indentation level (by pressing backspace) and not just blindly use the source code.
C++ indentation indeed works better now!
Pressing enter in this case indents automatically:
if (1)|
and unindents when pressing enter here:
if (1)
foo;|
Please do not regress this behavior when fixing regressions.
There also seems to be a new quirk with Javadoc/PHPdoc-style comments (the /** … */-style comments) in this new build. Here is an example of a properly indented Javadoc/PHPdoc-style comment:
[code]/**
Not too bothered about it yet, as I don’t add these comments terribly often.
Always appreciate your great work!
@farmerpaul: check out the DocBlockr plugin (https://github.com/spadgos/sublime-jsdocs)
I came to say what zee said.
Python indentation is a bit annoying. I tried turning auto indentation off thinking that without it pressing Return would at least keep current indentation level (basically the only kind of auto-indent I really want), but it turns out that no, without auto-indent we always go back at the beginning of the line.
So I’m stuck with this new auto-indent.
Some aspects of this don’t seem to work for me. Specifically:
[code]/**
– becomes –
/**
When I try this, I do not get the second line as described
I am very pleased that you added this Ruby expansion.
But it should also work when a word is selected (like in TextMate).
+1 on this one - Python indenting seemed like it behaved better prior to the recent changes…
Agreed! I use the same style of coding for classes and functions, and this is a little annoying to correct all the time. Although I can understand that it is difficult to provide the best solution for everyone, I have a feeling that the first example you gave is a much more common coding style than the second indention style. Best style for me would be: don’t indent unless a brace, bracket or parenthesis has been opened but not been closed.
Cheerleading too soon
[code]if 1:
if 1:
if current < 8:
current = 8
s.set(“font_size”, current)
sublime.save_settings("Base File.sublime-settings")
class ResetFontSizeCommand(sublime_plugin.ApplicationCommand):
def run(self):
s = sublime.load_settings(“Base File.sublime-settings”)
[/code]
Try putting the cursor in front of class
and hitting enter