Home Download Buy Blog Forum Support

Dev Build 2172

Comment indenting in Build 2172

Postby farmerpaul on Mon Jan 30, 2012 10:29 pm

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: Select all
/**
 * Description.
 *
 * @param type $variable description
 * ...
 */

Granted, I've never actually seen these kinds of comments auto-indented in SublimeText quite the same way I was used to in VIM, where each newline produces a new asterisk in the appropriate column as well as the correct number of spaces following it, but it has never really bothered me until now. Now, in Build 2172, SublimeText prefaces each newline of a PHPdoc-style comment with a tab/softtab. I have to hit backspace to delete it, then add a space, then the asterisk, then another space, before typing my intended line of text. Pre-build 2172 at least just started the line with a single space character, after which I could just add the asterisk and another space.

Not too bothered about it yet, as I don't add these comments terribly often. :)

Always appreciate your great work!
farmerpaul
 
Posts: 18
Joined: Mon Jul 25, 2011 6:17 pm

Re: Dev Build 2172

Postby C0D312 on Mon Jan 30, 2012 11:10 pm

@farmerpaul: check out the DocBlockr plugin (https://github.com/spadgos/sublime-jsdocs)
C0D312
 
Posts: 1063
Joined: Sun Jul 10, 2011 3:23 am

Re: Dev Build 2172

Postby hsoft on Tue Jan 31, 2012 12:21 am

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.
hsoft
 
Posts: 12
Joined: Tue Feb 08, 2011 2:40 pm

Re: Dev Build 2172

Postby handycam on Tue Jan 31, 2012 1:46 am

C0D312 wrote:@farmerpaul: check out the DocBlockr plugin (https://github.com/spadgos/sublime-jsdocs)


Some aspects of this don't seem to work for me. Specifically:

Code: Select all
/**
*  Foo bar<<enter>>
*/

-- becomes --

/**
*  Foo bar
*  |
*/


When I try this, I do not get the second line as described
Mac OS 10.9.3
ST 3 (3059)
handycam
 
Posts: 271
Joined: Tue Jan 03, 2012 2:42 pm

Re: Dev Build 2172

Postby royp on Tue Jan 31, 2012 7:42 am

Ruby: #{} is expanded when # is entered in a string

I am very pleased that you added this Ruby expansion.
But it should also work when a word is selected (like in TextMate).
royp
 
Posts: 1
Joined: Tue Jan 31, 2012 7:37 am

Re: Dev Build 2172

Postby jburnett on Tue Jan 31, 2012 9:02 am

zee wrote:There's a frustrating quirk with Python now (not sure, but don't remember seeing it before)


+1 on this one - Python indenting seemed like it behaved better prior to the recent changes...
jburnett
 
Posts: 89
Joined: Wed Jul 27, 2011 9:23 pm

Re: Dev Build 2172

Postby sublimator on Tue Jan 31, 2012 9:07 am

jburnett wrote:+1 on this one - Python indenting seemed like it behaved better prior to the recent changes...


Yep, Python is royally fubarred
It is better to remain silent and be thought a fool, than to speak out and remove all doubt
sublimator
 
Posts: 649
Joined: Thu Mar 20, 2008 5:41 am

Re: Dev Build 2172

Postby Toolskyn on Tue Jan 31, 2012 9:46 am

daris wrote:The PHP indentation is very annoying now, because I have to correct it every time manually.

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.
Toolskyn
 
Posts: 4
Joined: Wed Oct 26, 2011 7:35 pm

Re: Dev Build 2172

Postby jps on Tue Jan 31, 2012 11:19 am

2173 should address the above issues - please let me know if this isn't the case.
jps
Site Admin
 
Posts: 3067
Joined: Wed Mar 19, 2008 12:33 pm

Re: Dev Build 2172

Postby jbrooksuk on Tue Jan 31, 2012 11:42 am

jps wrote:2173 should address the above issues - please let me know if this isn't the case.

HTML and PHP seem to be working for me!
jbrooksuk
 
Posts: 765
Joined: Sun Apr 11, 2010 10:37 am
Location: England

PreviousNext

Return to General Discussion

Who is online

Users browsing this forum: QED1224, yitzhakbg and 24 guests