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

[Noam Postavsky]

Live System User <nyc4bos@aol.com> writes:

> Noam Postavsky <npostavs@users.sourceforge.net> writes:
>
>> 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:
>
> (defun term-handle-ansi-terminal-messages (message)
[...]
>           ((= command-code ?e)
>            (save-excursion
>             (find-file-other-window argument))

You have a missing paren here, is that a typo introduced when posting,
or is that what you ran?

And could you elaborate on the steps you take after that?  You said
something about an alias, but I couldn't tell if it's relevant or not.

>>
>>>         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.

So how many times do I do "it" until I should expect to see a failure?
10?  100?  1000?

And what is "it" exactly?

>>> 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?

It's referenced in term-emulate-terminal which is a process filter, so
it could be significant during output too.