<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Extend/Shrink Selection</title>
	<atom:link href="http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/</link>
	<description>ReSharper for productivity, dotTrace for performance, dotCover for test coverage</description>
	<pubDate>Mon, 13 Feb 2012 08:08:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Ted Jardine</title>
		<link>http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-267902</link>
		<dc:creator>Ted Jardine</dc:creator>
		<pubDate>Wed, 06 Feb 2008 19:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-267902</guid>
		<description>If like me your mapping has gotten all mixed up and resetting ReSharper keyboard shortcuts in just ReSharper options does little or nothing, try resetting key mappings in VS first (of course, all your customized mapping will be lost unless you restore etc.). Tools -&#62; Options -&#62; Environment -&#62; Keyboard -&#62; Then click reset on the applicable keyboard mapping scheme. Then go to ReSharper -&#62; Options -&#62; Environment -&#62; General -&#62; then restore ReSharper keyboard shortcuts.

</description>
		<content:encoded><![CDATA[<p>If like me your mapping has gotten all mixed up and resetting ReSharper keyboard shortcuts in just ReSharper options does little or nothing, try resetting key mappings in VS first (of course, all your customized mapping will be lost unless you restore etc.). Tools -&gt; Options -&gt; Environment -&gt; Keyboard -&gt; Then click reset on the applicable keyboard mapping scheme. Then go to ReSharper -&gt; Options -&gt; Environment -&gt; General -&gt; then restore ReSharper keyboard shortcuts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Jardine</title>
		<link>http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-267248</link>
		<dc:creator>Ted Jardine</dc:creator>
		<pubDate>Fri, 01 Feb 2008 23:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-267248</guid>
		<description>Argh. I'd love to use this shortcut, but it continues to wait for the second key of the chord. I have made sure that this specific shortcut has not been overwritten by restoring ReSharper keyboard shortcuts and still no go. Moreover, the VS ctrl-alt-right arrow shortcut doesn't work and the Resharper -&#62; Code -&#62; Extend Selection does not have the ctrl-w shortcut description next to it while the shrink selection (ctrl-shift-w) does (and does work).

Am I missing something completely obvious here?</description>
		<content:encoded><![CDATA[<p>Argh. I&#8217;d love to use this shortcut, but it continues to wait for the second key of the chord. I have made sure that this specific shortcut has not been overwritten by restoring ReSharper keyboard shortcuts and still no go. Moreover, the VS ctrl-alt-right arrow shortcut doesn&#8217;t work and the Resharper -&gt; Code -&gt; Extend Selection does not have the ctrl-w shortcut description next to it while the shrink selection (ctrl-shift-w) does (and does work).</p>
<p>Am I missing something completely obvious here?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jura Gorohovsky</title>
		<link>http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-266939</link>
		<dc:creator>Jura Gorohovsky</dc:creator>
		<pubDate>Tue, 29 Jan 2008 16:36:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-266939</guid>
		<description>Hi Joe,
No, selecting a subword is certainly followed by selecting the whole containing word.
That was my fault, ambiguous wording. Thanks for taking note!</description>
		<content:encoded><![CDATA[<p>Hi Joe,<br />
No, selecting a subword is certainly followed by selecting the whole containing word.<br />
That was my fault, ambiguous wording. Thanks for taking note!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe White</title>
		<link>http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-266936</link>
		<dc:creator>Joe White</dc:creator>
		<pubDate>Tue, 29 Jan 2008 16:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-266936</guid>
		<description>So if you have the CamelHumps option turned on, Ctrl+W once will select a single sub-word, but the second time will select the larger expression that the word is in? I would've expected the second time to move up to the word -- i.e., to have the option add one more step to the beginning of the sequence, without actually removing any functionality.</description>
		<content:encoded><![CDATA[<p>So if you have the CamelHumps option turned on, Ctrl+W once will select a single sub-word, but the second time will select the larger expression that the word is in? I would&#8217;ve expected the second time to move up to the word &#8212; i.e., to have the option add one more step to the beginning of the sequence, without actually removing any functionality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jura Gorohovsky</title>
		<link>http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-266818</link>
		<dc:creator>Jura Gorohovsky</dc:creator>
		<pubDate>Mon, 28 Jan 2008 10:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-266818</guid>
		<description>Hi Paulius,
ReSharper provides four actions for using CamelHumps locally when the corresponding global option is switched off:
ReSharper_HumpNext - move caret to next hump/word
ReSharper_HumpPrev - move caret to previous hump/word
ReSharper_HumpNextExtend - expand selection to next hump
ReSharper_HumpPrevExtend - expand selection to previous hump
Of course, you can assign to them whatever shortcuts you feel appropriate in VS Tools &#62; Options &#62; Environment&#62; Keyboard
Note that both HumpNextExtend and HumpPrevExtend only work in a linear fashion, without additional functionality of Extend/Shrink Selection
Hope that helps.</description>
		<content:encoded><![CDATA[<p>Hi Paulius,<br />
ReSharper provides four actions for using CamelHumps locally when the corresponding global option is switched off:<br />
ReSharper_HumpNext - move caret to next hump/word<br />
ReSharper_HumpPrev - move caret to previous hump/word<br />
ReSharper_HumpNextExtend - expand selection to next hump<br />
ReSharper_HumpPrevExtend - expand selection to previous hump<br />
Of course, you can assign to them whatever shortcuts you feel appropriate in VS Tools &gt; Options &gt; Environment&gt; Keyboard<br />
Note that both HumpNextExtend and HumpPrevExtend only work in a linear fashion, without additional functionality of Extend/Shrink Selection<br />
Hope that helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paulius</title>
		<link>http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-266633</link>
		<dc:creator>Paulius</dc:creator>
		<pubDate>Sat, 26 Jan 2008 08:15:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/dotnet/2008/01/extendshrink-selection/#comment-266633</guid>
		<description>Hi,
could we have CamelHumps not as turn on/off feature but as a separate shortcut? Or at least it could be turned on/off with a shortcut. It's rather useful actually (CamelHumps), but it's like 30/70 for me, where I would use 30% for selection with CamelHumps and 70% without it, so currently it does not justify turning it on every time it is needed for a short period of time..
thanks</description>
		<content:encoded><![CDATA[<p>Hi,<br />
could we have CamelHumps not as turn on/off feature but as a separate shortcut? Or at least it could be turned on/off with a shortcut. It&#8217;s rather useful actually (CamelHumps), but it&#8217;s like 30/70 for me, where I would use 30% for selection with CamelHumps and 70% without it, so currently it does not justify turning it on every time it is needed for a short period of time..<br />
thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>

