summary refs log tree commit diff
path: root/tab.c
diff options
context:
space:
mode:
authorJune McEnroe <june@causal.agency>2018-08-11 12:46:21 -0400
committerJune McEnroe <june@causal.agency>2018-08-11 12:46:21 -0400
commit6323ca0209383cec1bf774f9723b63a5a4685710 (patch)
tree67c4cb2ac7ca62fea06b58373f43d2e757284c02 /tab.c
parentBecome multi-channel (diff)
downloadcatgirl-6323ca0209383cec1bf774f9723b63a5a4685710.tar.gz
catgirl-6323ca0209383cec1bf774f9723b63a5a4685710.zip
Fix removing entries during tab complete
Since tabNext starts on match->next, if match gets removed, it should be
set to match->prev so that tabNext will start in the same spot.
Diffstat (limited to '')
-rw-r--r--tab.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/tab.c b/tab.c
index a6bb795..c0a96a4 100644
--- a/tab.c
+++ b/tab.c
@@ -81,7 +81,7 @@ void tabRemove(struct Tag tag, const char *word) {
 		if (tag.id != TAG_ALL.id && entry->tag != tag.id) continue;
 		if (strcmp(entry->word, word)) continue;
 		unlink(entry);
-		if (match == entry) match = entry->next;
+		if (match == entry) match = entry->prev;
 		free(entry->word);
 		free(entry);
 		return;
@@ -92,7 +92,7 @@ void tabClear(struct Tag tag) {
 	for (struct Entry *entry = head; entry; entry = entry->next) {
 		if (entry->tag != tag.id) continue;
 		unlink(entry);
-		if (match == entry) match = entry->next;
+		if (match == entry) match = entry->prev;
 		free(entry->word);
 		free(entry);
 	}
r'>2019-11-10Filter ACCOUNT, AWAY, CHGHOST for incapable clientsJune McEnroe 2019-11-10Rename listen to localJune McEnroe 2019-11-09Remove extended-join and invite-notifyJune McEnroe The remaining caps only generate new commands which can easily be filtered out when sending to clients so will be in the first pass of support. extended-join is probably safe to pass through unaltered, just causing extraneous parameters on JOIN commands, but maybe not. invite-notify reuses the INVITE command where the invited user is not self. 2019-11-09Maintain stateCaps and offer them to clientsJune McEnroe 2019-11-09Parse capabilitiesJune McEnroe The list that I've defined are the ones that I expect to be able to enable probably without any clients breaking... And of course server-time which pounce implements itself. 2019-11-09Avoid the reserved _A names with BIT macroJune McEnroe 2019-11-09Define macro for bit flag enumsJune McEnroe 2019-11-08Check that password is hashedJune McEnroe 2019-11-08Avoid calling getopt_long again after it returns -1June McEnroe On GNU, calling getopt_long again will reset optind back to the first non-option argument, which would cause an infinite loop of reading the same configurtion file forever. 2019-11-08Only change AWAY status for registered clientsJune McEnroe Turns out I did eventually fix this, because I may want to implement "passive clients" for logging or notification stuff, which wouldn't affect AWAY status either. 2019-11-07Just write the example normallyJune McEnroe 2019-11-07Include path in readlinkat errorJune McEnroe 2019-11-07Call clientConsume before clientRecvJune McEnroe This might reduce the frequency of a client getting its own message back because it was behind in the ring when it sent it. 2019-11-06Use -l:filename in Linux.mkJune McEnroe 2019-11-06Fix compat.h for #defined strlcpyJune McEnroe 2019-11-06Allow unsetting LIBRESSL_PREFIXJune McEnroe 2019-11-06Document calico service configurationJune McEnroe 2019-11-06Document SASL EXTERNAL configuration in more detailJune McEnroe 2019-11-06Document pounce service configurationJune McEnroe 2019-11-06Mention Darwin and GNU/Linux in READMEJune McEnroe 2019-11-06Assume LibreSSL from brew on DarwinJune McEnroe 2019-11-06Remove -DNO_EXPLICIT_BZERO from Darwin.mkJune McEnroe 2019-11-06Don't install rc scripts or dirs on LinuxJune McEnroe