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 |
| 59 | 0 | I just realized that i duplicated PR #76 with PR #93 | I just started trying to understand themes, only 40 years late or something |
| 58 | 0 | OK that's on master now | OK |
| 57 | 0 | trev: restarted now, but I doint see any actual channel buffers. What am I missing? | trev: restarted now, but I think it was in each channel buffer |
| 56 | 0 | I like how it behaves for a prompt token. | I like the 'network style. Nice when using multiple networks in a clatter instance. |
| 55 | 0 | re buffer names, is the only client where I found it. | re buffer names, is the *clatter: prefix needed/useful? I mean, running two IRC clients in one emacs process also seems like an edge case, and the names are fairly distinct |
| 54 | 0 | might be right | might be difficult to stay out of the way of other keybindings |
| 53 | 0 | I'm not suggesting that clatter adapt to my soju instance, bouncerserv seems to echo the AWAY back as well. | I'm not suggesting that clatter adapt to my weird way of doing colour schemes, btw, |
| 52 | 0 | resolved it. also some other network to see you're still enjoying hacking on it. | resolved it. also some other weird soju behavior i noticed when i deleted a child network server buffer and tried to reconnect - it now will restore that network connection |
| 51 | 0 | i will give one quick feedback item. I had an issue with 'oldest-first | i will try to look later too |
| 50 | 0 | seeing some messages like "error in process filter: cons: Wrong type argument: char-or-string-p, nil" during initial connection. Haven't had a lot of use of `buffer-invisibility-spec' and `wrap-prefix' for soft line wraps. This is even better than the current one. | seeing some messages like "error in process filter: cons: Wrong type argument: char-or-string-p, nil" during initial connection. Haven't had a chance to narrow it down yet. The connection seems to go OK despite the messages |
| 49 | 0 | ok, probably long enough not to be a little buggy when that is slow. | ok, probably long enough not to be a throwaway troll account ;) |
| 48 | 0 | that seems ok though | that seems to be specific to the configuration on libera.chat; on oftc debchange (same bot) answers me in channel. |
| 47 | 0 | OIC. the bots sends messages that end up in my init for clatter.el, might be less annoying now. | OIC. the bots sends messages that end up in my server buffer. |
| 46 | 0 | If I use 'full and think it's this form → (or line (clatter-irc-privmsg target text)) | If I go /query litharge, I don't see the output from the bot when I e.g. type "help". I can see the output in other clients connected to the same soju instance. Any ideas what that might be? |
| 45 | 0 | I'm using auth-source-pass, so it would work...it kind of debug view that shows everyone's ratio lol | I'm using auth-source-pass, so it might be less configurable |
| 44 | 0 | trev: (clatter-setup) registers the hooks and MELPA mandates that loading elisp code should have no effect either way. In my init for clatter.el, might be right | trev: (clatter-setup) registers the hooks and MELPA mandates that loading elisp code should have no side-effects, so I don't think we can get rid of that. |
| 43 | 0 | pushed a few commits behind | pushed a few fixes. there's also a new function `clatter-track-clear-all' which will clear all the track notifications at the bottom. |
| 42 | 0 | Does seem kinda related to gnutls | Does seem kinda related to the scrollbar though. If I use the scrollbar to scroll → slow/laggy. Keyboard motions → fine. |
| 41 | 0 | thanks to you and alcor It's become a great daily driver | thanks |
| 40 | 0 | Gonna try running in 'oldest-first for a while on some other complex check. | Gonna try running in 'oldest-first for a while on some other network to see what happens |
| 39 | 0 | One thing I was screwing around wiht the compact join/part stuff cause it was CLabber that I duplicated PR #76 with PR #93 | One thing I was thinking about, clatter makes a lot of use of `buffer-invisibility-spec' and `wrap-prefix' for soft line wraps. This is some advanced stuff and might slow Emacs down on large backlogs/buffers. |
| 38 | 0 | i have a split doesn't clear the track in mode-line. | i have lag in the #systemcrafters buffer only |
| 37 | 0 | Reminder to self. The clatter-track issue where focusing a split and not buffer switch | Reminder to self. The clatter-track issue where focusing a split doesn't clear the track in mode-line. |
❝ Latest quotes
No quotes saved yet.