Bug 437 - Can't use emacs keys to navigate when autocomplete boxes are popped up
Summary: Can't use emacs keys to navigate when autocomplete boxes are popped up
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 2.8 Alpha 2
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-08-25 14:32 UTC by Nat Friedman
Modified: 2011-08-29 10:16 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Nat Friedman 2011-08-25 14:32:25 UTC
Comment 1 Mike Krüger 2011-08-26 10:31:34 UTC
Comment 2 Mikayla Hutchinson [MSFT] 2011-08-26 13:24:24 UTC
Reopened because the fix was flawed:
* It makes the completion window close. The window should only close if the command causes the caret to move outside of the completion word.
* It allows keystrokes with the control modifier and an alphanumeric key to fall through on all platforms, which is inconsistent - if we allow control on windows/linux, we should allow command on mac - and doesn't allow alt, allows, punctuation and F1-F12.
Comment 3 Mike Krüger 2011-08-29 10:16:39 UTC
The close behaviour is in line with the caret behaviour.

This bug is very specific to the built in keys, when other keys are hacked into the text editor we should change it, yes. But most actions should be done by the command manager and these keys are working.

The close behaviour needs to be addressed, but is unrelated to that bug.