00:10 <luis> sindan: what's "the slime buffer"?

00:13 <luis> sindan: do you mean the REPL? If so, you could close it then reopen it with M-x slime-repl

00:14 <luis> (by close I mean M-x kill-buffer)

06:27 <sindan> luis, I could always do that but I don't want to lose the contents of the buffer.

06:28 <sindan> I solved it as always, by undoing until the point is no longer on a read-only region

06:31 <sindan> The point of my question is: how did it end up in this state? It has happened to other people (stackoverflow etc) and the solutions involve a cross-emacs/slime panoply of suggestions.

06:32 <sindan> I want to know why does this happen and how to fix it consistently.

06:34 <sindan> In principle, if some of slime-repl has read-only properties scattered over it (I'd say at the prompt text), then I shouldn't be able to either delete that text (which I can't) or delete invisible text properties (which apparently I can) to end up in some unexpected text-only state.

07:32 <luis> sindan: the first step is to come up with a recipe for reproducing the error.

11:50 <sindan> luis, isn't that what I just said with "why does this happen"? Do you think you have to teach anyone on #slime to fucking debug? If you have nothing else to contribute than platitudes, you better shut up.

11:52 <sindan> If I knew hot to reproduce the situation (not an "error"), I wouldn't be asking why does this happen. Try not to "help" me in this stupid way.

11:56 <Shinmera> Calm down, jesus.

12:07 <edgar-rft> not you, malm :-)

19:47 <luis> sindan: I don't know you, so I have no idea what kind of hints/pointers you need. All I know right now is that you're extremely rude.

19:48 <luis> And you're running into a problem that neither of us know how to reproduce.