Re: "Connection broken" message appearing in odd places in buffers

[Lars Magne Ingebrigtsen]

Lars Magne Ingebrigtsen <address@hidden> writes:

> This seems like a bug to me, I think, but I thought I'd ask here first
> if anybody knows what this is about.

It's this code in status_notify that's the culprit:

              /* Insert new output into buffer
                 at the current end-of-output marker,
                 thus preserving logical ordering of input and output.  */
              if (XMARKER (p->mark)->buffer)
                Fgoto_char (p->mark);
              else
                SET_PT_BOTH (ZV, ZV_BYTE);

And if I added a trace to output the process-mark throughout the
conversation, I get this:

Mark: #<marker at 363 in *trace of SMTP session to hermes.netfonds.no*>
235 Authentication succeeded
Mark: #<marker at 363 in *trace of SMTP session to hermes.netfonds.no*>
250 OK
Mark: #<marker at 363 in *trace of SMTP session to hermes.netfonds.no*>
250 Accepted
Mark: #<marker at 363 in *trace of SMTP session to hermes.netfonds.no*>
354 Enter message, ending with "." on a line by itself
Sending email...done
Mark: #<marker at 363 in *trace of SMTP session to hermes.netfonds.no*>
250 OK id=1R3xha-0001tb-Ic
Mark: #<marker at 363 in *trace of SMTP session to hermes.netfonds.no*>

So the process-mark stays at character 363, and that's where it outputs
the message.  So the question is, I guess -- why doesn't the marker
increase?  Because the output from the process gets inserted at the end
of the buffer.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/