This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ BUILD # : 200711081200 ] [ JDK VERSION : 1.6.0_02 ] Sometimes when I start NB, the active source document has default tab size 8. All others have the tab size I have configured, which is 4. We don't expand tabs to spaces. After closing the source and opening it again it has the correct tab size.
*** Issue 122175 has been marked as a duplicate of this issue. ***
With FCS, this is happening to me every time I start NB. It is becoming a bit frustrating.
I'm noticing exactly the same behavior and, like the original poster, it seems to be happening more frequently with the official release of 6.0. I'm running under JDK 1.6_02 on Fedora 5.
Same here on Windows XP, JDK 1.6.0_03-b05
This happens to me every time I start netbeans. I even put netbeans on my home PC to see what happens and it has the same behavior. Please fix.
It seems to go away when I remove the option "-J-Dnetbeans.keep.expansion" from my netbeans.conf file
I don't have (and never did) a "-J-Dnetbeans.keep.expansion" in my netbeans.conf file. Is there anything else you might have changed? My netbeans.conf file has mainly Java memory management items, with a few EE things sprinkled in. I am using Windows XP. netbeans_default_options="-J-Dorg.netbeans.modules.tomcat.autoregister.token=1196712843684 -J-Dorg.netbeans.modules.tomcat.autoregister.catalinaHome=\"C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0.14\" -J-Dcom.sun.aas.installRoot=\"C:\Program Files\glassfish-v2\" -J-client -J-Xss2m -J-Xms32m -J-Xmx256m -J-XX:PermSize=32m -J-XX:MaxPermSize=200m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled -J-XX:+CMSPermGenSweepingEnabled"
BTW, as another work-around for this issue. You can also bring up the options dialog (Tools -> options), wait a few seconds and then cancel it. This will correct the problem as well without having to close and then re-open the file. However, there often are repaint issues that can be cured by scrolling around a bit. Waiting a few seconds after the dialog appears is important for me. I tend to do this as soon as NB will let me after startup. Possibly the wait just lets NB finish initializing enough to let this work.
With the old settings infrastructure ripped out and deprecated this should no longer be a problem. Please check in a dev build or the upcoming 6.1M1.