keyboard-shortcuts

Anyone know if there is a keystroke shortcut or option to autogenerate a try/catch block around a statement in Visual Studio 2010? I can see what exceptions are thrown if I look at the overlay documentation when I hover over a statement. I'd like to right click -> generate try/catch, as it would save a lot of time in handling all possible cases. Is this possible? sshow Using the mouse Mark your code Right-click Select Surround with... Double-click try Using the keyboard #1 Mark your code using Shift , Ctrl + A , or whatever works for you Press Menu key / Application key (alternatively Shift +

I'm asking the question already asked (and even answered) here: Why are some textboxes not accepting Control + A shortcut to select all by default But that answer doesn't work for me. I have this code: public class LoginForm : Form { private TextBox tbUsername; public LoginForm() { tbUsername = new TextBox(); tbUsername.ShortcutsEnabled = true; tbUsername.Multiline = false; Controls.Add(tbUsername); } } The textbox shows up, I can write on it, I can cut, copy and paste text on it without any problems. But when I try to press Ctrl + A I only hear a "bling" similar to the bling that you hear if

I went to the official Workbench keyboard shortcut page and found this: Function | Keyboard Shortcut | Context -------------------------------+-------------------+----------- Comment/Uncomment lines of SQL | Modifier+/ | SQL Editor However, Control + / doesn't work. I have MySQL Workbench installed on a Windows machine. How do you get the shortcut to work? Thanks for filing the bug report, it's annoying. If you have a full size keyboard try using the division symbol. i.e. The CONTROL + "/" using the division key above the keypad instead of the "?/" key on the main keyboard. It's not nearly as

Learning debugging in PhpStorm and keep accidentally hitting Ctrl + Alt + F8 . I use 3 displays this disconnects the two remotes and goes back to just the laptop. I cannot see this documented anywhere (running Win 10). The worst part is that hitting the combination again does NOT reconnect the displays. Anyone know either: combination to reverse the effect - IE reconnect displays how I can stop it or a tool that will help me find out where it is firing from (motherboard/Windows/Intel/nVidia/USB monitor driver - goodness knows where). Grateful for a helping hand. F8 in various combinations are

I used to be able to build and run my console applications by hitting Ctrl + F5 in visual studio. This no longer works. I looked everywhere. Does anyone know how to re-enable this command? Might be a ridiculous suggestion but does your keyboard have some kind of "F Lock" key? Happened to me after I got a new keyboard and accidentally hit it. Didn't even know it was there :) Before you trash all your settings, consider just resetting the Keyboard preferences: In Tools / Options / Environment / Keyboard there's a drop-down for your Keyboard scheme and next to it a Reset button. Make sure the

This is not a duplicate of How to come out of while loop during debugging . See the comment on this answer https://stackoverflow.com/a/8107702/1391924 by the author of this question. While debugging, we can use short-cut keys like F8 to resume, F7 to step return, F5 to step into, F6 to step over. Is there any short-cut key to skip loops (for,while and do-while) while debugging Java code? In the picture shown below Currently debug cursor is at line no 57. Is there any short cut key when pressed it debug cursor should come out of innermost loop (for,while or do-while. Here while loop) and pause

When dealing with merge conflicts it is common that the >>>>>> and ====== inserted by DCVS are syntactically incorrect for the file I'm in and show up as highlighted in red. When dealing with merge conflicts it would be useful to have commands to jump to these error. When I type :cnext I just get the message "No Errors". These are Mercurial merge conflicts so I can't use Fugitive, but I generally prefer editing merge conflicts by hand anyway. Is there a way to jump to the next syntax error in the file? I think these errors are dictated by the syntax highlighting file. Nguyen You can use :lopen