Here is an example output from Slack, even though weirdly enough nothing seemed to trigger the error: |======================================================================
1 -> (comint-output-filter #<process Shell> "[05/12/20, 13:06:14:636] info: [DESKTOP-SIDE-EFFECT] Update from desktop for keys  [\"settings\"] 
")(:comint-pmark nil)
| 2 -> (set-marker #<marker at 37370 in *Async Shell Command*> 37469)(:comint-pmark (#<marker at 37370 in *Async Shell Command*> . #<marker at 37469 in *Async Shell Command*>))
| 2 <- set-marker: #<marker at 37469 in *Async Shell Command*>(:comint-pmark (#<marker at 37469 in *Async Shell Command*> . #<marker at 37469 in *Async Shell Command*>))
| 2 -> (set-marker #<marker at 37469 in *Async Shell Command*> 37566)(:comint-pmark (#<marker at 37469 in *Async Shell Command*> . #<marker at 37469 in *Async Shell Command*>))
| 2 <- set-marker: #<marker at 37566 in *Async Shell Command*>(:comint-pmark (#<marker at 37469 in *Async Shell Command*> . #<marker at 37566 in *Async Shell Command*>))
| 2 -> (ansi-color-process-output "[05/12/20, 13:06:14:636] info: [DESKTOP-SIDE-EFFECT] Update from desktop for keys  [\"settings\"] 
")(:comint-pmark (#<marker at 37469 in *Async Shell Command*> . #<marker at 37566 in *Async Shell Command*>))
| 2 <- ansi-color-process-output: nil(:comint-pmark (#<marker at 37469 in *Async Shell Command*> . #<marker at 37566 in *Async Shell Command*>))
| 2 -> (set-marker #<marker (moves after insertion) at 37566 in *Async Shell Command*> 37566)(:comint-pmark (#<marker at 37469 in *Async Shell Command*> . #<marker at 37566 in *Async Shell Command*>))
| 2 <- set-marker: #<marker (moves after insertion) at 37566 in *Async Shell Command*>(:comint-pmark (#<marker at 37469 in *Async Shell Command*> . #<marker at 37566 in *Async Shell Command*>))
1 <- comint-output-filter: #<marker (moves after insertion) at 37566 in *Async Shell Command*>(:comint-pmark nil)
| Because I am on the testing branch of Debian, is there any chance Emacs got updated and this bug fixed? On 05/05/2020 19:33, Noam Postavsky wrote: > Jacob Lagares Pozo writes: > >> If I run it without your patches, it works surprisingly just fine (I >> noticed the original errors pop up most commonly on Slack I guess >> because it prints a lot more?), whereas if I evaluate said patches, >> this is the output of the trace buffer: > I don't see anything unexpected in the trace either. > >> I am not sure what does this mean, perhaps it is some special >> character Slack uses for logging that messes with those markers, I >> don't know. Maybe I could try printing all of the ASCII characters >> sequentially and see what happens. > Well, ideally we would want a trace from something that does trigger the > error. > >> Regardless, I'm still not entirely sure what your code is doing anyway. > It's basically just printing out the values of the markers, so we might > hopefully notice when they get changed in an unexpected way.