| Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
string for easier parsing
|
|
|
|
created' signals.
Answer is no, because it gets initialised befor the perl
core, so we're too late to handle the signal. Might be a useful testcase for
when I start meddling with multiple keyboards though.
|
|
|
|
auto-display though. Maybe need to generate an index? (But where to store it?)
|
|
|
|
|
|
|
|
can't figure out why.
|
|
|
|
to fix it.
|
|
|
|
Hopefully a useful starting point for people wanting remote command info.
|
|
|
|
|
|
Test::Irssi module.
|
|
|
|
|
|
output.
|
|
to work on the output format though.
|
|
|
|
messages and automatically overrides /join to point you to the right forwarded channel.
|
|
but still a bit dumb.
|
|
nested.
|
|
attributions and cleanup though
|
|
IO. Hope to expand it to include network IO at some point.
|
|
|
|
command output so it can be parsed.
|
|
exposes all the Irssi exportables into the temp namespace.
|
|
|
|
|
|
|
|
namespace functions for ease of testing.
|
|
|
|
|
|
|
|
fly from within irssi scripts.
|
|
|
|
|
|
the signal docs to describe hte behaviour of 'gui print text'
|
|
|
|
|