Jump to content
  • Advertisement
  • entries
  • comments
  • views


Sign in to follow this  


I am thoroughly PISSED THE HELL OFF right now.

One of my favorite text editor options in old versions of Visual Studio was "Go to selection anchor after pressing escape." If you never experienced the blissful joy of this, here's what it did:

- Open some long code file
- Hold Shift
- Accidentally press PGUP instead of HOME, or PGDN instead of END
- Oh shit! Now my selection is all fucked and I lost my editing position!
- But wait, all we have to do is press ESC and we're right back where we were, like nothing happened!

This is FUCKING BEAUTIFUL for someone who types fast and makes a lot of mistakes with hitting keys (like me) due to using a lot of different keyboards during the course of a given work week.


I didn't realize how much I missed it until I made the same mistake four times in a row today. In a fit of anger I started looking for ways to force the option to activate.

Here's the fucking stupid part. Look in the Visual Studio infrastructure documentation for a property called GoToAnchorAfterEscape. This property EXISTS in 2012 and is DOCUMENTED. (For the irony of this, look up the docs on Google or whatever. I'll wait.)

Want to know something even more fucking retarded?

If you modify your .vssettings file to set this to True, or try and import another .vssettings file with this property set to True, or generally make any attempt whatsoever to set this to True, VISUAL STUDIO FUCKING ERASES YOUR SETTINGS ENTIRELY. Doesn't error, doesn't quietly fail, IT FUCKING DESTROYS ALL OF YOUR PREFERENCES.

Considering I live near Redmond, some stupid FUCK needs to watch his back for a while, because I swear to every deity ever invented that if I find out who made this decision I will feed him his own fucking testicles.
Sign in to follow this  


Recommended Comments

I sense a certain bitterness in thy words.


No matter how small a feature, someone out there is relying on it :)

Share this comment

Link to comment

Yeah, Microsoft isn't quite right recently in chopping good features in their software.  It would be interesting to see what is happening behind the scenes in their corporate culture to allow these kinds of blunders, unless the features will reappear later for some unknown reason.  It is very strange and disappointing to say the least.

Share this comment

Link to comment

We need the Bill Gates Review back. First Windows 8, now this!

Share this comment

Link to comment
Can't you just press the left/right arrow key to deselect and jump to the start/end of the selection respectively? Also I tried this in VS2012 and pressing ESC deselected it just as you described.

Share this comment

Link to comment

Yeah, the arrow keys work, but they're not in my muscle memory yet. I still don't understand why the feature was neutered.


Pressing ESC [i]does[/i] deselect text, but it moves you to the wrong end of the selection, i.e. where the cursor stopped, not where selection began (the anchor point).

Share this comment

Link to comment

You've only scratched the surface of VS's failings. "Sucks" is an understatement. I did a demo build with VS2012 a couple months ago, after a few years of Linux bliss. I thought Linux was crappy, and in many ways it still is, but it's 1000% better than this BS.

Share this comment

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!