Bug 11520 - Ctrl + Left/Right ignores non-alphanumeric characters
Summary: Ctrl + Left/Right ignores non-alphanumeric characters
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.0.3
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2013-04-02 12:29 UTC by chris
Modified: 2013-04-02 14:18 UTC (History)
1 user (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 chris 2013-04-02 12:29:18 UTC
In previous versions of MonoDevelop, Ctrl+Left/Right would stop before/after non-alphanumeric characters like {}();. etc.

The current version only stops after alphanumeric words.

e.g. for

      foreach (var item in foo.Bar())

In 4.0.3 Ctrl+Right only stops here (indicated by |)

      foreach| (var| item| in| foo|.Bar|())

I don't have an old version installed but if I compare this to Visual Studio's Ctrl+Right the cursor will be stopped before and after each word/symbol group:

      |foreach |(|var |item |in |foo|.|Bar|())|

Could the behavior be changed either to what it was before or to behave the same as in VS?
Comment 1 Mikayla Hutchinson [MSFT] 2013-04-02 14:06:04 UTC
Nothing changed, it uses native-style word boundaries, this is how word selection behaves on Mac.

You probably head it set to "sharpdevelop" (windows-style) word breaking in text editor preferences.
Comment 2 chris 2013-04-02 14:18:52 UTC
Ah, I found it, thank you! I was looking through the options but I missed this one.