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: | Keystroke set redundancy | ||
|---|---|---|---|
| Product: | cnd | Reporter: | Torbjorn Norbye <tor> |
| Component: | Terminalemulator | Assignee: | ivan <ivan> |
| Status: | CLOSED FIXED | ||
| Severity: | blocker | CC: | akemr |
| Priority: | P3 | ||
| Version: | 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
It looks like request for Ivan IMO. Will add a setKeyStrokeSet. Target milestone -> 3.3.1. Target milestone -> 3.3.1. Target milestone -> 3.4 Target milestone -> 3.4 Target milestone -> 3.4 Target milestone -> 3.4 This was actually fixed in 3.3.1 closed moving terminal emulator issues to terminalemulator component. To see the correct version and target milestone of this issue look at Issue Activity table. |
My terminal emulator window is running an external shell process, so I want control-p to mean "go to previous command", not bring up the NetBeans print dialog. On the other hand, most shell commands do not use the f-keys, and this is where most of NetBeans shortcuts are located, so I want F7 to step the debugger. Therefore, I'm using Term's ability to define keystrokes that should not be consumed. This does however lead to a bit of redundancy. Here's my e-mail to Ivan on the subject, and he asked me to file an issue in issuezilla: > Just fyi - I'm adding keystrokes to the set. Since I want any combination > involving an F-key to be passed on to NetBeans, and since I'm ignoring > the Meta key (NetBeans only seem to use shift, control and alt in their > shortcuts) I get eight combinations per f-key - for a total of > 12 f-keys times 8 combinations = 96 keystrokes in the hashset (and there > is one hashset per terminal window, e.g. I get one for the dbx window, > the i/o window, the access error window, the leaks term and the blocks > term). > > Is this ok you think or can it be done smarter? Can the hashsets be > shared? (I don't think so since I only get the accessor for the keystroke > set). Can special f-key support be built in to term?