Dev Build 2174

[kalipek]

I love this application, but sometimes it eats 80-100% of my CPU almost instantly when I’m starting to edit files (just after start it is always ok, 0-5%) and it stops only after completely shutting down the program.
I have this problem for almost month of testing.
I’m working on Ubuntu 11.10 32bit and Core2 CPU T7200 @ 2.00GHz × 2.

[ge3kusa]

The SublimeLinter (yes, I know an external package) seems to be only working on save now for my JS. Is it just a coincidence that this occurs after the latest update or something else?

[ge3kusa]

I found out that I could “Enable Backround Linting”. I’m wondering why I had to enable that after update, but in any case, that solves the issue if anyone else was looking into it.

[willy1234x1]

It seems like the merging of settings files messed up some plugins, namely SublimeLinter. Like ge3kusa’s example I noticed that my ignored PEP8 settings were gone as well as what he pointed out.

[bgreenlee]

Yes, it looks like package settings files are being ignored. I also noticed that SublimeLinter was ignoring my PEP8 settings, but when I moved them into the global user settings files, it worked again.

[alek.sys]

Hi, thanks for release.
Is there any way to return old font instead of Consolas? Assume it’s “font_face” setting, but what is font name? Consolas is nice, but old font was soooo sexy.

[skaet]

[quote=“alek_sys”]Hi, thanks for release.
Is there any way to return old font instead of Consolas? Assume it’s “font_face” setting, but what is font name? Consolas is nice, but old font was soooo sexy.[/quote]

You can return the previous default font with this setting in the new preferences file

"font_face": "Courier New"

[fred]

[quote=“n00ge”]

OSX: when the default settings have the entry “word_wrap”: “auto” then word wrap can’t be activated, neither through the user settings or the menu.

I just came across this as well.[/quote]

“word_wrap”: “true”

[hubert]

[quote=“fred”]

OSX: when the default settings have the entry “word_wrap”: “auto” then word wrap can’t be activated, neither through the user settings or the menu.

I just came across this as well.
“word_wrap”: “true”[/quote]

Yes that is the work around, but this is a regression.

[spadgos]

Seriously? You prefer Courier New? Please do yourself a favour: hivelogic.com/articles/top-10-programming-fonts/

[andyjeffries]

Consolas is better than Courier New, but why anyone on a Mac would switch from Monaco to it is beyond me! I quite like Inconsolata from that article, but still find Monaco nicer.

Oh well, each to their own.

[handycam]

[quote=“andyjeffries”]Consolas is better than Courier New, but why anyone on a Mac would switch from Monaco to it is beyond me! I quite like Inconsolata from that article, but still find Monaco nicer.

Oh well, each to their own.[/quote]

Indeed. I can’t stand Monaco,

[ge3kusa]

I prefer Menlo

[malpeli]

Good night everyone!
I’m doing something wrong? my CMD+P is now opening the file in a new file. Before he used open the file at the same window and CMD+T had this behavior.

Best Regards

[ianthehenry]

This problem didn’t start with this build, but I don’t know exactly when it started so I’m just gonna throw it here in the hopes that it gets seen.

ctrl/cmd+d, used to select the next occurrence of the current selection, doesn’t respect the “whole word” flag in your find settings (although it does respect the case sensitive flag).

This is a very noticeable problem now because of the new match_selection feature (which also ignores it, but defaults to true instead of false). It would be logical for “select more” to always select the next “highlighted” bit of text, and for the behavior of both to be consistent and user-definable.

Is there some setting I’m missing for this?