| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Both cases were off-by-one mistakes erring on the side of being too
conservative. This fixes these two harmless issues:
- For a single empty paste, it required another keystroke before
processing it
- For a sequence of themcase, a single '~' was left in the input
|
|
This actually workarounds a bug with the "st" terminal, for which i've
already submitted a patch, but irssi needs to be able to handle it
decently too.
|
|
"Small" as in ending in the same sig_input() call where they started
|
|
|
|
|
|
|
|
Also move relevant code to a paste_bracketed_end() function
|
|
- Use a keybinding to detect the start of a bracketed paste
- Iterate over the paste buffer looking for the end marker
|
|
The sequences we're after are found at the beginning or at the end of the
buffer, there's no need to scan the whole thing.
|
|
|
|
In the hope it'll do the same under the hood.
|
|
|
|
As an alternative method of paste detection, more reliable but might not be
supported by all the VTs.
|
|
Allow the user to set and modify the SASL parameters
|
|
The /NETWORK ADD command now is able to modify the SASL mechanism, the
username and the password on a chatnet basis.
|
|
|
|
|
|
dcc-get: close() the temp fd so we don't get ETXTBSY in ntfs mounts
|
|
Patch from debian bug 696963 [1]
Fixes github bug #220 and flyspray bug 867 [2]
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696963
[2]: http://bugs.irssi.org/index.php?do=details&task_id=867
|
|
Add multi-prefix to list of capabilities to request
|
|
The g_strcmp0 fallback in particular was broken since it was used in a
few places as a GCompareFunc, and macros don't work that way.
Yes, that one was my fault, but nobody complained :D
|
|
Turns out event_names_list() in irc-nicklist.c already handles this.
event_who() just ignores it, which is probably a good idea since some of
the irc servers I tested this with have a bug that results in sending
multiple prefixes in the NAMES reply but not in the WHO one (they were
forks of ircd-hybrid before 7.3.0)
And NAMES always happens, anyway. WHO is omitted sometimes for huge
channels.
|
|
|
|
Add new setting to modify behaviour of hilight_nick_matches to match anywhere in message
Fixes #56
|
|
|
|
|
|
Fix indentation
Remove unused variables that crept into the nick_match_msg_everywhere function
|
|
|
|
Network and IPv{4,6} related changes
|
|
The return value is a char*, and here it was false which is 0 which is
more or less the same as null.
That could have been a crash somewhere, the functions that call this
don't expect null ever.
|
|
Just passing the full target to the "message irc op_public" signal
handler and letting it do the cleanup.
The fe_channel_skip_prefix() call in event_privmsg() is kept because
recode_in() needs a real channel name, but
There was similar code in sig_message_own_wall(), but that one is
correct - the /wall command always sends NOTICE @#chan, so I added a
comment down there to make it clear.
|
|
Fixes FS#817 - "SegFault when executing bind command", which provides
the test case "/bind cleft key meta", which is stupid but now it doesn't
break things.
The limit of 100 is arbitrary, it means roughly 140 stack frames total.
The flyspray ticket mentions it crashes at 512, in my system it goes all
the way to 149677 stack frames.
http://bugs.irssi.org/index.php?do=details&task_id=817
|
|
http://bugs.irssi.org/index.php?do=details&task_id=905
Not using the patch from that ticket, the issue turned out to be that
(dest - last_lf_pos) returned number of unichr, not bytes, so that's 4
times less than what the size parameter of memmove() should be.
|
|
Add expandos for hostname
|
|
|
|
Ip's aren't selected using random() anymore, also select the ip version
by using getaddrinfo and some proper hints.
|
|
SASL support
|
|
Add some copyright headers here and there too.
|
|
|
|
|
|
Remove Garbage Collection support.
|
|
Add comment on the use of ??) in C, since that string isn't entirely
obvious to people who are reading the code.
|
|
GC support was never enabled by default and nobody in the current
development team seems to care about it.
|
|
|
|
|
|
|
|
|
|
Closes #169
|
