(Leaving this to read it later…)
And it’s a week since we were said about new upcoming build… I love Sublime Text 3, bought it and do hope to get updates and any reaction from the developer at least sometimes.
In faith we believe.
(Leaving this to read it later…)
And it’s a week since we were said about new upcoming build… I love Sublime Text 3, bought it and do hope to get updates and any reaction from the developer at least sometimes.
In faith we believe.
My ST3 installation on OSX just said there is an update available, but error downloading manifest. OOOOH!
I got the same on windows 64 portable. Hopefully this is a sign that new things are coming…
According to sublimetext.com/3dev, the changes are:
I see. You said this over a week ago. I guess “preparing a new build” includes infinite time spans, but this is ridiculous.
The last two builds are TOTALLY useless on win64 and large projects. Get your act together, jon…
[quote=“Arjan”]
I see. You said this over a week ago. I guess “preparing a new build” includes infinite time spans, but this is ridiculous.
The last two builds are TOTALLY useless on win64 and large projects. Get your act together, jon…[/quote]
Jon needs to be more responsive indeed, but you should also note that not everybody uses win64 or have problems with large projects (and these aren’t the only issues Sublime have either). It would be great if we had an official issue tracker instead of having to report bugs on a forum and hope that someone from Sublime HQ will see and fix it someday.
Arjan, if you are having speed related issues, please create a new post, specifying exactly what is slow, which OS version, which Sublime Text build, how large your project is, if indexing is currently occurring (i.e., multiple sublime_text.exe processes, and a percent complete indicator in the status bar), and if the files are on a local or remote file system.
FWIW I haven’t seen any Windows related speed issues, irrespective of project size.
Arjan, I am on Win64 and also work with projects with 1000’s of files. I am experiencing none of the speed issues you allude to.
Also your complete lack of respect for the software developer is really amazing. Where is your patience?
OK, Arjan, what the heck are you working on that is 17K files? The 2.6 linux kernel has that many files, and no single developer can keep track of that much stuff. Break your projects down into smaller subprojects, man. The problem isn’t your tool, its your organization. Do you seriously expect us to believe that you need to access 17k files every day? It really just sounds like you’re going out of your way to be obtuse.
I really, really, really don’t care what you believe or not. It’s a huge project partly because the majority of the files are generated, some of which need hand-editing.
The point is that it works on ST2 on the same OS instance, so I figured it was important to submit the problem report (as done in separate post)
It’s one thing to report a problem and it’s another thing to report a problem by saying „omg, this product suck, nobody helps me”.
If disabling the indexing will somehow fix the problem, you could just disable the indexing and you are all set.
You clearly don’t make the difference between a beta vs a stable release.
It’s easy to pick on Arjan here, but the main reason that he is not get a satisfying answer is because the bug report was not presented in the right way. A bug report that says “performance sucks with lots of files” is almost impossible to answer. Being able to effectively ask questions is an important skill, especially when working in the computing field. Google “the right way to report a bug” and you’ll find lots of resources explaining how to effectively report a bug. The most relevant point in this context is that you need to provide a way for the developer to reproduce the problem. Unfortunately Arjan is the only one who is seeing this issue so the onus is on him to provide a way to reproduce the problem so it can be fixed.
What jbjornson says…
Told you!, I’m pretty sure ( ) the problem Arjan has is because of the “generated files”, I mentioned this possibility in the other thread, and I got ignored. This just had happened to me. IF you have opened a project with files that are being changed by another process the index of your project will run constantly, keeping CPU high.
[quote=“tito”]What jbjornson says…
Told you!, I’m pretty sure ( ) the problem Arjan has is because of the “generated files”, I mentioned this possibility in the other thread, and I got ignored. This just had happened to me. IF you have opened a project with files that are being changed by another process the index of your project will run constantly, keeping CPU high.[/quote]
Well, tito, the thing is that the generator isn’t running when i open ST3…
So, it was mcaffe “touching” the files,
which to me is exactly the same thing.
Glad you solved the problem, welcome to the “frustration” team. Now, hope you can accept it is this way, who knows what’s going on, try to cooperate in productive and civil ways, hoping for the best.
[quote=“tito”]So, it was mcaffe “touching” the files,
which to me is exactly the same thing.
Glad you solved the problem, welcome to the “frustration” team. Now, hope you can accept it is this way, who knows what’s going on, try to cooperate in productive and civil ways, hoping for the best. [/quote]
No can do.
My mum once told me; “If you have nothing nice to say, don’t say anything at all.”