Home Download Buy Blog Forum Support

Dev Build 2157

Dev Build 2157

Postby jps on Mon Jan 02, 2012 10:41 am

Dev Build 2157 is out, with a few tweaks
jps
Site Admin
 
Posts: 3071
Joined: Wed Mar 19, 2008 12:33 pm

Re: Dev Build 2157

Postby stiang on Mon Jan 02, 2012 10:48 am

Hmm, my tab bar looks like this now:
Screen Shot 2012-01-02 at 11.44.20.png
Visual bug with 2157
Screen Shot 2012-01-02 at 11.44.20.png (44.81 KiB) Viewed 2112 times


It was fine with 2156.
stiang
 
Posts: 39
Joined: Sat Jan 29, 2011 12:34 pm

Re: Dev Build 2157

Postby senzo on Mon Jan 02, 2012 11:15 am

Deleting files via the side bar will send them to the trash, rather than deleting them outright

like
senzo
 
Posts: 106
Joined: Tue May 24, 2011 9:17 am

Re: Dev Build 2157

Postby ryanlecompte on Mon Jan 02, 2012 12:16 pm

Hello, I'd like to report a bug that causes the editor to crash hard to the point where it must be restarted. When I open up a Ruby source file and add a comma character to a specific part of the file, the whole editor crashes. Please let me know where I can the find the crash logs if it would be helpful in diagnosing the problem. Right now I have to work around this by entering a space and then the comma so that it doesn't crash. It's a weird bug.

It crashes when I add a comma directly after this line:

:path => "/photos/:id/:style/:filename"
ryanlecompte
 
Posts: 20
Joined: Wed Dec 28, 2011 2:16 pm

Re: Dev Build 2157

Postby CaptainCrowbar on Mon Jan 02, 2012 12:46 pm

The "New version available" alert has been reporting the wrong release number for several releases now. When 2157 was available it reported that 2156 was available, when 2156 was out it reported 2155, and so on. I can't remember when this started, at least several versions ago. The actual update isn't broken, it installs the latest version, it just reports the wrong number on the alert box.
CaptainCrowbar
 
Posts: 24
Joined: Tue Aug 02, 2011 4:31 am

Re: Dev Build 2157

Postby jps on Mon Jan 02, 2012 12:52 pm

ryanlecompte wrote:Please let me know where I can the find the crash logs if it would be helpful in diagnosing the problem.

On OS X, you can get the crash logs via the Console application, under the User Diagnostic Reports section.

Adding a comma after that line doesn't cause any issues for me, does it happen for you on an empty file containing nothing but that line?
jps
Site Admin
 
Posts: 3071
Joined: Wed Mar 19, 2008 12:33 pm

Re: Dev Build 2157

Postby jps on Mon Jan 02, 2012 12:53 pm

stiang: that indicates some of the referenced images in the theme are missing. http://www.sublimetext.com/docs/2/revert.html will fix it.
jps
Site Admin
 
Posts: 3071
Joined: Wed Mar 19, 2008 12:33 pm

Re: Dev Build 2157

Postby C0D312 on Mon Jan 02, 2012 1:10 pm

Auto complete: Tweaked popup hiding rules


Wow, I got way too excited when I read this...

You'll be getting my money today ;)
C0D312
 
Posts: 1063
Joined: Sun Jul 10, 2011 3:23 am

Re: Dev Build 2157

Postby ryanlecompte on Mon Jan 02, 2012 1:11 pm

jps wrote:
ryanlecompte wrote:Please let me know where I can the find the crash logs if it would be helpful in diagnosing the problem.

On OS X, you can get the crash logs via the Console application, under the User Diagnostic Reports section.

Adding a comma after that line doesn't cause any issues for me, does it happen for you on an empty file containing nothing but that line?


Actually it doesn't fail on a single line in a new file, it just must be this particular file that I have (unfortunately I can't copy the rest of the surround code).

Here's the crash that I'm seeing in console:


1/2/12 5:09:14.055 AM com.apple.launchd.peruser.501: ([0x0-0x118c18b].com.sublimetext.2[948]) Exited abnormally: Broken pipe: 13
ryanlecompte
 
Posts: 20
Joined: Wed Dec 28, 2011 2:16 pm

Re: Dev Build 2157

Postby stiang on Mon Jan 02, 2012 1:59 pm

CaptainCrowbar wrote:The "New version available" alert has been reporting the wrong release number for several releases now. When 2157 was available it reported that 2156 was available, when 2156 was out it reported 2155, and so on. I can't remember when this started, at least several versions ago. The actual update isn't broken, it installs the latest version, it just reports the wrong number on the alert box.


Yeah, it’s been that way for quite a while. I reported this back when 2063 was released :)
stiang
 
Posts: 39
Joined: Sat Jan 29, 2011 12:34 pm

Next

Return to General Discussion

Who is online

Users browsing this forum: BestGreek, Exabot [Bot], Google [Bot] and 18 guests