| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Fixes the test suite. I guess it's useful for something.
|
| |
|
|
| |
Also split underscore_dedupe from nick_dedupe.
|
| |
|
|
|
|
|
| |
Used uncrustify, with the configuration file in ./doc/uncrustify.cfg
Commit author set to "Indent <please@skip.me>" so that it's easier to
skip while doing git blame.
|
| |
|
|
|
|
|
|
|
|
|
| |
With similar commands being supported, such as INVITE, the KICK command
should be supported as well. The key motivation behind supporting KICK
is having for having a way to remove users from group chats. As of now,
there is no way for a bitlbee user to remove a user from a group chat.
With no current KICK implementation, it made using this command a prime
candidate for the UI side of this implementation. In addition, the KICK
command has been supported in the control channel as well. This is to
keep the INVITE/KICK pair consistent.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This allows for users to be declared as being special, which does not
have any specific meaning. The meaning of being special is different
from protocol-to-protocol, which many protocols do not even implement.
This functionality is mainly geared towards a special user state which
only some protocols may actually need to define. For example, with the
third-party Steam plugin, this can be used for denoting a user which is
actively playing a game.
By default, this mode will not actually be used by any plugin. However,
it does default to the half-operator user mode.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the auto_join channel flag set to false, the channel is still
auto-joined. This can lead to the channel being "doubly" joined if
a client previously sent a channel join request. The result of being
"doubly" joined is really undefined, but most notably memory leaks
can occur.
It also appears, based on the comment under the modified condition,
the previous condition was incorrect.
Another patch should probably implement some sort of check to ensure a
channel is not already joined, assuming the auto_join flag is enabled.
|
| |
|
|
|
|
|
|
|
|
|
| |
This fixes warnings about passing signed chars to them (apparently they
are implemented as macros that do array lookups without checks in some
platforms, yay)
Specifically:
functions=isalnum|isalpha|isdigit|isspace|isxdigit|tolower|toupper
sed -ir "s/$functions/g_ascii_&/g" **/*.c
|
| | |
|
| |
|
|
|
|
| |
fix is ugly as it's putting a detail relevant to XML storage elsewhere in
the code. But I don't think we should have any other storage formats anyway.
|
| |
|
|
|
|
|
| |
my copyright mentions since some were getting pretty stale. Left files not
touched since before 2012 alone so that this change doesn't touch almost
EVERY source file.
|
| |
|
|
|
|
| |
separate control channel with all contacts *not* in a certain group/from
a certain IM account/network, etc.
|
| |
|
|
|
|
|
| |
for example when the user gets invited to a channel that already exists.
Separately, I should handle invites like that better. Will file a bug for
that.
|
| |
|
|
|
|
|
| |
channel-chatroom reference when leaving a chatroom. This fixes two very
similar crash bugs when leaving a chatroom within the paste_buffer_delay
period.
|
| |
|
|
|
| |
a user's message in, instead of just &bitlbee by default.
|
| |
|
|
|
| |
bug and preventing a generally confusing and undesirable setup.
|
| |
|
|
|
|
|
|
|
|
| |
BitlBee used by a user, and if it looks like s/he hasn't used this one
before, show a list of new features that may be interesting.
Since I don't think im.bitlbee.org users will read any changelogs ever,
this is probably not a bad idea. If you hate it, the following command
should get rid of it forever: set last_version 9999999
|
| |
|
|
|
| |
in the current channel.
|
| | |
|
| |
|
|
|
| |
the last_channel variable, like for any other user.
|
| | |
|
| |
|
|
|
| |
attribute, not as a setting (since all accounts have it anyway).
|
| | |
|
| |
|
|
|
|
| |
show_offline and away_devoice and possibly other ideas into one setting
called show_users. Documentation will come soon. :-P
|
| |
|
|
|
|
| |
only triggers on channels created by the user. (And not at identify time,
which was causing odd problems on my test setup.)
|
| |
|
|
|
| |
what the older version also did so that Irssi won't clean up the window.
|
| |
|
|
|
| |
groupchats not reimplemented yet but that's the next step.
|
| |
|
|
|
| |
pointless at that stage and may cause crashes.
|
| |
|
|
|
| |
channel if the user isn't in it.
|
| |
|
|
|
| |
name.
|
| |
|
|
|
|
| |
If someone has two MSN accts and wants contacts from both in one channel,
this is now possible.
|
| | |
|
| |
|
|
|
| |
so if it wants to (temporary channels), do it via a timer.
|
| |
|
|
|
| |
forever.
|
| | |
|
| |
|
|
|
| |
that same channel.
|
| |
|
|
|
|
| |
much any 8-bit character is allowed in there - while nicknames are very
restricted.
|
| |
|
|
|
| |
will check the others now.
|
| | |
|
| |
|
|
|
| |
s/he joins.
|
| |
|
|
|
| |
channel name or a number in "chan set"/etc.
|
| |
|
|
|
| |
(when sending a /quit instead, for example).
|
| |
|
|
|
|
| |
restored "chat add" behaviour a little bit better (don't clean up a
channel when its room disappears, just disconnect it from the groupchat).
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
"chat"
command will probably mostly stick around for bw compatibility. Still thinking
about how this should work eventually.
|
| |
|
|
|
| |
first character after the prefix *can* be a number.
|
| | |
|
