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.

Bug 132772 - Tab size setting not retained in JSPs on app start
Summary: Tab size setting not retained in JSPs on app start
Status: RESOLVED DUPLICATE of bug 134217
Alias: None
Product: javaee
Classification: Unclassified
Component: JSP (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker with 1 vote (vote)
Assignee: Marek Fukala
URL:
Keywords:
: 134114 (view as bug list)
Depends on: 90403
Blocks:
  Show dependency tree
 
Reported: 2008-04-14 15:07 UTC by velodiver
Modified: 2008-06-24 19:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description velodiver 2008-04-14 15:07:34 UTC
Tab sizes are not applied/retained in JSP pages when the IDE opens. 

Setting: ExpandTabsToSpaces=false

Import setting from 6.0 (3 spaces)- Tab size remains 8.


Set tab size to 3 in Options.  Tabs go to 3 on JSP page as expected.  
Restart the application. Tab size returns to 8, but setting remains 3.
Comment 1 Jiri Prox 2008-04-15 08:08:01 UTC
Which build do you use? This looks similar to issue 130644, but it should be fixed in builds after Mar 25 

Did you import the userdir from previous Netbeans version?
Comment 2 velodiver 2008-04-15 15:24:52 UTC
I am using 6.1 RC1. (after Mar 25).

It is similar bug 130644.  However, I can change the number of spaces/tab. The bug is that that setting is not applied 

to JSPs when the project is closed and reopened,  or the application restarts.  The Options editor still shows my
original setting (3 spaces), but the number used on JSPs is the default 8 spaces. 

Each time I open the project, I have to change the value of the spaces/tab so that JSPs use a value other than 8.  


I do not know it I imported userdir from the previous version. I allowed NBs to import user settings - so what ever it
does by default. 



Comment 3 Jiri Prox 2008-04-16 10:11:46 UTC
Thanks for info, I can repoduce it in RC2 as well (at least for tab size).
The common java files seems to work correctly -> reassigning to jsp editor for evaluation
Comment 4 Marek Fukala 2008-05-14 10:29:23 UTC
*** Issue 134114 has been marked as a duplicate of this issue. ***
Comment 5 entonio 2008-06-14 23:50:58 UTC
This happens also with javascript files. It's quite annoying: in practice, it forces me to, each time I start NB, open
the Options, see that tab size and spaces per indent are both '4' as I'd defined them, change them, close the options,
see that the editor has applied the new (unwanted) settings, open the options, and restore them to '4'. And then the
editor applies the new (wanted) settings and all goes ok... until I close NB and have to so it all over again.

This happens at home with Windows XP, both with an old user dir and with a completely new one. It doesn't seem to happen
at work with Vista.
Comment 6 velodiver 2008-06-17 15:27:16 UTC
Yeah, 

Amazing how many things that worked in 6.0 are broken in 6.1.

The shortest way to re-apply your settings is: Open Options, change the tab settings to something else, switch to
advanced mode (which applies changes), then back to basic mode and reset the tab settings to what they were when you
started. Close Options and the changes are applied.

Hard to believe this didn't make it into the last patch.


Dave
Comment 7 Marek Fukala 2008-06-21 16:04:40 UTC
Vito, this seems to be a generic problem - user complains about javascript and jsps as well. Are you aware of a problem
in this ares? Do you have an issue for it?
Comment 8 Vitezslav Stejskal 2008-06-23 14:23:41 UTC
Yes, I'm aware. There is bunch of issues complaining about indentation settings, some filed against the editor, some
against other modules. Whenever somebody pointed me to such an issue I marked it as depending on 90403, which I think
was the common culprit. 90403 is now fixed and I'm going to go through its dependencies and re-check the status of these
issue.
Comment 9 Vitezslav Stejskal 2008-06-24 19:31:29 UTC
It's the same problem as issue #134217. Both should be fixed now in trunk.

*** This issue has been marked as a duplicate of 134217 ***