Re: nnimap with openssl stopping up after connecting in Windows

[Steinar Bang <sb@dod.no>]

>>>>> Steinar Bang <sb@dod.no>:

>> So I guess the right thing to do here, is to make sure there is no form
>> of end-of-line translation going on in the nnimap buffer.

>> I wonder what the correct approach here, is?
>> (set-buffer-process-coding-system 'undecided 'undecided)

> So I guess set-buffer-file-coding-system is the one to try next... 

That didn't work either.

But perhaps I did the wrong thing by piggy-backing on the
imap-disable-multibyte function?

Perhaps the only place to set the coding system, are in the two calls to
the imap-disable-multibyte function that aren't applied to the
imap-log-buffer?  I.e. the two calls to imap-disable-multibyte that are
inside the imap-open function?

And perhaps the calls should be to set-buffer-process-coding-system?

I think I will try to create a new inline function that sets the buffer
process coding system to undecided both for outgoing and incoming, and
call that from the two places in imap-open that imap-disable-multibyte
is called from.

(I'm waving around blindly here, as readers of this articles may have
guessed.  Any assistance from anyone who can tell what actually makes
sense would be appreciated)