From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: 66738@debbugs.gnu.org
Subject: bug#66738: 30.0.50; Gud LLDB regressions
Date: Wed, 25 Oct 2023 11:06:02 +0200 [thread overview]
Message-ID: <m2v8av137p.fsf@Pro.fritz.box> (raw)
In-Reply-To: <1985D138-4723-4744-A1C5-1DC1057AEB4B@gmail.com> ("Mattias Engdegård"'s message of "Wed, 25 Oct 2023 10:32:10 +0200")
Mattias Engdegård <mattias.engdegard@gmail.com> writes:
>> 1. M-x lldb RET leads to errors. *Messages* contains:
>>
>> error in process filter: gud-marker-filter: Text is read-only
>> error in process filter: Text is read-only
>
> Sorry, I don't observe this myself.
Turns out it's comint-prompt-read-only, but...
>
>> I think this can also be seen
>> when binding inhibit-read-only around the delete-region.
>
> That sounds strange. Did you bind inhibit-read-only to `t`? That should have overridden any text protection.
> Unless I can reproduce it, I'm afraid you are left with the task to
> debug it.
...I'll fix this myself, thank you.
Yeah, I did that. But it seems I have misinterpreted what the intention
of the delete-region is. (I'm kind of refusing to read the partial
terminal enumlator part of the code :-).
>
>> 2. Nitpick: when extracting the file name in the filter function, with
>>
>> (group (+ (not (in "\n\r")))) ; 3: file
>>
>> this means that file names cannot contain LF and CR, which they actually
>> can.
>
> And that is a possibility that I'm going to ignore unless it's
> actually a security problem (and I don't think it is). File names
> containing control characters on purpose are excessively rare in Unix
> systems and disallowed on Windows (at least 0-31).
Then let me ask differently: why did you change this in the first place?
next prev parent reply other threads:[~2023-10-25 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 4:24 bug#66738: 30.0.50; Gud LLDB regressions Gerd Möllmann
2023-10-25 8:32 ` Mattias Engdegård
2023-10-25 9:06 ` Gerd Möllmann [this message]
2023-10-25 9:40 ` Mattias Engdegård
2023-10-25 14:02 ` Gerd Möllmann
2023-10-25 14:23 ` Mattias Engdegård
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=m2v8av137p.fsf@Pro.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=66738@debbugs.gnu.org \
--cc=mattias.engdegard@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.