From: Jacob Lagares Pozo <jlagarespo@iebesalu.cat>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 40323@debbugs.gnu.org
Subject: bug#40323: 28.0.50; error in process filter: Invalid search bound (wrong side of point)
Date: Fri, 17 Apr 2020 16:13:25 +0200 [thread overview]
Message-ID: <73b0b37b-2ae9-f9c0-c673-4eaafe4ea61a@iebesalu.cat> (raw)
In-Reply-To: <87ftd22uz1.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
OK, not sure if this is what we want, but this is an example output that
looks interesting.
If needed I'll dump the whole thing to a file, compress, it and post it
here.
Many thanks,
Jacob
|======================================================================
1 -> (comint-output-filter #<process slack> "[04/17/20, 16:06:12:068]
info: [CHECK-FOR-OLD-IMS] (TAVFB00JW) Within limit: 4
")(:comint-pmark nil)
| 2 -> (set-marker #<marker at 238540 in *slack*<4>>
238595)(:comint-pmark #<marker at 238595 in *slack*<4>>)
| 2 <- set-marker: #<marker at 238595 in *slack*<4>>(:comint-pmark
#<marker at 238595 in *slack*<4>>)
| 2 -> (set-marker #<marker at 238595 in *slack*<4>>
238675)(:comint-pmark #<marker at 238595 in *slack*<4>>)
| 2 <- set-marker: #<marker at 238675 in *slack*<4>>(:comint-pmark
#<marker at 238675 in *slack*<4>>)
| 2 -> (ansi-color-process-output "[04/17/20, 16:06:12:068] info:
[CHECK-FOR-OLD-IMS] (TAVFB00JW) Within limit: 4
")(:comint-pmark #<marker at 238675 in *slack*<4>>)
| 2 <- ansi-color-process-output: nil(:comint-pmark #<marker at 238675
in *slack*<4>>)
| 2 -> (set-marker #<marker (moves after insertion) at 238675 in
*slack*<4>> 238675)(:comint-pmark #<marker at 238675 in *slack*<4>>)
| 2 <- set-marker: #<marker (moves after insertion) at 238675 in
*slack*<4>>(:comint-pmark #<marker at 238675 in *slack*<4>>)
1 <- comint-output-filter: #<marker (moves after insertion) at 238675 in
*slack*<4>>(:comint-pmark nil)
|
On 2020-04-17 13:49, Noam Postavsky wrote:
> Jacob Lagares Pozo <jlagarespo@iebesalu.cat> writes:
>
>> For brevity, I'll just post just a single one of them, because the
>> whole buffer is 172k characters and growing. I hope it's enough; if it
>> is not, please let me know and I'll post the whole thing.
> Please compress before posting. If you can find a spot where the
> comint-last-output-start goes from a large number to 1, I think that
> would probably be where the interesting part is.
[-- Attachment #2: Type: text/html, Size: 3044 bytes --]
next prev parent reply other threads:[~2020-04-17 14:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 11:04 bug#40323: 28.0.50; error in process filter: Invalid search bound (wrong side of point) Jacob Lagares Pozo
2020-03-30 14:50 ` Noam Postavsky
2020-03-30 15:25 ` Andreas Schwab
2020-03-30 15:49 ` Drew Adams
2020-03-31 23:00 ` Noam Postavsky
2020-04-15 2:25 ` Noam Postavsky
2020-04-17 11:39 ` Jacob Lagares Pozo
2020-04-17 11:43 ` Jacob Lagares Pozo
2020-04-17 11:49 ` Noam Postavsky
2020-04-17 14:13 ` Jacob Lagares Pozo [this message]
2020-04-19 12:57 ` Noam Postavsky
2020-04-20 10:07 ` Jacob Lagares Pozo
2020-04-21 2:29 ` Noam Postavsky
2020-05-05 12:01 ` Jacob Lagares Pozo
2020-05-05 17:33 ` Noam Postavsky
2020-05-12 11:11 ` Jacob Lagares Pozo
2020-05-13 1:21 ` Noam Postavsky
2020-05-15 11:06 ` Jacob Lagares Pozo
2020-05-15 15:45 ` Noam Postavsky
2020-05-16 11:50 ` Jacob Lagares Pozo
2020-05-20 1:29 ` Noam Postavsky
2022-04-23 13:03 ` Lars Ingebrigtsen
2022-05-22 11:27 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=73b0b37b-2ae9-f9c0-c673-4eaafe4ea61a@iebesalu.cat \
--to=jlagarespo@iebesalu.cat \
--cc=40323@debbugs.gnu.org \
--cc=npostavs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.