cl-irc-devel

cl-irc-devel@common-lisp.net

99 discussions

Start a nNew thread

[cl-irc-devel] Last chance: move your files off of common-lisp.net FTP, please.
by eenge＠common-lisp.net 14 Aug '06

14 Aug '06

See http://common-lisp.net/pipermail/users/2006-August/000006.html for more information. Thanks.

1 0

[cl-irc-devel] Re: patch for Allegro Common Lisp
by Erik Huelsmann 19 Jun '06

19 Jun '06

Hi! Thanks for your patch. However, I think it misses some parts: > Recent SVN stuff for CL-IRC has broken CL-IRC on Allegro. This patch > makes a couple of changes: > > 1. removes the asdf dependency on flexi-streams when :allegro is a > feature. I see this in the patch. > 2. replaces use of flexi-streams with use of allegro simple-streams > using conditional compilation. It is possible that some of this > might break on older versions of ACL. I *believe* it's safe on > ACL 7.0 and 8.0. Unless this is automagical by removing flexi-streams, I don't see this one. > 3. There was a quoted :type option to the channel :visibility slot. > This caused Allegro to toss a hairball in the MOP. I dequoted it, > and all seems well. And definitely not this one. (I'll comment a fix for it soon though, since I already found what you meant.) > Patch follows. I'm afraid it's just a default svn generated diff --- > I don't understand svn as well as CVS. In this respect CVS and svn shouldn't differ much. There are some stray symbols in your patch, did you mean to include them? > Index: utility.lisp > =================================================================== > --- utility.lisp (revision 161) > +++ utility.lisp (working copy) > @@ -112,7 +112,7 @@ > > (defun read-byte-no-hang (stream &optional eof-error-p eof-value) > (declare (optimize (speed 3) (debug 0) (safety 0))) > - (when (listen stream) > + (when (listen stream)all Here 'all' seems to be misplaced > (read-byte stream eof-error-p eof-value))) > > (defun read-sequence-until (stream target limit &key non-blocking) > @@ -421,7 +421,6 @@ > > (defmethod irc-string-downcase ((map-name (eql :ascii)) > string &key (start 0) end) > - (declare (ignore map-name)) > (string-downcase string :start start :end end)) Your log doesn't say why the declare should be removed... > (defun parse-isupport-multivalue-argument (argument) > Index: cl-irc.asd > =================================================================== > --- cl-irc.asd (revision 161) > +++ cl-irc.asd (working copy) > @@ -16,7 +16,7 @@ > :version "0.5.2" > :licence "MIT" > :description "Common Lisp interface to the IRC protocol" > - :depends-on (:split-sequence :trivial-sockets :flexi-streams) > + :depends-on (:split-sequence :trivial-sockets #-allegro > :flexi-streams) > :properties ((#:author-email . "cl-irc-devel(a)common-lisp.net") > (#:date . "$Date$") > ((#:albert #:output-dir) . "doc/api-doc/") Thanks for your comments and contribution! I hope you'll work with me to 'nail this one'! bye, Erik. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

1 0

[cl-irc-devel] Your message to cl-irc-ticket awaits moderator approval
by cl-irc-ticket-bounces＠common-lisp.net 08 May '06

08 May '06

Your mail to 'cl-irc-ticket' with the subject Re: [cl-irc] #16: LED???| 010-86508750??????13911588988??????|LED?????|??LED?????|010-86508750??????13911588988???????LED????????LED???????LED??????LED??????LED???????LED???????????????LED????????LED???????LED???????LED??????LED??????LED???????????????????????????????????????(????)?????????????????????????????????????????LED????????LED????????LED??????????????LED??????LED??? led???010-86508750??????13911588988 ????????????led??????????: 010-86508750??????13911588988 ???????? led led????? ????? led??? ??LED??????LED???????LED???????LED??????LED???????LED??????LED????????LED????????LED??????LED??????LED??????LED???????LED??????LED??????LED??????LED??????LED???????LED??????LED????????LED???????LED???????LED??????LED???????LED??????LED???????LED????????LED???????LED??????LED???????LED??????LED???? ??LED???|??LED???????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED????LED??????LED???? ??LED???|??LED?????????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED???????LED???????LED??????LED???? ??LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED???? LED????LED??????LED???? LED?????????LED??????LED???????LED??????LED???????LED??????LED???????????????????????LED????????????????????????????????LED?????????????????LED??????LED??????LED???????LED???????LED??????LED???????LED??????LED????????LED????????LED??????LED??????LED??????LED???????LED??????LED??????LED??????LED??????LED???????LED??????LED????????LED???????LED???????LED??????LED???????LED??????LED???????LED????????LED???????LED??????LED???????LED??????LED??????LED???|??LED???????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED????LED??????LED??????LED???|??LED?????????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED???????LED???????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED???? Is being held until the list moderator can review it for approval. We're sorry, due to the volume of spam we receive most mailinglists require you to subscribe before posting. You may cancel this post (at the URL below) or waiting for the moderator to approve it. Thanks and sorry for the inconvenience. The reason it is being held: Message body is too big: 111492 bytes with a limit of 40 KB Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://common-lisp.net/cgi-bin/mailman/confirm/cl-irc-ticket/6b18394db627bf…

1 0

[cl-irc-devel] Your message to cl-irc-ticket awaits moderator approval
by cl-irc-ticket-bounces＠common-lisp.net 08 May '06

08 May '06

Your mail to 'cl-irc-ticket' with the subject [cl-irc] #16: LED???| 010-86508750??????13911588988??????|LED?????|??LED?????|010-86508750??????13911588988???????LED????????LED???????LED??????LED??????LED???????LED???????????????LED????????LED???????LED???????LED??????LED??????LED???????????????????????????????????????(????)?????????????????????????????????????????LED????????LED????????LED??????????????LED??????LED??? led???010-86508750??????13911588988 ????????????led??????????: 010-86508750??????13911588988 ???????? led led????? ????? led??? ??LED??????LED???????LED???????LED??????LED???????LED??????LED????????LED????????LED??????LED??????LED??????LED???????LED??????LED??????LED??????LED??????LED???????LED??????LED????????LED???????LED???????LED??????LED???????LED??????LED???????LED????????LED???????LED??????LED???????LED??????LED???? ??LED???|??LED???????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED????LED??????LED???? ??LED???|??LED?????????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED???????LED???????LED??????LED???? ??LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED???? LED????LED??????LED???? LED?????????LED??????LED???????LED??????LED???????LED??????LED???????????????????????LED????????????????????????????????LED?????????????????LED??????LED??????LED???????LED???????LED??????LED???????LED??????LED????????LED????????LED??????LED??????LED??????LED???????LED??????LED??????LED??????LED??????LED???????LED??????LED????????LED???????LED???????LED??????LED???????LED??????LED???????LED????????LED???????LED??????LED???????LED??????LED??????LED???|??LED???????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED????LED??????LED??????LED???|??LED?????????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED???????LED???????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED??????LED???? Is being held until the list moderator can review it for approval. We're sorry, due to the volume of spam we receive most mailinglists require you to subscribe before posting. You may cancel this post (at the URL below) or waiting for the moderator to approve it. Thanks and sorry for the inconvenience. The reason it is being held: Message body is too big: 261582 bytes with a limit of 40 KB Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://common-lisp.net/cgi-bin/mailman/confirm/cl-irc-ticket/d49ee4f735b863…

1 0

[cl-irc-devel] Using Trac for project administration?
by Erik Huelsmann 12 Apr '06

12 Apr '06

Hi! Now that the repository has been converted to Subversion, it's worth to consider Trac for project administration (bugs, tasks, milestones, etc). I've asked for a setup for usocket, which was already running Subversion; you can see it here: http://trac.common-lisp.net/usocket . If nobody objects, I'll proceed and ask Erik Enge for a setup for cl-irc too. Thanks for your reactions in advance! bye, Erik. -- GMX Produkte empfehlen und ganz einfach Geld verdienen! Satte Provisionen f�r GMX Partner: http://www.gmx.net/de/go/partner

1 2

[cl-irc-devel] Re: [cl-irc-cvs] r146 - public_html
by Erik Huelsmann 08 Apr '06

08 Apr '06

> Author: ehuelsmann > Date: Sat Apr 8 18:13:34 2006 > New Revision: 146 Since this commit propagated to the website automatically, all seems to be set up fine. (Commit mails are comming in too, I see :-) I'll request Trac for the project so antifuchs can file his patches instead of me loosing them in my mail archive. Bye, Erik. -- "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail

1 0

[cl-irc-devel] cl-irc moved to subversion
by Erik Huelsmann 08 Apr '06

08 Apr '06

Hi! It's been a while since I brought up the subject of moving to Subversion. I did not find any objections back then and must say have been using svn support with the usocket project with great satisfaction. So, I decided there were no reasons left not to move. The subversion repository is now available under /project/cl-irc/svn. I know it's rather suddenly, but, with the given project activity, I thought I'd do it now that I had some time, without a long pre-notification period. I hope you don't mind. The old CVS repository is still there, but has been moved to cvsroot-to-move-to-svn/ (I'm trying to make it read-only and move it back under cvsroot). The website isn't yet in the repository. The svn repository layout is the standard one for Subversion repositories: - trunk/ - tags/ - branches/ To these topdirs, I'll also add the public_html directory, making it: - trunk/ - tags/ - branches/ - public_html/ since I don't consider it part of the project or documentation. When done, I'll also add a update-website-upon-public_html-commit script, for easy website maintenance. bye, Erik. -- Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer

1 0

[cl-irc-devel] external format guessing for incoming messages
by Andreas Fuchs 08 Mar '06

08 Mar '06

Hi, the following patch is a proof-of-concept implementation of external format guessing for incoming messages (and customizable external formats for outgoing messages, defaulting conservatively to latin-1). With that patch, cl-irc now opens a binary stream to the server, and opens flexi-streams on top of that. The outgoing part is pretty straightforward; the incoming part not so much (: Reading works like this: * We read a line of latin-1 chars * We try to decode their code-chars (latin1 is a 1:1 translation to code-chars, and where it isn't, I hope flexistreams takes care of that (-:) using the list of external-formats in *default-incoming-external-formats*. * When we find a decoding that doesn't throw a error, we build a message from that. Positive side effect: cl-irc should now work on windows because the external format allows specification of eol convention. Negative side effect: I didn't get parsing to work without #\Return, so this patch appends a #\Return character to the raw message. Which brings me to the todo list: * DCC connections probably don't work. I don't care about dcc, so I won't fix them (: * The parser should work without #\Return. * reading latin1 and decoding from the char codes is ... ugly. But it's probably less ugly than doing our own buffering. Maybe somebody wants to investigate that. (: Here's the patch: Cheers, -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs

1 0

[cl-irc-devel] [patch] ctcp request loop protection
by Andreas Fuchs 22 Feb '06

22 Feb '06

as it stands now, cl-irc answers ctcp replies with a reply of its own; this leads to loops (and, in the case of bouncers, to amplified loops). Here's a patch that makes cl-irc reply only if the request was in a privmsg (as specified in http://www.invlogic.com/irc/ctcpprot_06.html): Cheers, -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs

2 1

[cl-irc-devel] trailing argument bots patch
by Erik Huelsmann 20 Feb '06

20 Feb '06

Hi! Deprecating trailing-argument makes the bots in examples/ out of date. Below is a patch to fix that, but, given that I don't run them much, I'd like to send the patch here and have someone look them over and commit. Brian, could you? Thanks in advance! bye, Erik. Index: example/cliki.lisp =================================================================== RCS file: /project/cl-irc/cvsroot/cl-irc/example/cliki.lisp,v retrieving revision 1.38 diff -u -r1.38 cliki.lisp --- example/cliki.lisp 15 Oct 2005 19:16:52 -0000 1.38 +++ example/cliki.lisp 20 Feb 2006 20:36:21 -0000 @@ -723,7 +723,7 @@ (defun valid-cliki-message (message) - (scan *cliki-attention-prefix* (trailing-argument message))) + (scan *cliki-attention-prefix* (car (last (arguments message))))) (defvar *respond-to-general-hellos* nil) @@ -740,24 +740,27 @@ (format *trace-output* "~A~%" (nthcdr 10 (sb-debug:backtrace-as-list))) (return-from msg-hook)))) - (progn - (scan-for-more (trailing-argument message)) - (let ((respond-to (if (string-equal (first (arguments message)) *cliki-nickname*) (source message) (first (arguments message))))) + (destructuring-arguments + (target &rest unused &last text) + message + (declare (ignore unused)) + (scan-for-more text) + (let ((respond-to (if (string-equal target *cliki-nickname*) (source message) target))) (if (valid-cliki-message message) - (let ((response (cliki-lookup (regex-replace *cliki-attention-prefix* (trailing-argument message) "") :sender (source message) :channel (first (irc:arguments message))))) + (let ((response (cliki-lookup (regex-replace *cliki-attention-prefix* text "") :sender (source message) :channel target))) (and response (privmsg *cliki-connection* respond-to response))) - (if (string-equal (first (arguments message)) *cliki-nickname*) - (aif (cliki-lookup (trailing-argument message) :sender (source message)) + (if (string-equal target *cliki-nickname*) + (aif (cliki-lookup text :sender (source message)) (privmsg *cliki-connection* respond-to it)) - (if (anybody-here (trailing-argument message)) - (privmsg *cliki-connection* (first (arguments message)) (format nil "~A: hello." (source message)))))) + (if (anybody-here text) + (privmsg *cliki-connection* target (format nil "~A: hello." (source message)))))) (take-care-of-memos respond-to (source message)))))) (defvar *cliki-nickserv-password* "") (defun notice-hook (message) (if (and (string-equal (source message) "NickServ") - (scan "owned by someone else" (trailing-argument message))) + (scan "owned by someone else" (car (last (arguments message))))) (privmsg *cliki-connection* (source message) (format nil "IDENTIFY ~A" *cliki-nickserv-password*)))) (defun rename-cliki (new-nick) Index: example/specbot.lisp =================================================================== RCS file: /project/cl-irc/cvsroot/cl-irc/example/specbot.lisp,v retrieving revision 1.14 diff -u -r1.14 specbot.lisp --- example/specbot.lisp 9 Aug 2005 01:26:14 -0000 1.14 +++ example/specbot.lisp 20 Feb 2006 20:36:21 -0000 @@ -102,12 +102,13 @@ (and (not final) string)) (defun msg-hook (message) - (let ((destination (if (string-equal (first (arguments message)) *nickname*) - (source message) - (first (arguments message)))) + (let* ((target (first (arguments message)))) + (destination (if (string-equal target *nickname*) + (source message) + target)) (to-lookup (strip-address (trailing-argument message)))) (if (and (or - (string-equal (first (arguments message)) *nickname*) + (string-equal target *nickname*) (not (string= to-lookup (trailing-argument message)))) (member to-lookup '("help" "help?") :test #'string-equal)) (progn -- DSL-Aktion wegen gro�er Nachfrage bis 28.2.2006 verl�ngert: GMX DSL-Flatrate 1 Jahr kostenlos* http://www.gmx.net/de/go/dsl

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

cl-irc-devel