Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
MonoDevelop on Mac OSX - doesn't seem possible to get to the "Resolve -> using <namespace>" command via the keyboard. Always need to reach for the mouse which is really annoying. A short cut key for the context menu would be great.
Chris, what is the keybinding that you suggest we use?
That particular command is accessible via the "quick fix" command, already bound as Alt-enter.
Regarding a command for opening the context menu, that seems to be something that no-one does on Mac, unlike Windows where there's a dedicated key supported by the GUI toolkit.
Opening the context menu is so you can pick a different Resolve if it matches more than one item?
I tried using Alt + Enter for the "quick fix" command (and checked it is bound to that keybinding which it is but nothing happens (see http://screencast.com/t/JhupOeQLxN9 ).
Probably a regression, the 'quick fix' command was made more generic with the new resolver, so it probably wasn't restored after that work was moved into the 'newresolver' branch. I think a couple of other commands (e.g. move class to file) are also affected.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This was fixed long ago.