Bulletin board for consort on #clatter
Vote on phrases with !vote, !vote -N, or !vote index. Add quotes with !addquote.
🗳 Top-voted phrases
| # | Votes | Phrase | Trigger |
|---|---|---|---|
| 2 | 1 | I'm still in the nick list for asteroid | I'm still in the UK. Working from home but it's honestly so quiet. I've been spending most of my time coding. So it's been great for my personal projects. Did you check our my blog post? |
| 1 | 1 | I will filter the people with a header using CLabber including unicode and stop them getting weird symbols instead of emojis/icons | I will filter the people with a header using CLabber including unicode and stop them getting weird though the pipeline is looking rough |
| 134 | 0 | you can switch that | you can change the clatter-track-count face as well, if you want to make it smaller or different color |
| 133 | 0 | interesting it happens every time I run the command I actually use 'newest-first but I think in our case we need to set that up - the other modes all work fine. We can have your client suddenly join. | interesting |
| 132 | 0 | I think soju disconnected | I think it's in some sense a me problem, since it occurred before the command existed |
| 131 | 0 | otoh, I guess I wouldn't know without a second track mode line indicator is too long and should be less annoying now. | otoh, I guess I wouldn't know without a second client running in parallel? |
| 130 | 0 | you can add it again | you can open it up and request it yourself though |
| 129 | 0 | right now | right |
| 128 | 0 | and the nick colors work nicely with light themes now. | and the other client (which got the messages) was connected the whole time |
| 127 | 0 | ah, maybe that's just a specific buffer was not created | ah, maybe that's the issue. It's playback on client re-connect |
| 126 | 0 | bremner: test it out yesterday and I like goguma though, it's simon ser, the same result. | bremner: test it out (all 10 fingers) |
| 125 | 0 | lol true. my mode-line seems quite bare now that i duplicated PR #76 with PR #93 | lol |
| 124 | 0 | anyone have requests before i implemented :bouncer , cause it would be good! | anyone have requests before i head out? |
| 123 | 0 | the topic could go in the nick list for asteroid | the topic could go in the buffer header line rather than the mode line. the mode line is pretty cramped with the buffer name |
| 122 | 0 | re: previous /part detach conversation, I want or the server buffer? | re: previous /part detach conversation, I want killing buffers to detach by default rather than parting entirely (which I’m fine with doing explicitly since it’s rare for me). I advised clatter-irc-part with (funcall fn channel (or message "detach")), but exposing a clatter-default-part-reason might make sense |
| 121 | 0 | never used customize-themes | never used that...i have a custom function that just loads N messages |
| 120 | 0 | ok it must be from me in channel. | ok it must be passing it to the child |
| 119 | 0 | I know it's good | I know nothing about IRC but I would have thought connecting to upstream networks would be handled entirely by the bouncer |
| 118 | 0 | yeah it seemed to work. | yeah it seems like clatter-soju.el should be handling this correctly, idk |
| 117 | 0 | > The OFTC child | > The OFTC network is relatively popular, and currently does not provide SASL support. This is why chat.sr.ht does not prompt the user for SASL-based login details when connecting to it. |
| 116 | 0 | I think the advantage you have a split doesn't clear the track in mode-line. | I think I need to disable sasl but just for the oftc child |
| 115 | 0 | I use the palette of your servers | I use chat.sr.ht (normally via the web interface) and am in quite a few channels. Is it possible to configure clatter to only open channel buffers on demand? I remember when I set up ERC it created buffers for every single channel and that seemed like it would be an issue with long-running emacs sessions |
| 114 | 0 | hrm. Maybe I didn't try it out :) | hrm. Maybe I need to restart emacs |
| 113 | 0 | "Do not request ‘NAMES’ for each frame if at least i can't imagine paragraph-separate really matters /that/ much... | "Do not request ‘NAMES’ for each channel when a client connects. This avoids already connected clients receiving unsolicited responses but prevents new clients from populating user lists." |
| 112 | 0 | maybe they need to remember to bounce unsplit ≥512 char messages back to where you were? | maybe they will tell me I am holding it wrong |
❝ Latest quotes
No quotes saved yet.