======================================================================
1 -> (comint-output-filter #<process Shell>
"Initializing local storage instance at path:
/home/sheep/.co\
nfig/Slack/local-settings.json
")(:comint-pmark
nil)
| 2 -> (set-marker #<marker in no buffer>
1)(:comint-pmark nil)
| 2 <- set-marker: #<marker at 1 in *Async Shell
Command*>(:comint-pmark (#<marker at 1 in *Async
Shell C\
ommand*> . #<marker at 1 in *Async Shell
Command*>))
| 2 -> (set-marker #<marker at 1 in *Async Shell
Command*> 92)(:comint-pmark (#<marker at 1 in *Async
She\
ll Command*> . #<marker at 1 in *Async Shell
Command*>))
| 2 <- set-marker: #<marker at 92 in *Async Shell
Command*>(:comint-pmark (#<marker at 1 in *Async
Shell \
Command*> . #<marker at 92 in *Async Shell
Command*>))
| 2 -> (ansi-color-process-output "Initializing
local storage instance at path: /home/sheep/.config/Slack\
/local-settings.json
")(:comint-pmark (#<marker at 1 in *Async Shell
Command*> . #<marker at 92 in *Async Shell
Command*>))
| 2 <- ansi-color-process-output: #<marker in no
buffer>(:comint-pmark (#<marker at 1 in *Async Shell
Com\
mand*> . #<marker at 92 in *Async Shell
Command*>))
| 2 -> (comint-adjust-window-point #<window 8 on
*Async Shell Command*> #<process
Shell>)(:comint-pmark (\
#<marker at 1 in *Async Shell Command*> .
#<marker at 92 in *Async Shell
Command*>))
| 2 <- comint-adjust-window-point: nil(:comint-pmark
(#<marker at 1 in *Async Shell Command*> .
#<marker \
at 92 in *Async Shell
Command*>))
| 2 -> (set-marker #<marker (moves after insertion)
at 92 in *Async Shell Command*> 92)(:comint-pmark
(#<\
marker at 1 in *Async Shell Command*> . #<marker at
92 in *Async Shell Command*>))
| 2 <- set-marker: #<marker (moves after insertion)
at 92 in *Async Shell Command*>(:comint-pmark
(#<mark\
er at 1 in *Async Shell Command*> . #<marker at 92
in *Async Shell Command*>))
1 <- comint-output-filter: #<marker (moves after
insertion) at 92 in *Async Shell Command*>(:comint-pmark\
nil)
This is on master, I can't seem to reproduce the bug, with or without the patch. This is getting progressively weirder; I remember perfectly how I launched just about anything and the error would start triggering immediately and it was super annoying.
All the packages are still the same. I am doing all the tests on
Slack because it is the one I remembered that would trigger it
more often. I have no clue what could be different this time
around.
Jacob Lagares Pozo <jlagarespo@iebesalu.cat> writes:Should I install the newer version with another prefix and try to reproduce it there?Yes please.