Don't check for continuation if we're executing a CUSTOMREQUEST

[ehlertjd]

Closes #486

[captain-caveman2k]

The fix seems simple enough.

Unfortunately I'm not near any of my Linux boxes at the moment so I was wondering do the Imap tests still run with this fix?

[bagder]

I was wondering do the Imap tests still run with this fix?

The travis-CI tests says all OK here, so I would say yes they do! =)

[ehlertjd]

I can also verify that they passed on my test system:

uname -a

Linux build-test 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

On Tue, Oct 13, 2015 at 2:32 PM, Daniel Stenberg notifications@github.com
wrote:

I was wondering do the Imap tests still run with this fix?

The travis-CI tests says all OK here, so I would say yes they do! =)

—
Reply to this email directly or view it on GitHub
#487 (comment).

[captain-caveman2k]

@bagder Cool - as I've been away from the project for a bit I couldn't remember if Travis-CI ran the test suit or not :-/

@ehlertjd Are you able to generate a custom request test as well. Again I can't remember if I wrote one when we added custom request support :-(

[ehlertjd]

I'll take a look to see what's out there and get back.

On Tue, Oct 13, 2015 at 2:39 PM, Steve Holme notifications@github.com
wrote:

@bagder https://github.com/bagder Cool - as I've been away from the
project for a but I couldn't remember if Travis-CI ran the test suit or not
:-/

@ehlertjd https://github.com/ehlertjd Are you able to generate a custom
request test as well. Again I can't remember if I wrote one when we added
custom request support :-(

—
Reply to this email directly or view it on GitHub
#487 (comment).

[ehlertjd]

I added a test (#841) that demonstrates the issue (in prior branches) and that the issue is fixed here. I also verified that there are a 11 other CUSTOMREQUEST tests in the IMAP suite. PR is pending Travis-CI validation.