Code formatting problem

Question

Is the code formatting buggy or is it just that I cannot seem to find the correct mix of settings? I hope it is the latter and that someone here may know how to get it
After setting the settings I think I want I get a simple SQL formatted like this.
{noformat}
select username
,sid
,serial#
   from v$session
  where sid  = 11
  and(status = 'ACTIVE'
  or status  = 'INACTIVE')
{noformat}Ignore the fact that the actual query may not be logical...
The first problem is that the different columns are lined up to the left and not indented lika I would like them to be.
The second (and much less important) is that the and/or are not indented like the keywords. I'd like to get the SQL to be formatted like this.
{noformat}
select username
       ,sid
       ,serial#
   from v$session
  where sid    = 11
    and(status = 'ACTIVE'
     or status = 'INACTIVE')
{noformat}How can I make the code formatting result in the above SQL (especially the aligning of the columns)?

Answer 1

Turloch,
Thank you for the reply. I figured this may be a bug, so it is nice to have it confirmed. I can live with it not being correct as long as a fix will show up eventually.
The problem with using tabs or large settings for space is that it causes other parts of PLSQL to look to spread out. One thing that happens is that the right justification of the keywords gets messed up. But I can make soem SQL look OK with it, but that is at the expense of getting other ones to not look good. For example if I get the columns to line up with a leading comma, the concatenation is not correct and vice versa. I also get SQL to look better, but then indentation in PLSQL is too agressive and looks very bad.
I would like to be able to set and/or to be set to be handled as keywords so they too can be right justified. Columns (whether or not concatenated or separated with a comma) should be possible to align with the column in which the first column starts.
While I'm at it, there seems to be an issue with the formatting of keywords such as inner join. I think inner too should be considered keywords so it can be right justified with other keywords. Same thing with subselects, they end up the the left of the right column of the keywords.
I think the formatting features are really good now. There is still room for improvement to be able to control it enough to make it look exactly like I want, but it is getting close and flexible enough to allow many different ideas of how the template should be to be configured.
Thanks,
Mathias