luis changed the topic of #slime to: SLIME, the Superior Lisp Interaction Mode for Emacs | https://common-lisp.net/project/slime | https://irclog.tymoon.eu/freenode/%23slime | https://irclog.whitequark.org/slime
makomo has joined #slime
makomo has quit [Ping timeout: 240 seconds]
scymtym has quit [Remote host closed the connection]
luismbo[m] has quit [Remote host closed the connection]
moldybits has quit [Quit: WeeChat 2.4]
frgo has quit [Remote host closed the connection]
frgo has joined #slime
frgo has quit [Read error: No route to host]
edgar-rft has quit [Quit: Leaving]
sindan has joined #slime
<sindan> Sometimes I edit the slime buffer higher up and, I don't know how or why, when I come back down to write something, I get "Text is read-only" in the minibuffer. updatesually I undo my way out of it, but today I cannot get out of it. Is this a bug of slime? emacs? how do I write again in the slime buffer?
<sindan> s/updatesually/Usually/
moldybits has joined #slime
eggo has joined #slime
<eggo> /msg NickServ identify 1Suurtelekas
eggotest has joined #slime
eggo has quit [Read error: Connection reset by peer]
eggo has joined #slime
<eggo> /msg NickServ identify 1Suurtelekas
<eggo> /msg eggotest asd
<eggo> welp thats not working right
eggo has quit [Read error: Connection reset by peer]
eggotest has quit [Remote host closed the connection]
moldybits has quit [Quit: WeeChat 2.4]
frgo has joined #slime
makomo has joined #slime
makomo has quit [Client Quit]
frgo has quit [Ping timeout: 245 seconds]
makomo has joined #slime
luismbo[m] has joined #slime
makomo has quit [Quit: WeeChat 2.4]
luismbo[m] has quit [Ping timeout: 245 seconds]
luismbo[m] has joined #slime