there could be hidden characters in the code causing the issues you could view a file in a text editor such as bbedit or sublime and view or remove all the spacing on the line in front of your code and try and see if that works.
I have yet to see any indication that your crashes are related to indentation. Have you figured out any way to reproduce these crashes consistently? Can you please start a new thread?
I shared an actual PHP file, via dropbox, on this thread. As far as I can tell, there is nothing unusual about the files. Especially since it is doing this to EVERY file within my project, and that it worked just fine with the same files prior to the update.
I just got the updated to KE9 and the problem still exists! I have used KE for YEARS and I cannot believe you guys would produce such a significant bug. Can you guys PLEASE help me fix this? KE has essentially become unusable being that I have to adjust manually each and every file preference that I open.
The commit I referred to is in Komodo 9.3, which is currently under development. A nightly will soon be available with this fix.
I understand your frustration but we are doing our best to address your concern here as is evident by our numerous responses to this thread. Lets keep this nice and civil.
Thank you for your understanding. I will look for the update soon. Could you possibly post in here once the nightly update is available for me?
Still no update?
We’re intending to push it today actually. Note that’s “intending”, since this is the first 9.3 nightly we do a little bit of testing to ensure it doesn’t break anything significant. This WILL be a “nightly” release so it is bound to have bugs.
Note we delayed the nightly until next week, most likely Monday.
Reason being that today is our feature-freeze, so we figured we might as well release the first nightly with all the 9.3 features in there. We’ll start rigorous testing and bug fixing next week.
Is this the IDE 9 or Edit 9? I use Komodo Edit, can you direct me to the correct nightly download?
Nevermind, I found it. Just had to navigate to the correct tab.
FYI - I just installed the 9.3 KE nightly and the issue still exists. Every file I open has the incorrect indentation and must be manually adjusted. This is very annoying.
I’ve always had problems with Komodo’s indenting. I don’t know how to fix it globally and it devolves into a cluster-frack. I’ll update my settings, but then some files are still using 2 spaces.
How can I set komodo to always use tabs of 4 spaces and - here’s the catch - NEVER-ever allow customized file indentations? This really messes me up, especially with python.
The fix does not work retroactively, you need to reset your file level settings and then it should not happen again.
Open a new tab (ctrl+tab) and on the new tab page hit Troubleshooting > Reset File Preferences. Note this troubleshooting menu is slightly bugged at the moment, if it doesn’t work you can manually reset your file preferences by shutting down Komodo and deleting doc-state.xmlc from your profile folder.
I reset the file preferences manually be removing the doc-state.xmlc from my profile folder. Then I started up KE 9.3 once again and the problem still exists. Every file I open has the incorrect indentation (2,2) and must be manually adjusted. I have been using KE 8.5.4 on a daily basis and it does not have this issue.
Could you give a sample file? Perhaps the indentation detection is simply off.
Also, these are still your indentation settings? (including for the language you are using)
Yes, those are still my indentation settings - I have not changed anything.
Here is a simple php file I have in my project. Again, when I open this file, it opens with 2,2 indentation, I have to manually adjust it.
Could you create a userscript (macro) with the following contents:
var log = require("ko/logging");
log.getLogger("koDocument").setLevel(10);
log.getLogger("editorconfig").setLevel(10);
Save it and execute it, then restart Komodo (we want a clean log). Once started execute the macro and then open one of your files. Then copy the error log into this thread (Help > Troubleshooting > View Log File).