| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Too much repeated, non-obvious code.
|
|
|
|
| |
Just set `tls_cert`, and add `sasl` to `capabilities`.
|
|
|
|
|
| |
It doesn't require much effort to cancel capabilities, plus with
the newer version we get the respective notification anyway.
|
|
|
|
|
| |
The list may later be requested manually, which shouldn't have
an unexpected side-effect.
|
|
|
|
| |
We can receive and display capability values now.
|
| |
|
|
|
|
| |
The bug has apparently been there since the beginning.
|
|
|
|
| |
Forgotten to do it when adding the support for it.
|
|
|
|
|
| |
We might just always set the highlighted bit on,
it would be consistent with PMs.
|
|
|
|
|
|
| |
Also fixed the possibility of eating a sequence of signals
as we reset the indicators /after/ we took action,
which creates a time window for races.
|
| |
|
| |
|
|
|
|
| |
Don't trust the IRCd to have them in a subset of UTF-8.
|
|
|
|
|
|
|
| |
It was super annoying to just slightly modify strings and
string arrays, now you can have existing values filled in.
complete_word() looks a bit cleaner now as well.
|
|
|
|
|
|
|
|
| |
When fancy-prompt.lua is enabled, tho prompt is two-lined
and a simple PageUp would skip one line of content.
It works slightly better than it should: when there's under
a page of content to scroll, there is no shift at all.
|
|
|
|
|
| |
A most unfortunate 06d3b3b regression, mostly stemming from
forgetting why the `break` was in place and not documenting it.
|
| |
|
| |
|
|
|
|
|
| |
It may theoretically bite us in the ass with non-UTF-8-compliant
IRC servers, and certainly with double-width characters.
|
|
|
|
| |
Partly by unifying the interface for prompt hooks to match GNU Readline.
|
|
|
|
|
|
|
| |
Now that the input to the backlog helper is wrapped the same way
as what we display. There's a slight issue always triggered by
fancy-prompt.lua where a multiline prompt/command line makes less(1)
go too high up but it's nothing too important.
|
|
|
|
|
|
| |
There's nothing experimental about this project anymore. It's stable.
Maybe we should add a photo of Hitler or something.
|
|
|
|
| |
A few things might have changed.
|
| |
|
|
|
|
| |
To some extent they duplicate the README but from a different angle.
|
|
|
|
| |
Regression from the last release.
|
| |
|
|
|
|
| |
Now our user just needs to be able to guess that it's a hex string.
|
|
|
|
| |
It's quite unlikely that this project will ever see compiled plugins.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Install plugins to /usr/share rather than /usr/lib since they're
arch-independent. Many precedents can be found for scripted plugins
in /usr/share and fewer for /usr/lib.
Look for plugins in all XDG data directories and repurpose
the "plugin_dir" setting to override this behaviour.
This adds some complexity to the bot but unifies the project.
It might make sense to remove the "plugin_dir" setting.
|
| |
|
|
|
|
| |
Their usefulness was almost negative.
|
|
|
|
| |
The multiple-output custom command ran separately for each binary.
|
|
|
|
| |
A nice, round number.
|
| |
|
|
|
|
| |
Testing in production is discouraged.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Ensure the error stack is cleared after errors are processed.
Also handle NULL returns safely.
Makes the debug mode spew more data, though almost none of
the contexts is in reaction to network peer data.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The worst offenders are actually OpenSSL and Lua, this is
mostly about a preventable surprise.
This is more correct because we mix escape sequences for
attributes with text, however in practice no one will use
shit-jizz with degesch.
It is also a clean-up: "struct line_char" has been almost
halved in size. We used to use it as a cache and now we
recompute the multibyte sequence.
Of course, it'd be best to get rid of the linked list but
it would take a very long time to rewrite the algorithm.
Plus, it's not certain that it could be improved by much.
The change in "struct line_char_attrs" is merely cosmetical.
|
| |
|
|
|
|
|
| |
We don't want to print the reply for ourselves
nor for unknown or PM-only users.
|
| |
|
|
|
|
|
| |
Channels now need a reference to the server,
so don't pass it to functions.
|
|
|
|
|
| |
We're not going to implement polling. Polling is complex.
Freenode supports away-notify.
|
| |
|
| |
|
|
|
|
| |
I got confused about safety.
|
|
|
|
| |
3_3_3_3_4 looks awful and it wasn't even precise.
|