bug#28687: 25.2; Error using term-handle-ansi-terminal-messages

[Live System User]

Noam Postavsky <npostavs@users.sourceforge.net> writes:

> tags 28687 + unreproducible moreinfo
> quit
>
> Live System User <nyc4bos@aol.com> writes:
>
>>         When trying to use `term-handle-ansi-terminal-messages`
>>         as a template, a new command code is defined:
>
> Do you mean you have defined some new function?  Please post a complete
> example, not just fragments.

  No: I justed added those lines to the existing
  `term-handle-ansi-terminal-messages`function:

term-ansi.el
Description: term-handle-ansi-terminal-messages addition

>
>>         Most of the time thi works.
>>         
>>         When it doesn't work as expected,
>
> How often does it fail?

  Enough to notice buy no enough to notice a pattern.
  
>
>>            1. I get the error:
>> 
>>               if: Symbol’s value as variable is void:
>>               term-pending-delete-marker
>> 
>> Debugger entered--Lisp error: (void-variable term-pending-delete-marker)
>>   term-emulate-terminal(#<process test> "\nAnSiTe test\nAnSiTu 
>> liveuser\nAnSiTc /home/liveuser\nAnSiTh localhost.localdomain\n")
>> 
>
> Seems like you might be running in the wrong buffer.
> term-pending-delete-marker is only defined buffer-locally.

  Since I use `find-file-other-window`, i.e. another buffer,
  why don't I get that error every time that ANSI code is
  processed instead of only occasionally?

  When does `term-pending-delete-marker`kick in?

  Shouldn't it only be a factor as I am typing chacaters and/or
  interacting with the ansi-term?

  Thanks.