Bug 4951 - Allow editing virtual indents
Summary: Allow editing virtual indents
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-05-08 16:26 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-05-09 03:05 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Mikayla Hutchinson [MSFT] 2012-05-08 16:26:54 UTC
It should be possible to edit the virtual indent e.g. tab or backspace should add/remove a tab.

I don't know whether it would be best if they caused it to become "real" and edited the real whitespace, or temporarily edited the virtual indent.

This is important for correcting the virtual indent when it's wrong. Currently tab/backspace clear the indent completely to the beginning of the line, which is annoying and leads to a lot of extra typing of tabs.
Comment 1 Mike Krüger 2012-05-09 03:05:29 UTC
fixed

The tab was a bug - I don't know when it's got introduced or if it's there for a long time :(.

The backspace was meant to work this way, but VS.NET does it differently. Now we behave like they do in this area.