Fork me on GitHub
#proton
<
2016-02-12
>
jessejanderson00:02:50

I had previously installed and then removed proton, then re-installed again. Not sure if that could be related. Other than that I can’t think of anything out of the ordinary I was trying.

dvcrn03:02:44

any ruby people here? Would love some feedback on this https://github.com/dvcrn/proton/pull/139

jessejanderson05:02:24

You doing linters in lang layers?

dvcrn05:02:59

added rubocop, thanks!

dvcrn05:02:28

@jessejanderson: no, lang layers hook into :tools/linter and specify packages to be installed when the linter layer is enabled

dvcrn05:02:40

if you disable :tools/linter, it will wipe all linter packages in all langs

dvcrn05:02:51

rubocop seems really good

dvcrn05:02:55

great way to get started with ruby

jessejanderson05:02:29

Yah, it’s pretty solid.

dvcrn06:02:16

https://atom.io/packages/highlight-selected whoa. How come we don't have that in proton yet

dvcrn06:02:20

need to add that right away

geksilla09:02:15

regarding ruby layer I was hoping on https://github.com/ypresto/robe-atom but looks like author doesn't support it any more(

geksilla09:02:33

robe mode for emacs is awesome

geksilla09:02:50

also https://atom.io/packages/rubocop-auto-correct and bind to SPC m L f mnemonic to Linter fix

austincrft14:02:11

@dvcrn: I have that installed, but I haven't really found a good use for it. Other than looking kinda cool, what do you see as the benefit of this package/

austincrft14:02:11

@dvcrn and @geksilla: I have some concerns about packages being added to the core layer. Each package adds load time to Atom (maybe small, but still there) and there have already been incidents of people wanting to disable packages. Do you think the goal of the core package should be to stay slim, at least until a way to disable packages is available? In the example of the highlight-selected plugin, I don't feel it really adds much to the development experience, and it'd be very easy to just add it to the additional plugins.

geksilla15:02:50

Yeah load time may be an issue, but I remember one comment from issue related to some package "Do you often reload your editor?" simple_smile

geksilla15:02:35

we can provide config option to disable any package, even from core layer

geksilla15:02:59

actually proton itself take about 500ms to load first time

lucien.knechtli15:02:03

keep in mind that it has to reopen every time you switch to a different project

geksilla15:02:36

just wondering, can you post your atom's startup time? my total 17666ms

geksilla15:02:52

Window load time17666ms Shell load time1548ms Workspace load time431ms Project load time234ms Window state load time32ms

lucien.knechtli15:02:24

where can I find that info?

geksilla15:02:55

from Command Palette type timecop

lucien.knechtli15:02:17

Window load time18383ms Shell load time1373ms Workspace load time915ms Project load time997ms Window state load time74ms

austincrft15:02:23

Startup Time Window load time5729ms Shell load time814ms Workspace load time0ms Project load time0ms Window state load time1ms

geksilla15:02:20

I think @austincrft on mac? simple_smile

austincrft15:02:27

Windows, actually!

lucien.knechtli15:02:39

without the project (which is a pretty massive one) I get Window load time1918ms Workspace load time0ms Project load time0ms Window state load time0ms

austincrft15:02:21

Yeah, that was me loading our webpages folder

lucien.knechtli15:02:50

that project I've got like 7 buffers open, an expanded file tree, and probably several thousand lines of code to render between all those buffers

lucien.knechtli15:02:10

so guess that makes sense lol

austincrft15:02:08

Yeah, that's quite a bit. What's weird to me is that I opened the base project directory (that contains folder I just opened for the timecop), and it took less time

austincrft15:02:15

Maybe they get cached or something?

austincrft15:02:46

I know that the filenames get indexed for the fuzzy-finder

lucien.knechtli15:02:01

weird. my project buffer state seems to not be updating when I restart atom. keeps reverting to an earlier set

austincrft15:02:55

That seems strange

austincrft15:02:10

Do you guys know if there's a way to set project-specific settings?

austincrft15:02:02

Yeah, is that supported natively?

lucien.knechtli15:02:17

that's just in project.cson

lucien.knechtli15:02:37

and yes it works. its actually in one of the examples

austincrft15:02:58

Well, I guess that would've been the intelligent place for me to look 😛

lucien.knechtli15:02:31

wait not sure it actually works with proton - I have the editor default set to 4 also. lemme see

lucien.knechtli15:02:24

ack nope. its overwritten by proton settings looks like

geksilla15:02:10

probably workaround is to open project.cson and hit save

austincrft15:02:10

I was talking to someone on reddit about project support in Atom and they said this

It doesn't reset original settings when you swap project. So if you have custom settings per project (and I do), those "leak" to other projects when you swap. In addition, it opens a new window whenever you change project, which is really bad since i want to alt tab easily.
I don't use it enough to know how true this is.

geksilla15:02:55

we need to handle this on proton side using project-manager provided service

lucien.knechtli15:02:12

I concur with everything that person said