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.
Summary: | Wont comment multi-line selection at EOF | ||
---|---|---|---|
Product: | ruby | Reporter: | nigel_bris <nigel_bris> |
Component: | Editing | Assignee: | Erno Mononen <emononen> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Image of failed selection |
Description
nigel_bris
2008-08-31 22:36:42 UTC
I tried this on a current build and it worked for both Ruby and ERb files... Perhaps there is something about the specific lexical tokens on the lines you are selecting. Can you reproduce this with a trivial file (that you can attach) ? Just tested on latest build.... This works if you start your selection from the bottom up.... If you select from a few lines above the EOF downwards to the bottom of the file... then use comment key... This does not comment the last line Seems to work for me now, even if I don't start from the bottom up. Please reopen if you still run into this with 6.7 dev. Still occurs in 200905131401 Image attached.... If you when you use keyboard and shift and down arrow (to select), with the cursor fully left. The cursor ends on the last line (in image the last end) which has no cr/lf at the end of it. THe last line is not selected (but the cursor is on it) and when you press cmd+/ it commens out al selected lines not the last line where the cursor is Created attachment 82549 [details]
Image of failed selection
Returning to this after a long time.. this is actually by design, only the lines that are selected get commented out when commenting out multiple lines (different from commenting out the current line). In your example the last line isn't selected, so it doesn't get commented out even if the cursor is on it. I guess it is a matter of taste whether this is desirable or not, I personally prefer the current behavior. I'm closing this for now at least, but if more people complain about this we should reopen and reconsider. |