7 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

Here is the approach that has been proven to work pretty well for me. 11, 2

As soon as I sense that Oh, but, now there's another problem I reply with comment like this:

Looks like <refer to original problem> is solved isn't it? As for <refer to "next" problem>, that would be a different question, consider posting it separately.

For easy copy-n-paste.

Looks like &lt;refer to original problem&gt; is solved isn't it? As for &lt;refer to "next" problem&gt;, that would be a **[different question](https://meta.stackexchange.com/questions/43478/exit-strategies-for-chameleon-questions "at Stack Exchange sites, “chameleon questions” are not quite welcome")**, consider posting it separately.

Interesting that above approach "utilizes" your question to deal with the kind of issues you're asking about. Feels pretty meta.

Here is the approach that has been proven to work pretty well for me. 1, 2

As soon as I sense that Oh, but, now there's another problem I reply with comment like this:

Looks like <refer to original problem> is solved isn't it? As for <refer to "next" problem>, that would be a different question, consider posting it separately.

For easy copy-n-paste.

Looks like &lt;refer to original problem&gt; is solved isn't it? As for &lt;refer to "next" problem&gt;, that would be a **[different question](https://meta.stackexchange.com/questions/43478/exit-strategies-for-chameleon-questions "at Stack Exchange sites, “chameleon questions” are not quite welcome")**, consider posting it separately.

Interesting that above approach "utilizes" your question to deal with the kind of issues you're asking about. Feels pretty meta.

Here is the approach that has been proven to work pretty well for me. 1, 2

As soon as I sense that Oh, but, now there's another problem I reply with comment like this:

Looks like <refer to original problem> is solved isn't it? As for <refer to "next" problem>, that would be a different question, consider posting it separately.

For easy copy-n-paste.

Looks like &lt;refer to original problem&gt; is solved isn't it? As for &lt;refer to "next" problem&gt;, that would be a **[different question](https://meta.stackexchange.com/questions/43478/exit-strategies-for-chameleon-questions "at Stack Exchange sites, “chameleon questions” are not quite welcome")**, consider posting it separately.

Interesting that above approach "utilizes" your question to deal with the kind of issues you're asking about. Feels pretty meta.

6 replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
source | link

Here is the approach that has been proven to work pretty well for me. 1, 22

As soon as I sense that Oh, but, now there's another problem I reply with comment like this:

Looks like <refer to original problem> is solved isn't it? As for <refer to "next" problem>, that would be a different question, consider posting it separately.

For easy copy-n-paste.

Looks like &lt;refer to original problem&gt; is solved isn't it? As for &lt;refer to "next" problem&gt;, that would be a **[different question](https://meta.stackexchange.com/questions/43478/exit-strategies-for-chameleon-questions "at Stack Exchange sites, “chameleon questions” are not quite welcome")**, consider posting it separately.

Interesting that above approach "utilizes" your question to deal with the kind of issues you're asking about. Feels pretty meta.

Here is the approach that has been proven to work pretty well for me. 1, 2

As soon as I sense that Oh, but, now there's another problem I reply with comment like this:

Looks like <refer to original problem> is solved isn't it? As for <refer to "next" problem>, that would be a different question, consider posting it separately.

For easy copy-n-paste.

Looks like &lt;refer to original problem&gt; is solved isn't it? As for &lt;refer to "next" problem&gt;, that would be a **[different question](https://meta.stackexchange.com/questions/43478/exit-strategies-for-chameleon-questions "at Stack Exchange sites, “chameleon questions” are not quite welcome")**, consider posting it separately.

Interesting that above approach "utilizes" your question to deal with the kind of issues you're asking about. Feels pretty meta.

Here is the approach that has been proven to work pretty well for me. 1, 2

As soon as I sense that Oh, but, now there's another problem I reply with comment like this:

Looks like <refer to original problem> is solved isn't it? As for <refer to "next" problem>, that would be a different question, consider posting it separately.

For easy copy-n-paste.

Looks like &lt;refer to original problem&gt; is solved isn't it? As for &lt;refer to "next" problem&gt;, that would be a **[different question](https://meta.stackexchange.com/questions/43478/exit-strategies-for-chameleon-questions "at Stack Exchange sites, “chameleon questions” are not quite welcome")**, consider posting it separately.

Interesting that above approach "utilizes" your question to deal with the kind of issues you're asking about. Feels pretty meta.

5 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

Here is the approach that has been proven to work pretty well for me. 1, 2

As soon as I sense that Oh, but, now there's another problem I reply with comment like this:

Looks like <refer to original problem> is solved isn't it? As for <refer to "next" problem>, that would be a different questiondifferent question, consider posting it separately.

For easy copy-n-paste.

Looks like &lt;refer to original problem&gt; is solved isn't it? As for &lt;refer to "next" problem&gt;, that would be a **[different question](httphttps://meta.stackexchange.com/questions/43478/exit-strategies-for-chameleon-questions "at Stack Exchange sites, “chameleon questions” are not quite welcome")**, consider posting it separately.

Interesting that above approach "utilizes" your question to deal with the kind of issues you're asking about. Feels pretty meta.

Here is the approach that has been proven to work pretty well for me. 1, 2

As soon as I sense that Oh, but, now there's another problem I reply with comment like this:

Looks like <refer to original problem> is solved isn't it? As for <refer to "next" problem>, that would be a different question, consider posting it separately.

For easy copy-n-paste.

Looks like &lt;refer to original problem&gt; is solved isn't it? As for &lt;refer to "next" problem&gt;, that would be a **[different question](http://meta.stackexchange.com/questions/43478/exit-strategies-for-chameleon-questions "at Stack Exchange sites, “chameleon questions” are not quite welcome")**, consider posting it separately.

Interesting that above approach "utilizes" your question to deal with the kind of issues you're asking about. Feels pretty meta.

Here is the approach that has been proven to work pretty well for me. 1, 2

As soon as I sense that Oh, but, now there's another problem I reply with comment like this:

Looks like <refer to original problem> is solved isn't it? As for <refer to "next" problem>, that would be a different question, consider posting it separately.

For easy copy-n-paste.

Looks like &lt;refer to original problem&gt; is solved isn't it? As for &lt;refer to "next" problem&gt;, that would be a **[different question](https://meta.stackexchange.com/questions/43478/exit-strategies-for-chameleon-questions "at Stack Exchange sites, “chameleon questions” are not quite welcome")**, consider posting it separately.

Interesting that above approach "utilizes" your question to deal with the kind of issues you're asking about. Feels pretty meta.

4 added 370 characters in body
source | link
3 Migration of MSO links to MSE links
source | link
2 fixed typo // discovered while copying canned message for quoting :)
source | link
1
source | link