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 239573

Summary:	Editor needs to select expression / syntactical element
Product:	javascript	Reporter:	kimsp <kimsp>
Component:	Editor	Assignee:	Petr Pisl <ppisl>
Status:	REOPENED ---
Severity:	normal
Priority:	P3
Version:	8.0
Hardware:	PC
OS:	Mac OS X
Issue Type:	ENHANCEMENT	Exception Reporter:

Description kimsp 2013-12-17 19:52:47 UTC

Netbeans really needs functionality like IDEA ctrl+w or Eclipse alt+shift arrow up or arrow down.

Not having an intelligent way of incrementally selecting the surrounding scope is a show stopper as it hinders my productivity.

See more here:
http://www.jetbrains.com/idea/webhelp/selecting-text-in-the-editor.html#d1233299e196

http://www.vogella.com/articles/EclipseShortcuts/article.html

Comment 1 kimsp 2013-12-17 20:02:11 UTC

I found, of course after filing the bug, that Netbeans has the feature. But why is it not advertised more, I can't seem to find it in the shortcut keys pdf nor in the menus (I found it here: http://netbeans.dzone.com/news/10-handy-editor-shortcuts-netbeans-ide-60)

Comment 2 kimsp 2013-12-17 20:34:17 UTC

I have decided that this is relevant as the aforementioned feature does works in Java files and but not all all in JavaScript file and only somewhat poorly in HTML files. For an editor that claims to focus and HTML and JavaScript this i bad.

Exampe for HTML:

Consider this:

<meta charset="utf-8">

If I place the curser at the - in the "utf-8" attribute I would expect that pressing alt-ctrl period would select the "uft-8" but it actually select the whole shown element.

And for JavaScript there is nothing to show, it simple does not work.

Comment 3 Svata Dedic 2013-12-17 20:45:48 UTC

'Key bindings' component just provides a way/ui/API how to bind a key to a certain plugin-provided function. 

In this case the function does not even exist in the mentioned languages (javascript, html). Moving to appropriate component (I would give JS slightly higher priority than HTML)