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 for Bug 551 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The DeleteKey command is an old hack that added a hidden keybinding to the delete key, because at the time the Delete command caused an unexpected effect when triggered in some contexts (e.g. editing a filename in the solution pad).
It should be removed for several reasons:
* it's a hack, and in insufficiently undocumented
* it causes confusion for users - they see the Delete command isn't bound, and bind it to the Delete key, then get the same problems we were trying to prevent.
* it's no longer required, at least in the case mentioned in the comments - the command service was changed to special-case certain combinations (control-a, control-x etc) when the focus is in text entries. This should be fixed the same way.
Hhm, is there a reason why we didn't remove it that I'm missing? It seems to be actively referenced in Debugger (BreakpointPad, ObjectValueTreeView), but only for legacy reasons (?), since both would handle the Delete keys correctly without this command.
Plus: the command appears inside the global search results, which is wrong (but different issue)
@Lluis: any objectioons?