From jcm at FreeBSD-uk.eu.org Wed Jan 3 16:02:34 2007 From: jcm at FreeBSD-uk.eu.org (Jonathon McKitrick) Date: Wed, 3 Jan 2007 16:02:34 +0000 Subject: [hunchentoot-devel] Idle thread messages In-Reply-To: References: <20061226182741.GA20541@dogma.freebsd-uk.eu.org> Message-ID: <20070103160234.GA95422@dogma.freebsd-uk.eu.org> On Tue, Dec 26, 2006 at 08:23:17PM +0100, Edi Weitz wrote: : On Tue, 26 Dec 2006 18:27:41 +0000, Jonathon McKitrick wrote: : : > I searched the docs for 'idle' and 'thread' and google didn't turn : > up anything pertinent... is there any reason to be concerned about : > the idle thread messages that appear from time to time from : > hunchentoot? During debugging, they can pop up rather frequently in : > SLIME, and otherwise they are just logged to the console. Does this : > have anything to do with *cleanup-interval*? : : What are these "idle thread messages?" How do they look like? Which : Lisp are you using? Have you read the messages sent to the mailing : list this month? Are your problems related to the timeout problems : mentioned there? IIRC, this is just a minor issue that could be easily fixed, ignoring these non-errors. It would be very helpful for debugging if these messages didn't land me in the debugger every minute or so. Is this something I can track down myself? Jonathon McKitrick -- My other computer is your Windows box. From edi at agharta.de Thu Jan 4 11:21:39 2007 From: edi at agharta.de (Edi Weitz) Date: Thu, 04 Jan 2007 12:21:39 +0100 Subject: [hunchentoot-devel] Idle thread messages In-Reply-To: <20070103160234.GA95422@dogma.freebsd-uk.eu.org> (Jonathon McKitrick's message of "Wed, 3 Jan 2007 16:02:34 +0000") References: <20061226182741.GA20541@dogma.freebsd-uk.eu.org> <20070103160234.GA95422@dogma.freebsd-uk.eu.org> Message-ID: On Wed, 3 Jan 2007 16:02:34 +0000, Jonathon McKitrick wrote: > IIRC, this is just a minor issue that could be easily fixed, > ignoring these non-errors. It would be very helpful for debugging > if these messages didn't land me in the debugger every minute or so. > Is this something I can track down myself? Sure... From dathomp1 at yahoo.com Thu Jan 4 13:56:35 2007 From: dathomp1 at yahoo.com (dat) Date: Thu, 4 Jan 2007 05:56:35 -0800 (PST) Subject: [hunchentoot-devel] accessing xml data from xforms/xhtml post Message-ID: <20070104135635.93198.qmail@web34014.mail.mud.yahoo.com> I'm hoping this isn't in the "lame questions" category... Is there a straightforward way to have hunchentoot look at xml data submitted by an xforms document? (This comes from playing with firefox with the xforms extension.) Example: 1. Using the "post" method (not "form-data-post"), an xforms document submits xml at the end of the day. If the firefox "livehttpheaders" plugin isn't lying, it looks something like: POST /tadmin/qeditor-qcatsel HTTP/1.1 Host: 127.0.0.1:3000 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061208 Firefox/2.0.0.1 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Content-Length: 215 Content-Type: application/xml 2 1 2. However, Hunchentoot's RAW-POST-DATA returns only "2 1"...all of the xml tag information is (apparently) discarded. Is there a straightforward way to get anything a littler "rawer"? Unfortunately, I'm definitely on the lisp 'newbie' side and got lost on planet chunga as I was trying to figure things out... Thanks for your time and any tips/suggestions/recommendations, Alan Thompson __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From rm at seid-online.de Thu Jan 4 14:08:37 2007 From: rm at seid-online.de (Ralf Mattes) Date: Thu, 04 Jan 2007 15:08:37 +0100 Subject: [hunchentoot-devel] accessing xml data from xforms/xhtml post In-Reply-To: <20070104135635.93198.qmail@web34014.mail.mud.yahoo.com> References: <20070104135635.93198.qmail@web34014.mail.mud.yahoo.com> Message-ID: <1167919717.5224.5.camel@localhost.localdomain> On Thu, 2007-01-04 at 05:56 -0800, dat wrote: > I'm hoping this isn't in the "lame questions" category... Is there > a straightforward way to have hunchentoot look at xml data submitted by > an xforms document? (This comes from playing with firefox with the > xforms extension.) > > Example: > > 1. Using the "post" method > (not "form-data-post"), an xforms document submits xml at the end of > the day. If the firefox "livehttpheaders" plugin isn't lying, it looks > something like: > > POST /tadmin/qeditor-qcatsel HTTP/1.1 > Host: 127.0.0.1:3000 > User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061208 Firefox/2.0.0.1 > Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 > Accept-Language: en-us,en;q=0.5 > Accept-Encoding: gzip,deflate > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > Keep-Alive: 300 > Connection: keep-alive > Content-Length: 215 > Content-Type: application/xml > > > > > 2 1 > > > 2. > However, Hunchentoot's RAW-POST-DATA returns only "2 1"...all of the > xml tag information is (apparently) discarded. Is there > a straightforward way to get anything a littler "rawer"? > > Unfortunately, I'm definitely on the lisp 'newbie' side and got lost on planet chunga as I was trying to figure things out... > > Thanks for your time and any tips/suggestions/recommendations, How about raw-post-data (http://weitz.de/hunchentoot/#raw-post-data)? This will give you the "raw" xml which you can then parse yourself. HTH Ralf Mattes > Alan Thompson > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > _______________________________________________ > tbnl-devel site list > tbnl-devel at common-lisp.net > http://common-lisp.net/mailman/listinfo/tbnl-devel From marijnh at gmail.com Thu Jan 4 14:20:59 2007 From: marijnh at gmail.com (Marijn Haverbeke) Date: Thu, 4 Jan 2007 15:20:59 +0100 Subject: [hunchentoot-devel] accessing xml data from xforms/xhtml post In-Reply-To: <20070104135635.93198.qmail@web34014.mail.mud.yahoo.com> References: <20070104135635.93198.qmail@web34014.mail.mud.yahoo.com> Message-ID: > > 2. > However, Hunchentoot's RAW-POST-DATA returns only "2 1"...all of the > xml tag information is (apparently) discarded. Is there > a straightforward way to get anything a littler "rawer"? Are you perhaps looking at the data in your browser? If so, have you tried 'view source'? (The browser will interpret the XML as messy HTML and not show tags... this has confused me in the past.) Marijn -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcm at FreeBSD-uk.eu.org Thu Jan 4 14:51:41 2007 From: jcm at FreeBSD-uk.eu.org (Jonathon McKitrick) Date: Thu, 4 Jan 2007 14:51:41 +0000 Subject: [hunchentoot-devel] Idle thread messages In-Reply-To: <20070103160234.GA95422@dogma.freebsd-uk.eu.org> References: <20061226182741.GA20541@dogma.freebsd-uk.eu.org> <20070103160234.GA95422@dogma.freebsd-uk.eu.org> Message-ID: <20070104145141.GA1787@dogma.freebsd-uk.eu.org> get-request-data is wrapped in ignore-errors, but when it calls chunga:read-line, the timeout occurs. read-line* gets the timeout while calling flexi-streams, which of course calls lower level stuff. I'm over my head at that point. I don't understand why ignore-errors doesn't ignore the error - sb-sys:io-timeout. Jonathon McKitrick -- My other computer is your Windows box. From edi at agharta.de Thu Jan 4 17:24:18 2007 From: edi at agharta.de (Edi Weitz) Date: Thu, 04 Jan 2007 18:24:18 +0100 Subject: [hunchentoot-devel] Idle thread messages In-Reply-To: <20070104145141.GA1787@dogma.freebsd-uk.eu.org> (Jonathon McKitrick's message of "Thu, 4 Jan 2007 14:51:41 +0000") References: <20061226182741.GA20541@dogma.freebsd-uk.eu.org> <20070103160234.GA95422@dogma.freebsd-uk.eu.org> <20070104145141.GA1787@dogma.freebsd-uk.eu.org> Message-ID: On Thu, 4 Jan 2007 14:51:41 +0000, Jonathon McKitrick wrote: > get-request-data is wrapped in ignore-errors, but when it calls > chunga:read-line, the timeout occurs. read-line* gets the timeout > while calling flexi-streams, which of course calls lower level > stuff. I'm over my head at that point. I don't understand why > ignore-errors doesn't ignore the error - sb-sys:io-timeout. Look at the definition of IGNORE-ERROS in util.lisp. From dathomp1 at yahoo.com Thu Jan 4 23:59:41 2007 From: dathomp1 at yahoo.com (dat) Date: Thu, 4 Jan 2007 15:59:41 -0800 (PST) Subject: [hunchentoot-devel] accessing xml data from xforms/xhtml post Message-ID: <20070104235941.63288.qmail@web34001.mail.mud.yahoo.com> Thanks, Marijn (esp. for the kind/merciful parenthetical note). Your guess was correct. Although 'view source' didn't reveal anything in this particular case, looking at the data in lisp made it clear what was going on: I was using a browser to look at the value returned by RAW-POST-DATA and had lazily stuck

tags around the xml, not realizing the xml between the tags wasn't displayed by firefox... Thanks again, Alan Thompson dathomp1 at yahoo.com ----- Original Message ---- From: Marijn Haverbeke To: tbnl-devel at common-lisp.net Sent: Thursday, January 4, 2007 6:20:59 AM Subject: Re: [hunchentoot-devel] accessing xml data from xforms/xhtml post 2. However, Hunchentoot's RAW-POST-DATA returns only "2 1"...all of the xml tag information is (apparently) discarded. Is there a straightforward way to get anything a littler "rawer"? Are you perhaps looking at the data in your browser? If so, have you tried 'view source'? (The browser will interpret the XML as messy HTML and not show tags... this has confused me in the past.) Marijn _______________________________________________ tbnl-devel site list tbnl-devel at common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From edi at agharta.de Thu Jan 11 21:18:33 2007 From: edi at agharta.de (Edi Weitz) Date: Thu, 11 Jan 2007 22:18:33 +0100 Subject: [hunchentoot-devel] Re: hunchentoot specials In-Reply-To: <200701101638.33065.mega@retes.hu> =?iso-8859-1?q?=28G=E1bor?= Melis's message of "Wed, 10 Jan 2007 16:38:32 +0100") References: <200701101638.33065.mega@retes.hu> Message-ID: [Cc to mailing list.] Hi! On Wed, 10 Jan 2007 16:38:32 +0100, G?bor Melis wrote: > I've been migrating some of my stuff over to hunchentoot from > paserve and I'm generally happy with it. Good... :) > One thing that strikes me as odd is the number of specials that > govern server behaviour. I'm not talking about *request* and *reply* > since they are dynamic extent by nature, but *log-...*, > *default-...*, and well ... almost everything else. It seems to me > that they make it very hard to run more than one hunchentoot server > with different settings. I'm thinking virtual hosts. > > To keep it short: > > - do you agree? Yes. The reason is Hunchentoot's heritage from TBNL which was a single-server library. And the fact that I myself almost never use more than one server per image. > - if yes, do you think it will be changed? I'm pretty busy right now, so don't hold your breath. But, yes, it will be changed one day. > - would you take patches in this direction if I ever happen to get > around to do it? Sure. However, I get a lot of patches where I finally end up re-writing most of what I received which really doesn't save time. What I'd like to see is: - Follow the coding and indentation conventions I use elsewhere in the code. - Don't use tab characters. - Every function/variable/class/slot/etc. should have a reasonable documentation string. - The patch should include updates to the HTML documentation as well (if necessary). Yes, I'm anal about this, sorry. Anyway - apart from that I'm always happy to incorporate patches. And if I like the new code enough, I might also end up doing the work listed above myself. But it'll be faster if someone else has already done so. Thanks, Edi. From jeffrey at cunningham.net Fri Jan 12 03:38:39 2007 From: jeffrey at cunningham.net (Jeffrey Cunningham) Date: Thu, 11 Jan 2007 19:38:39 -0800 Subject: [hunchentoot-devel] How to pass define-easy-handler symbol? Message-ID: <20070112033839.GA18834@achilles.olympus.net> This is probably a dumb question, but I haven't been able to figure it out yet. Suppose I want to call 'DEFINE-EASY-HANDLER inside another function and pass the symbol as an argument. I tried stuff like this: (defun some-function (name) (define-easy-handler ((intern name) (concatenate 'string name ".html") :default-request-type :post) ((formarg :parameter-type :keyword) (html-generator name formarg))) But it wants a real symbol. Then I tried passing names as symbols and turning them into strings where I needed. That works in the sense that it creates the page, but each one is bound to the same symbol no matter what symbols I give it, so only the last page created works. Is there a way to do this? Thanks for any help. --Jeff From tobia.conforto at linux.it Fri Jan 12 15:13:08 2007 From: tobia.conforto at linux.it (Toby) Date: Fri, 12 Jan 2007 16:13:08 +0100 Subject: [hunchentoot-devel] How to pass define-easy-handler symbol? In-Reply-To: <20070112033839.GA18834@achilles.olympus.net> References: <20070112033839.GA18834@achilles.olympus.net> Message-ID: <20070112151307.GA1827@localhost.localdomain> Jeffrey Cunningham wrote: > Suppose I want to call 'DEFINE-EASY-HANDLER inside another function > and pass the symbol as an argument. I tried stuff like this: > > (defun some-function (name) > (define-easy-handler ((intern name) > :uri (concatenate 'string name ".html") > :default-request-type :post) > ((formarg :parameter-type :keyword)) > (html-generator name formarg))) define-easy-handler is a macro, which means that (intern name) doesn't get evaluated unless/until the macro sees fit. Try defining some-function as a macro too: (defmacro some-function (name) `(define-easy-handler (,(intern name) :uri ,(concatenate 'string name ".html") :default-request-type :post) ((formarg :parameter-type :keyword)) (html-generator ,name formarg))) Toby From jeffrey at cunningham.net Sat Jan 13 15:21:07 2007 From: jeffrey at cunningham.net (Jeffrey Cunningham) Date: Sat, 13 Jan 2007 07:21:07 -0800 Subject: [hunchentoot-devel] How to pass define-easy-handler symbol? In-Reply-To: <20070112151307.GA1827@localhost.localdomain> References: <20070112033839.GA18834@achilles.olympus.net> <20070112151307.GA1827@localhost.localdomain> Message-ID: <20070113152107.GB21616@achilles.olympus.net> On Fri Jan 12, 2007 at 04:13:08PM +0100, Toby wrote: > > define-easy-handler is a macro, which means that (intern name) doesn't > get evaluated unless/until the macro sees fit. > > Try defining some-function as a macro too: > > (defmacro some-function (name) > `(define-easy-handler (,(intern name) > :uri ,(concatenate 'string name ".html") > :default-request-type :post) > ((formarg :parameter-type :keyword)) > (html-generator ,name formarg))) > That works. I tried a macro but didn't quite get it right. Thank you, Toby. --Jeff From jeffrey at cunningham.net Sat Jan 13 16:18:29 2007 From: jeffrey at cunningham.net (Jeffrey Cunningham) Date: Sat, 13 Jan 2007 08:18:29 -0800 Subject: [hunchentoot-devel] How to pass define-easy-handler symbol? In-Reply-To: <20070112151307.GA1827@localhost.localdomain> References: <20070112033839.GA18834@achilles.olympus.net> <20070112151307.GA1827@localhost.localdomain> Message-ID: <20070113161829.GA22955@achilles.olympus.net> On Fri Jan 12, 2007 at 04:13:08PM +0100, Toby wrote: > > define-easy-handler is a macro, which means that (intern name) doesn't > get evaluated unless/until the macro sees fit. > > Try defining some-function as a macro too: > > (defmacro some-function (name) > `(define-easy-handler (,(intern name) > :uri ,(concatenate 'string name ".html") > :default-request-type :post) > ((formarg :parameter-type :keyword)) > (html-generator ,name formarg))) > Hmmm. Unfortunately, it leads to another problem when I try to apply it to something useful, such as this reduction: mapc #'some-function '("foo" "bar") or even (let ((s "foo")) (some-function s)) Now the macro sees only the symbol s, not the string it refers to. Is there a way to get around this? My knowledge of macros is pretty weak. Thanks, --Jeff From tobia.conforto at linux.it Sat Jan 13 17:27:22 2007 From: tobia.conforto at linux.it (Toby) Date: Sat, 13 Jan 2007 18:27:22 +0100 Subject: [hunchentoot-devel] How to pass define-easy-handler symbol? In-Reply-To: <20070113161829.GA22955@achilles.olympus.net> References: <20070112033839.GA18834@achilles.olympus.net> <20070112151307.GA1827@localhost.localdomain> <20070113161829.GA22955@achilles.olympus.net> Message-ID: <20070113172721.GD1827@localhost.localdomain> Jeffrey Cunningham wrote: > Now the macro sees only the symbol s, not the string it refers to. > Is there a way to get around this? Not without understanding how macros work. May I suggest this book, especially chapter 8? http://www.gigamonkeys.com/book/ Toby From jeffrey at cunningham.net Sat Jan 13 22:22:14 2007 From: jeffrey at cunningham.net (Jeffrey Cunningham) Date: Sat, 13 Jan 2007 14:22:14 -0800 Subject: [hunchentoot-devel] How to pass define-easy-handler symbol? In-Reply-To: <20070113172721.GD1827@localhost.localdomain> References: <20070112033839.GA18834@achilles.olympus.net> <20070112151307.GA1827@localhost.localdomain> <20070113161829.GA22955@achilles.olympus.net> <20070113172721.GD1827@localhost.localdomain> Message-ID: <20070113222214.GA29052@achilles.olympus.net> On Sat Jan 13, 2007 at 06:27:22PM +0100, Toby wrote: > Jeffrey Cunningham wrote: > > Now the macro sees only the symbol s, not the string it refers to. > > Is there a way to get around this? > > Not without understanding how macros work. > > May I suggest this book, especially chapter 8? > http://www.gigamonkeys.com/book/ > Okay, I read chapter 8 (very good chapter). And I'm almost there. I came up with this macro, which works: (defmacro build-handler (category) (let ((symb (gensym))) `(progn (setf ,symb (intern, category)) (define-easy-handler (,symb :uri (catstr "/" ,category ".html") :default-request-type :post) ((arg)) (declare (ignorable arg)) (with-html (:html (:body (:h1 "Crazy as " (str ,category)))))))))) So (let ((s "batshit")) (build-handler s)) and (build-handler "batshit") both work. But they give the following warning: -+ Warnings (2) |-- --> PROGN SETF | ==> | (SETQ #:G0 (INTERN CL-USER::S)) | undefined variable: #:G0 `-- This variable is undefined: #:G0 which doesn't seem healthy. Could you tell me what I'm doing wrong? Regards, --Jeff From jeffrey at cunningham.net Sun Jan 14 00:19:50 2007 From: jeffrey at cunningham.net (Jeffrey Cunningham) Date: Sat, 13 Jan 2007 16:19:50 -0800 Subject: [hunchentoot-devel] How to pass define-easy-handler symbol? In-Reply-To: <20070113222214.GA29052@achilles.olympus.net> References: <20070112033839.GA18834@achilles.olympus.net> <20070112151307.GA1827@localhost.localdomain> <20070113161829.GA22955@achilles.olympus.net> <20070113172721.GD1827@localhost.localdomain> <20070113222214.GA29052@achilles.olympus.net> Message-ID: <20070114001950.GA30645@achilles.olympus.net> On Sat Jan 13, 2007 at 02:22:14PM -0800, Jeffrey Cunningham wrote: > > Could you tell me what I'm doing wrong? > Nevermind. I figured it out. Thanks for the help. -Jeff From yoni-r at actcom.com Sun Jan 14 09:56:44 2007 From: yoni-r at actcom.com (Yoni Rabkin Katzenell) Date: Sun, 14 Jan 2007 11:56:44 +0200 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp Message-ID: <87ac0mgcdf.fsf@actcom.com> Some time ago I added two lines to test.lisp which add a favicon to the "menu" page. Maybe someone here will find it useful in a Google search. You don't actually need the patch, but it is the shortest method of explaining what to add where. -------------- next part -------------- A non-text attachment was scrubbed... Name: test_favicon.patch Type: text/x-patch Size: 919 bytes Desc: not available URL: -------------- next part -------------- -- "Cut your own wood and it will warm you twice" From yoni-r at actcom.com Sun Jan 14 10:07:56 2007 From: yoni-r at actcom.com (Yoni Rabkin Katzenell) Date: Sun, 14 Jan 2007 12:07:56 +0200 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: <87ac0mgcdf.fsf@actcom.com> (Yoni Rabkin Katzenell's message of "Sun\, 14 Jan 2007 11\:56\:44 +0200") References: <87ac0mgcdf.fsf@actcom.com> Message-ID: <873b6dhqf7.fsf@actcom.com> Yoni Rabkin Katzenell writes: > Some time ago I added two lines to test.lisp which add a favicon to the > "menu" page. Maybe someone here will find it useful in a Google search. > > You don't actually need the patch, but it is the shortest method of > explaining what to add where. OK... So that did not work. Sorry for the wierd attachment. I'll just paste it right into the mail this time: --- test_original.lisp 2007-01-14 10:56:18.000000000 +0200 +++ test.lisp 2007-01-14 10:55:15.000000000 +0200 @@ -474,6 +474,7 @@ (with-html (:html (:head + (:link :rel "shortcut icon" :href "/hunchentoot/test/favicon.ico" :type "image/x-icon") (:title "Hunchentoot test menu")) (:body (:h2 (str *headline*)) @@ -544,6 +545,11 @@ (make-pathname :name "fz" :type "jpg" :version nil :defaults *this-file*) "image/jpeg") + (create-static-file-dispatcher-and-handler + "/hunchentoot/test/favicon.ico" + (make-pathname :name "favicon" :type "ico" :version nil + :defaults *this-file*) + "image/x-icon") (create-folder-dispatcher-and-handler "/hunchentoot/code/" (make-pathname :name nil :type nil :version nil From jeffrey at cunningham.net Sun Jan 14 14:19:30 2007 From: jeffrey at cunningham.net (Jeffrey Cunningham) Date: Sun, 14 Jan 2007 06:19:30 -0800 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: <873b6dhqf7.fsf@actcom.com> References: <87ac0mgcdf.fsf@actcom.com> <873b6dhqf7.fsf@actcom.com> Message-ID: <20070114141930.GA22141@achilles.olympus.net> On Sun Jan 14, 2007 at 12:07:56PM +0200, Yoni Rabkin Katzenell wrote: > Yoni Rabkin Katzenell writes: > > --- test_original.lisp 2007-01-14 10:56:18.000000000 +0200 > +++ test.lisp 2007-01-14 10:55:15.000000000 +0200 > @@ -474,6 +474,7 @@ > (with-html > (:html > (:head > + (:link :rel "shortcut icon" :href "/hunchentoot/test/favicon.ico" :type "image/x-icon") > (:title "Hunchentoot test menu")) > (:body > (:h2 (str *headline*)) > @@ -544,6 +545,11 @@ > (make-pathname :name "fz" :type "jpg" :version nil > :defaults *this-file*) > "image/jpeg") > + (create-static-file-dispatcher-and-handler > + "/hunchentoot/test/favicon.ico" > + (make-pathname :name "favicon" :type "ico" :version nil > + :defaults *this-file*) > + "image/x-icon") > (create-folder-dispatcher-and-handler > "/hunchentoot/code/" > (make-pathname :name nil :type nil :version nil Wouldn't that execute the CREATE-STATIC-FILE-DISPATCHER-AND-HANDLER and CREATE-FOLDER-DISPATCHER-AND-HANDLER with every page view? It would probably be better to move them outside the function that builds the html so they only execute once when you startup the server. Regards, -Jeff From yoni-r at actcom.com Sun Jan 14 15:11:13 2007 From: yoni-r at actcom.com (Yoni Rabkin Katzenell) Date: Sun, 14 Jan 2007 17:11:13 +0200 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: <20070114141930.GA22141@achilles.olympus.net> (Jeffrey Cunningham's message of "Sun\, 14 Jan 2007 06\:19\:30 -0800") References: <87ac0mgcdf.fsf@actcom.com> <873b6dhqf7.fsf@actcom.com> <20070114141930.GA22141@achilles.olympus.net> Message-ID: <87mz4lfxta.fsf@actcom.com> Jeffrey Cunningham writes: [snip] > Wouldn't that execute the CREATE-STATIC-FILE-DISPATCHER-AND-HANDLER > and CREATE-FOLDER-DISPATCHER-AND-HANDLER with every page view? I can't make sense of the question, sorry. The patch is just a simple link to an image. -- "Cut your own wood and it will warm you twice" From tobia.conforto at linux.it Sun Jan 14 15:27:22 2007 From: tobia.conforto at linux.it (Toby) Date: Sun, 14 Jan 2007 16:27:22 +0100 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: <20070114141930.GA22141@achilles.olympus.net> References: <87ac0mgcdf.fsf@actcom.com> <873b6dhqf7.fsf@actcom.com> <20070114141930.GA22141@achilles.olympus.net> Message-ID: <20070114152721.GF1827@localhost.localdomain> Jeffrey Cunningham wrote: > Wouldn't that execute the CREATE-STATIC-FILE-DISPATCHER-AND-HANDLER > and CREATE-FOLDER-DISPATCHER-AND-HANDLER with every page view? Yoni Rabkin Katzenell wrote: > @@ -474,6 +474,7 @@ > (with-html > ... > @@ -544,6 +545,11 @@ > (create-static-file-dispatcher-and-handler > ... Toby From yoni-r at actcom.com Sun Jan 14 15:44:56 2007 From: yoni-r at actcom.com (Yoni Rabkin Katzenell) Date: Sun, 14 Jan 2007 17:44:56 +0200 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: <20070114152721.GF1827@localhost.localdomain> (Toby's message of "Sun\, 14 Jan 2007 16\:27\:22 +0100") References: <87ac0mgcdf.fsf@actcom.com> <873b6dhqf7.fsf@actcom.com> <20070114141930.GA22141@achilles.olympus.net> <20070114152721.GF1827@localhost.localdomain> Message-ID: <87irf9bojr.fsf@actcom.com> Toby writes: > Jeffrey Cunningham wrote: >> Wouldn't that execute the CREATE-STATIC-FILE-DISPATCHER-AND-HANDLER >> and CREATE-FOLDER-DISPATCHER-AND-HANDLER with every page view? > > Yoni Rabkin Katzenell wrote: >> @@ -474,6 +474,7 @@ >> (with-html >> ... >> @@ -544,6 +545,11 @@ >> (create-static-file-dispatcher-and-handler >> ... That's Dr. Weitz's code. I did not add or modify those. -- "Cut your own wood and it will warm you twice" From edi at agharta.de Sun Jan 14 16:08:20 2007 From: edi at agharta.de (Edi Weitz) Date: Sun, 14 Jan 2007 17:08:20 +0100 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: <87ac0mgcdf.fsf@actcom.com> (Yoni Rabkin Katzenell's message of "Sun, 14 Jan 2007 11:56:44 +0200") References: <87ac0mgcdf.fsf@actcom.com> Message-ID: On Sun, 14 Jan 2007 11:56:44 +0200, Yoni Rabkin Katzenell wrote: > Some time ago I added two lines to test.lisp which add a favicon to > the "menu" page. Maybe someone here will find it useful in a Google > search. > > You don't actually need the patch, but it is the shortest method of > explaining what to add where. Thanks. So, now we need someone to create a favicon.ico from the Hunchentoot logo... :) From edi at agharta.de Sun Jan 14 16:09:00 2007 From: edi at agharta.de (Edi Weitz) Date: Sun, 14 Jan 2007 17:09:00 +0100 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: <20070114141930.GA22141@achilles.olympus.net> (Jeffrey Cunningham's message of "Sun, 14 Jan 2007 06:19:30 -0800") References: <87ac0mgcdf.fsf@actcom.com> <873b6dhqf7.fsf@actcom.com> <20070114141930.GA22141@achilles.olympus.net> Message-ID: On Sun, 14 Jan 2007 06:19:30 -0800, Jeffrey Cunningham wrote: > Wouldn't that execute the CREATE-STATIC-FILE-DISPATCHER-AND-HANDLER > and CREATE-FOLDER-DISPATCHER-AND-HANDLER with every page view? It > would probably be better to move them outside the function that > builds the html so they only execute once when you startup the > server. Huh??? From jeffrey at cunningham.net Sun Jan 14 17:04:50 2007 From: jeffrey at cunningham.net (Jeffrey Cunningham) Date: Sun, 14 Jan 2007 09:04:50 -0800 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: <20070114141930.GA22141@achilles.olympus.net> References: <87ac0mgcdf.fsf@actcom.com> <873b6dhqf7.fsf@actcom.com> <20070114141930.GA22141@achilles.olympus.net> Message-ID: <20070114170450.GA24657@achilles.olympus.net> On Sun Jan 14, 2007 at 06:19:30AM -0800, Jeffrey Cunningham wrote: > On Sun Jan 14, 2007 at 12:07:56PM +0200, Yoni Rabkin Katzenell wrote: > > Yoni Rabkin Katzenell writes: > > > > --- test_original.lisp 2007-01-14 10:56:18.000000000 +0200 > > +++ test.lisp 2007-01-14 10:55:15.000000000 +0200 > > @@ -474,6 +474,7 @@ > > (with-html > > (:html > > (:head > > + (:link :rel "shortcut icon" :href "/hunchentoot/test/favicon.ico" :type "image/x-icon") > > (:title "Hunchentoot test menu")) > > (:body > > (:h2 (str *headline*)) > > @@ -544,6 +545,11 @@ > > (make-pathname :name "fz" :type "jpg" :version nil > > :defaults *this-file*) > > "image/jpeg") > > + (create-static-file-dispatcher-and-handler > > + "/hunchentoot/test/favicon.ico" > > + (make-pathname :name "favicon" :type "ico" :version nil > > + :defaults *this-file*) > > + "image/x-icon") > > (create-folder-dispatcher-and-handler > > "/hunchentoot/code/" > > (make-pathname :name nil :type nil :version nil > > > Wouldn't that execute the CREATE-STATIC-FILE-DISPATCHER-AND-HANDLER > and CREATE-FOLDER-DISPATCHER-AND-HANDLER with every page view? It > would probably be better to move them outside the function that builds > the html so they only execute once when you startup the server. > I Misread the patch above. At the time it looked like the CREATE-STATIC-FILE-DISPATCHER-AND-HANDLER and CREATE-FOLDER-DISPATCHER-AND-HANDLER calls were inside the WITH-HTML form, which didn't make any sense to me. I didn't see the line: > > @@ -544,6 +545,11 @@ separating tht two. My apologies. --Jeff From uvl at htg1.de Sun Jan 14 17:25:09 2007 From: uvl at htg1.de (Uwe von Loh) Date: Sun, 14 Jan 2007 18:25:09 +0100 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: References: <87ac0mgcdf.fsf@actcom.com> Message-ID: <45AA6775.1090709@htg1.de> Edi Weitz wrote: > Thanks. So, now we need someone to create a favicon.ico from the > Hunchentoot logo... :) Look at http://www.htg1.de/hunchentoot/hunchentoot.html Uwe 8-) -------------- next part -------------- A non-text attachment was scrubbed... Name: favicon.ico Type: image/x-icon Size: 326 bytes Desc: not available URL: From uvl at htg1.de Sun Jan 14 17:40:54 2007 From: uvl at htg1.de (Uwe von Loh) Date: Sun, 14 Jan 2007 18:40:54 +0100 Subject: [hunchentoot-devel] favicon again In-Reply-To: <45AA6775.1090709@htg1.de> References: <87ac0mgcdf.fsf@actcom.com> <45AA6775.1090709@htg1.de> Message-ID: <45AA6B26.6080400@htg1.de> Sorry, the 32 x 32 version looked awful. Here is a 16 x 16 favicon.ico -------------- next part -------------- A non-text attachment was scrubbed... Name: favicon.ico Type: image/x-icon Size: 198 bytes Desc: not available URL: From tobia.conforto at linux.it Sun Jan 14 17:47:19 2007 From: tobia.conforto at linux.it (Toby) Date: Sun, 14 Jan 2007 18:47:19 +0100 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: References: <87ac0mgcdf.fsf@actcom.com> Message-ID: <20070114174718.GG1827@localhost.localdomain> Edi Weitz wrote: > Thanks. So, now we need someone to create a favicon.ico from the > Hunchentoot logo... :) Here's my take on the 16x16px format Toby -------------- next part -------------- A non-text attachment was scrubbed... Name: hunchentoot.ico Type: image/x-icon Size: 318 bytes Desc: not available URL: From ch-tbnl at bobobeach.com Sun Jan 14 19:00:42 2007 From: ch-tbnl at bobobeach.com (Cyrus Harmon) Date: Sun, 14 Jan 2007 11:00:42 -0800 Subject: [hunchentoot-devel] favicon.ico patch for test.lisp In-Reply-To: <20070114174718.GG1827@localhost.localdomain> References: <87ac0mgcdf.fsf@actcom.com> <20070114174718.GG1827@localhost.localdomain> Message-ID: I like it, but some color might be nice :) On Jan 14, 2007, at 9:47 AM, Toby wrote: > Edi Weitz wrote: >> Thanks. So, now we need someone to create a favicon.ico from the >> Hunchentoot logo... :) > > Here's my take on the 16x16px format > > > Toby > > _______________________________________________ > tbnl-devel site list > tbnl-devel at common-lisp.net > http://common-lisp.net/mailman/listinfo/tbnl-devel From edi at agharta.de Sun Jan 14 19:01:27 2007 From: edi at agharta.de (Edi Weitz) Date: Sun, 14 Jan 2007 20:01:27 +0100 Subject: [hunchentoot-devel] New release 0.4.13 Message-ID: ChangeLog: Version 0.4.13 2007-01-14 Added favicon.ico to example website (thanks to Yoni Rabkin Katzenell, Toby, and Uwe von Loh) Download: http://weitz.de/files/hunchentoot.tar.gz Cheers, Edi. From jeffrey at cunningham.net Mon Jan 15 04:12:35 2007 From: jeffrey at cunningham.net (Jeffrey Cunningham) Date: Sun, 14 Jan 2007 20:12:35 -0800 Subject: [hunchentoot-devel] Re: [slime-devel] slime-texi patch In-Reply-To: <8757cb490701141954y42735fa0i2b14a6034e9eaba4@mail.gmail.com> References: <8757cb490701141710v7ce8f4dcy9f949f1a2bc736fc@mail.gmail.com> <20070115023523.GA3324@achilles.olympus.net> <8757cb490701141954y42735fa0i2b14a6034e9eaba4@mail.gmail.com> Message-ID: <20070115041235.GA5049@achilles.olympus.net> Hmmm. This is strange. I was given commit privileges specifically for doing extensive work on doc/slime.texi. CVS lets me log in alright and seems to accept the changes - prompts me for comments and everything. But I just checked out a fresh copy and none of the changes I made this month (several sessions) are there. And yet, the changes I made in December are there (for example, the image on the front page). I don't know what to make of it. I'm going to post a patch to the list which incorporates the changes you made plus those I've made. (attached) Here's a changelog entry for it: 2007-01-14 Jeff Cunningham * doc/slime.texi: Update of function/key index with links. --Jeff On Sun Jan 14, 2007 at 07:54:38PM -0800, Bill Clementson wrote: > Hi Jeff, > > On 1/14/07, Jeffrey Cunningham wrote: > >On Sun Jan 14, 2007 at 05:10:32PM -0800, Bill Clementson wrote: > >> Attached is a patch for slime-texi. Here's the changelog entry: > >> > >> 2007-01-14 Bill Clementson > >> > >> * doc/slime.texi: Cleanup of documentation typos/errors. > > > >Hi Bill; > > > >I noticed your patch is applied against doc/slime.texi from Jan 1 > >whereas I checked a number of changes into CVS for that file on Jan > >11. Should I do something beyond email the list that I have made > >changes? I am unfamiliar with what is customary in this list. Should I > >also send out a patch as you have done? > > > >I applied your patch to my current version and it worked fine. > > I did a cvs update before I made the changes to slime.texi, so my > patch should be against the latest version of slime.texi. Looking at > the changelog, it appears that the last patch to slime.texi was made > on 2006-12-24, so I don't know what happened to your changes. I just > did a "cvs co slime" as well to see what I got on a fresh install and > the date on slime.texi is also 2006-12-24. Perhaps your changes were > never applied? Since there are a limited number of people with commit > privileges, it's generally a good idea to double-check that any patch > that you email in is actually applied as sometimes they "fall through > the cracks". > > -- > Bill Clementson > -------------- next part -------------- 13c13 < @set UPDATED @code{$Date: 2007/01/11 06:3:15 $} --- > @set UPDATED @code{$Date: 2006/12/24 13:43:15 $} 161c161 < OpenMCL, version 0.14.3 or newer --- > OpenMCL, version 0.14.3 274c274 < paths. --- > path. 360,363d359 < A (near) complete list of the default keybindings set by @SLIME{} is < given in an appendix (@pxref{Index to Key Bindings}), with links to < their descriptions. < 377c373 < has a built-in default so that typing a prefix followed by @kbd{C-h} --- > has a builtin default so that typing a prefix followed by @kbd{C-h} 382c378 < You can assign or change default key bindings globally using the @code{global-set-key} --- > You can assign or change default key bindings using the @code{global-set-key} 385c381 < (global-set-key "\C-c s" 'slime-selector) --- > (global-set-key "\C-cs" 'slime-selector) 390,399d385 < Alternatively, if you want to assign or change a key binding in just a < particular slime mode, you can use the @code{global-set-key} function in < your @file{~/.emacs} file like this: < @example < (define-key slime-repl-mode-map (kbd "C-c ;") 'slime-insert-balanced-comments) < @end example < @noindent < which binds @kbd{C-c ;} to the function < @code{slime-insert-balanced-comments} in the REPL buffer. < 463c449 < to Functions}) and by key binding (@pxref{Index to Key Bindings}). --- > to Functions}) and by function (@pxref{Index to Key Bindings}). 655c641 < with no built-in @acronym{XREF} support @SLIME{} queries a portable --- > with no builtin @acronym{XREF} support @SLIME{} queries a portable 684c670 < Go to the cross-referenced location at point. --- > Goto the cross-referenced location at point. 723d708 < @itemx M-* 1117a1103 > @anchor{slime-repl-next-matching-input} 1118a1105 > @anchor{slime-repl-previous-matching-input} 1121,1125d1107 < @code{slime-repl-next-input, slime-repl-previous-input}@* < Go to next/previous in command history. < < @anchor{slime-repl-next-matching-input} < @anchor{slime-repl-previous-matching-input} 1128,1133c1110,1112 < @code{slime-repl-next-matching-input, slime-repl-previous-matching-input}@* < Search forward/reverse through command history with regex < < @c @code{slime-repl-@{next,previous@}-input}@* < @c @code{slime-repl-@{next,previous@}-matching-input}@* < @c @code{comint}-style input history commands. --- > @code{slime-repl-@{next,previous@}-input}@* > @code{slime-repl-@{next,previous@}-matching-input}@* > @code{comint}-style input history commands. 1163,1164c1142,1143 < compiling and loading Lisp systems. The set of shortcuts is listed < below, and you can also use the @code{help} --- > compiling and loading Lisp systems. The exact set of shortcuts is not > currently documented in this manual, but you can use the @code{help} 1167,1225d1145 < @table @kbd < @item change-directory (aka !d, cd) < Change the current directory. < < @item change-package (aka !p) < Change the current package. < < @item compile-and-load (aka cl) < Compile (if neccessary) and load a lisp file. < < @item compile-system < Compile (but not load) an ASDF system. < < @item defparameter (aka !) < Define a new global, special, variable. < < @item force-compile-system < Recompile (but not load) an ASDF system. < < @item force-load-system < Recompile and load an ASDF system. < < @item help (aka ?) < Display the help. < < @item load-system < Compile (as needed) and load an ASDF system. < < @item pop-directory (aka -d) < Pop the current directory. < < @item pop-package (aka -p) < Pop the top of the package stack. < < @item push-directory (aka +d, pushd) < Push a new directory onto the directory stack. < < @item push-package (aka +p) < Push a package onto the package stack. < < @item pwd < Show the current directory. < < @item quit < Quit the current Lisp. < < @item resend-form < Resend the last form. < < @item restart-inferior-lisp < Restart *inferior-lisp* and reconnect SLIME. < < @item sayoonara < Quit all Lisps and close all SLIME buffers. < < @end table < < < 1339,1341c1259 < @fcnanchor{in-sldb-face} < Return STRING propertised with face sldb-NAME-face. < --- > @c @anchor{slime-interactive-eval} 1499c1417 < Disconnect all connections. --- > Disconnect all connextions. 1626d1543 < @fcnanchor{slime-mode-hook} 1707c1624 < capabilities of your Lisp system. The general order of preference is --- > capabilities your Lisp system. The general order of preference is 1830c1747 < image, se we're not gonig to talk about it} and we'll only have one --- > image, se we're not gonig to talk about it} and we'll only have on 1938c1855 < often than not this is inconvenient. So, if you want code such as this: --- > often than not this inconvenient. So, if you want code such as this: 2011d1927 < These are the keybindings set by default in Slime. 2061c1977 < @kbdindex{M- at comma{}, slime-pop-find-definition-stack} --- > @kbdindex{M-\,, slime-pop-find-definition-stack} 2072,2080c1988,1989 < These functions are all available (when relevant). To find the < keybinding (if there is one) refer to the function description. < < @c Note to editors: @fcnindex{...} lines commented out below are place holders < @c ---------------- < @c They have yet to be documented < @c Please feel free to add descriptions in the text where appropriate, add the < @c appropriate anchors and uncomment them. < --- > @c Note: the functions commented out below are in slime.el but as > @c yet unreferenced (and may or may not be -jkc-). 2084c1993,2012 < @fcnindex{in-sldb-face} --- > @c @fcnindex{sldb-mode-hook} > @c @fcnindex{slime-mode-hook} > @c @fcnindex{slime-repl-mode-hook} > @c @fcnindex{compile} > @c @fcnindex{compile-defun} > @c @fcnindex{fboundp} > @c @fcnindex{def-sldb-face} > @c @fcnindex{def-sldb-faces} > @c @fcnindex{def-slime-selector-method} > @c @fcnindex{def-slime-test} > @c @fcnindex{define-sldb-invoke-restart-key} > @c @fcnindex{define-sldb-invoke-restart-keys} > @c @fcnindex{define-slime-dialect} > @c @fcnindex{defslime-repl-shortcut} > @c @fcnindex{destructure-case} > @c @fcnindex{in-sldb-face} > @c @fcnindex{inferior-slime-closing-return} > @c @fcnindex{inferior-slime-indent-line} > @c @fcnindex{inferior-slime-input-complete-p} > @c @fcnindex{inferior-slime-return} 2139d2066 < @c @fcnindex{sldb-mode-hook} 2162,2167d2088 < < < @c @fcnindex{inferior-slime-closing-return} < @c @fcnindex{inferior-slime-indent-line} < @c @fcnindex{inferior-slime-mode} < @c @fcnindex{inferior-slime-return} 2168a2090,2095 > @c @fcnindex{slime-accept-process-output} > @c @fcnindex{slime-activate-font-lock-magic} > @c @fcnindex{slime-add-face} > @c @fcnindex{slime-add-presentation-properties} > @c @fcnindex{slime-after-change-function} > @c @fcnindex{slime-alistify} 2171a2099 > @c @fcnindex{slime-apropos-summary} [internal] 2172a2101,2107 > @c @fcnindex{slime-arglist-specializers} > @c @fcnindex{slime-at-top-level-p} > @c @fcnindex{slime-autodoc} [internal] > @c @fcnindex{slime-autodoc-global-at-point} [internal] > @c @fcnindex{slime-autodoc-message} [internal] > @c @fcnindex{slime-autodoc-message-dimensions} [internal] > @c @fcnindex{slime-autodoc-message-ok-p} [internal] 2174c2109,2113 < @c @fcnindex{slime-autodoc-start-timer} --- > @c @fcnindex{slime-autodoc-pre-command-refresh-echo-area} [internal] > @c @fcnindex{slime-autodoc-start-timer} ?? > @c @fcnindex{slime-autodoc-stop-timer} [internal] > @c @fcnindex{slime-autodoc-thing-at-point} [internal] > @c @fcnindex{slime-autodoc-timer-hook} [internal] 2176a2116,2120 > @c @fcnindex{slime-batch-test} > @c @fcnindex{slime-beginning-of-comment} [internal] > @c @fcnindex{slime-beginning-of-list} [internal] > @c @fcnindex{slime-beginning-of-symbol} [internal] > @c @fcnindex{slime-bogus-completion-alist} 2178a2123,2125 > @c @fcnindex{slime-buffer-substring-with-reified-output} > @c @fcnindex{slime-busy-p} > @c @fcnindex{slime-bytecode-stale-p} 2179a2127,2128 > @c @fcnindex{slime-call-describer} > @c @fcnindex{slime-call-with-browser-setup} 2180a2130,2133 > @c @fcnindex{slime-changelog-date} > @c @fcnindex{slime-cheat-sheet} > @c @fcnindex{slime-cheat-sheet-table} > @c @fcnindex{slime-check} 2181a2135,2144 > @c @fcnindex{slime-check-connected} > @c @fcnindex{slime-check-eval-in-emacs-enabled} > @c @fcnindex{slime-check-sldb-level} > @c @fcnindex{slime-check-top-level} > @c @fcnindex{slime-choose-connection} > @c @fcnindex{slime-choose-overlay-for-sexp} > @c @fcnindex{slime-choose-overlay-region} > @c @fcnindex{slime-cl-symbol-external-ref-p} > @c @fcnindex{slime-cl-symbol-name} > @c @fcnindex{slime-cl-symbol-package} 2183a2147,2150 > @c @fcnindex{slime-coding-system-cl-name} > @c @fcnindex{slime-coding-system-mulibyte-p} > @c @fcnindex{slime-compilation-finished} > @c @fcnindex{slime-compilation-finished-continuation} 2187a2155 > @c @fcnindex{slime-compile-string} [internal] 2189a2158 > @c @fcnindex{slime-compiler-notes} [internal] 2193a2163,2165 > @c @fcnindex{slime-compiler-notes-to-tree} [internal] > @c @fcnindex{slime-complete-delay-restoration} [internal] > @c @fcnindex{slime-complete-forget-window-configuration} [internal] 2194a2167,2169 > @c @fcnindex{slime-complete-maybe-restore-window-configuration} [internal] > @c @fcnindex{slime-complete-maybe-save-window-configuration} [internal] > @c @fcnindex{slime-complete-restore-window-configuration} [internal] 2195a2171,2175 > @c @fcnindex{slime-complete-symbol*} [internal] > @c @fcnindex{slime-complete-symbol*-fancy-bit} [internal] > @c @fcnindex{slime-completion-window-active-p} [internal] > @c @fcnindex{slime-completions} [internal] > @c @fcnindex{slime-completions-for-keyword} [internal] 2196a2177,2180 > @c @fcnindex{slime-connected-p} [internal] > @c @fcnindex{slime-connection} [internal] > @c @fcnindex{slime-connection-at-point} [internal] > @c @fcnindex{slime-connection-close-hook} [internal] 2199c2183,2195 < @c @fcnindex{slime-copy-presentation-at-point} --- > @c @fcnindex{slime-connection-port} [internal] > @c @fcnindex{slime-control-modified-char} > @c @fcnindex{slime-copy-or-inspect-presentation-at-mouse} > @c @fcnindex{slime-copy-presentation-at-mouse} > @c @fcnindex{slime-create-message-window} > @c @fcnindex{slime-create-note-overlay} > @c @fcnindex{slime-create-test-results-buffer} > @c @fcnindex{slime-current-connection} [internal] > @c @fcnindex{slime-current-package} [internal] > @c @fcnindex{slime-def-connection-var} > @c @fcnindex{slime-define-keys} > @c @fcnindex{slime-defun-at-point} > @c @fcnindex{slime-delete-hidden-outline-text} 2200a2197 > @c @fcnindex{slime-describe-presentation-at-mouse} 2203a2201,2208 > @c @fcnindex{slime-dismiss-temp-buffer} > @c @fcnindex{slime-dispatch-event} > @c @fcnindex{slime-display-buffer-region} > @c @fcnindex{slime-display-completion-list} > @c @fcnindex{slime-display-eval-result} > @c @fcnindex{slime-display-message} > @c @fcnindex{slime-display-output-buffer} > @c @fcnindex{slime-display-xref-buffer} 2204a2210,2213 > @c @fcnindex{slime-draw-connection-list} > @c @fcnindex{slime-easy-menu} > @c @fcnindex{slime-echo-arglist} > @c @fcnindex{slime-ed} 2209a2219 > @c @fcnindex{slime-edit-value-callback} 2211,2212c2221,2228 < @c @fcnindex{slime-edit-value-mode} < @fcnindex{slime-ensure-typeout-frame} --- > @c @fcnindex{slime-emacs-20-p} > @c @fcnindex{slime-enclosing-operator-names} > @c @fcnindex{slime-end-of-symbol} > @c @fcnindex{slime-ensure-presentation-overlay} > @c @fcnindex{slime-ensure-typeout-frame} > @c @fcnindex{slime-etags-definitions} > @c @fcnindex{slime-eval} > @c @fcnindex{slime-eval-async} 2214a2231,2233 > @c @fcnindex{slime-eval-describe} > @c @fcnindex{slime-eval-feature-conditional} > @c @fcnindex{slime-eval-for-lisp} 2216a2236,2238 > @c @fcnindex{slime-eval-macroexpand} > @c @fcnindex{slime-eval-macroexpand-inplace} > @c @fcnindex{slime-eval-print} 2218a2241,2268 > @c @fcnindex{slime-eval-with-transcript} > @c @fcnindex{slime-events-buffer} > @c @fcnindex{slime-execute-tests} > @c @fcnindex{slime-expand-abbreviations-and-complete} > @c @fcnindex{slime-expand-class-node} > @c @fcnindex{slime-expand-xrefs} > @c @fcnindex{slime-extract-context} > @c @fcnindex{slime-face-inheritance-possible-p} > @c @fcnindex{slime-fetch-browsable-xrefs} > @c @fcnindex{slime-filter-buffers} > @c @fcnindex{slime-find-asd} [internal] > @c @fcnindex{slime-find-buffer-package} [internal] > @c @fcnindex{slime-find-coding-system} [internal] > @c @fcnindex{slime-find-connection-by-name} [internal] > @c @fcnindex{slime-find-filename-translators} [internal] > @c @fcnindex{slime-find-next-note} [internal] > @c @fcnindex{slime-find-note} [internal] > @c @fcnindex{slime-find-previous-note} [internal] > @c @fcnindex{slime-first-change-hook} > @c @fcnindex{slime-fontify-string} > @c @fcnindex{slime-forward-blanks} > @c @fcnindex{slime-forward-positioned-source-path} > @c @fcnindex{slime-forward-reader-comment} > @c @fcnindex{slime-forward-reader-conditional} > @c @fcnindex{slime-forward-sexp} > @c @fcnindex{slime-forward-source-path} > @c @fcnindex{slime-frame-windows} > @c @fcnindex{slime-from-lisp-filename} 2222,2225c2272,2292 < @c @fcnindex{slime-fuzzy-next} < @c @fcnindex{slime-fuzzy-prev} < @c @fcnindex{slime-fuzzy-select} < @c @fcnindex{slime-fuzzy-select/mouse} --- > @c @fcnindex{slime-fuzzy-choices-buffer} [internal] > @c @fcnindex{slime-fuzzy-completions} [internal] > @c @fcnindex{slime-fuzzy-done} [internal] > @c @fcnindex{slime-fuzzy-insert} [internal] > @c @fcnindex{slime-fuzzy-insert-completion-choice} [internal] > @c @fcnindex{slime-fuzzy-insert-from-point} [internal] > @c @fcnindex{slime-fuzzy-maybe-restore-window-configuration} [internal] > @c @fcnindex{slime-fuzzy-next} ??? > @c @fcnindex{slime-fuzzy-post-command-hook} [internal] > @c @fcnindex{slime-fuzzy-prev} ??? > @c @fcnindex{slime-fuzzy-save-window-configuration} [internal] > @c @fcnindex{slime-fuzzy-select} ??? > @c @fcnindex{slime-fuzzy-select/mouse} ??? > @c @fcnindex{slime-fuzzy-selected} [internal] > @c @fcnindex{slime-fuzzy-window-configuration-change} [internal] > @c @fcnindex{slime-fuzzy-window-configuration-change-add-hook} [internal] > @c @fcnindex{slime-generate-connection-name} > @c @fcnindex{slime-get-arglist} [internal] > @c @fcnindex{slime-get-cached-autodoc} [internal] > @c @fcnindex{slime-get-fuzzy-buffer} [internal] > @c @fcnindex{slime-global-variable-name-p} [internal] 2226a2294,2299 > @c @fcnindex{slime-goto-definition} ??? > @c @fcnindex{slime-goto-definition-other-window} [internal] > @c @fcnindex{slime-goto-location-buffer} [internal] > @c @fcnindex{slime-goto-location-position} [internal] > @c @fcnindex{slime-goto-next-xref} [internal] > @c @fcnindex{slime-goto-source-location} [internal] 2227a2301,2302 > @c @fcnindex{slime-group-similar} > @c @fcnindex{slime-handle-indentation-update} 2228a2304,2308 > @c @fcnindex{slime-hide-inferior-lisp-buffer} [internal] > @c @fcnindex{slime-highlight-edits} > @c @fcnindex{slime-highlight-edits-compile-hook} > @c @fcnindex{slime-highlight-edits-init-buffer} > @c @fcnindex{slime-highlight-edits-reset-buffer} 2230a2311 > @c @fcnindex{slime-in-expression-p} 2231a2313,2316 > @c @fcnindex{slime-inferior-connect} [internal] > @c @fcnindex{slime-inferior-lisp-args} [internal] > @c @fcnindex{slime-init-command} > @c @fcnindex{slime-init-connection-state} 2232a2318,2320 > @c @fcnindex{slime-init-output-buffer} > @c @fcnindex{slime-init-xref-buffer} > @c @fcnindex{slime-input-complete-p} 2234a2323,2326 > @c @fcnindex{slime-insert-presentation} > @c @fcnindex{slime-insert-transcript-delimiter} > @c @fcnindex{slime-insert-xrefs} > @c @fcnindex{slime-inside-comment-p} 2235a2328,2329 > @c @fcnindex{slime-inspect-presentation-at-mouse} > @c @fcnindex{slime-inspector-buffer} 2237a2332,2333 > @c @fcnindex{slime-inspector-fontify} > @c @fcnindex{slime-inspector-insert-ispec} 2239a2336,2340 > @c @fcnindex{slime-inspector-operate-on-click} > @fcnindex{slime-inspector-operate-on-point} > @fcnindex{slime-inspector-pop} > @c @fcnindex{slime-inspector-pprint} > @c @fcnindex{slime-inspector-previous-inspectable-object} 2243a2345,2354 > @c @fcnindex{slime-intersperse} > @c @fcnindex{slime-io-speed-test} > @c @fcnindex{slime-isearch} > @c @fcnindex{slime-isearch-with-function} > @c @fcnindex{slime-keys} > @c @fcnindex{slime-kill-all-buffers} > @c @fcnindex{slime-last-expression} > @c @fcnindex{slime-length>} > @c @fcnindex{slime-lisp-mode-hook} > @c @fcnindex{slime-list-all-repl-shortcuts} 2248c2359 < @c @fcnindex{slime-list-repl-shortcuts} --- > @c @fcnindex{slime-list-repl-short-cuts} 2250a2362 > @c @fcnindex{slime-load-file-set-package} 2251a2364,2366 > @c @fcnindex{slime-log-event} > @c @fcnindex{slime-lookup-lisp-implementation} > @c @fcnindex{slime-lookup-shortcut} 2253a2369 > @c @fcnindex{slime-macroexpand-again} 2254a2371 > @c @fcnindex{slime-macroexpand-all-inplace} 2255a2373,2374 > @c @fcnindex{slime-make-net-buffer} > @c @fcnindex{slime-make-tramp-file-name} 2257c2376,2404 < @fcnindex{slime-mode} --- > @c @fcnindex{slime-make-variables-buffer-local} > @c @fcnindex{slime-mark-input-start} > @c @fcnindex{slime-mark-output-end} > @c @fcnindex{slime-mark-output-start} > @c @fcnindex{slime-mark-presentation-end} > @c @fcnindex{slime-mark-presentation-end-handler} > @c @fcnindex{slime-mark-presentation-start} > @c @fcnindex{slime-mark-presentation-start-handler} > @c @fcnindex{slime-maybe-complete-as-filename} > @c @fcnindex{slime-maybe-display-output-buffer} > @c @fcnindex{slime-maybe-list-compiler-notes} > @c @fcnindex{slime-maybe-show-xrefs-for-notes} > @c @fcnindex{slime-maybe-start-lisp} > @c @fcnindex{slime-menu-choices-for-presentation} > @c @fcnindex{slime-merge-note-into-overlay} > @c @fcnindex{slime-merge-notes} > @c @fcnindex{slime-merge-notes-for-display} > @c @fcnindex{slime-message} > @c @fcnindex{slime-minibuffer-respecting-message} > @c @fcnindex{slime-most-severe} > @c @fcnindex{slime-net-close} > @c @fcnindex{slime-net-connect} > @c @fcnindex{slime-net-decode-length} > @c @fcnindex{slime-net-encode-length} > @c @fcnindex{slime-net-filter} > @c @fcnindex{slime-net-have-input-p} > @c @fcnindex{slime-net-read} > @c @fcnindex{slime-net-send} > @c @fcnindex{slime-net-sentinel} 2261a2409,2437 > @c @fcnindex{slime-note-at-point} > @c @fcnindex{slime-note-count-string} > @c @fcnindex{slime-note-has-location-p} > @c @fcnindex{slime-note-overlay-p} > @c @fcnindex{slime-note-overlays-at-point} > @c @fcnindex{slime-note.location} > @c @fcnindex{slime-note.message} > @c @fcnindex{slime-note.references} > @c @fcnindex{slime-note.severity} > @c @fcnindex{slime-note.short-message} > @c @fcnindex{slime-notes-in-same-location-p} > @c @fcnindex{slime-one-line-ify} > @c @fcnindex{slime-oneliner} > @c @fcnindex{slime-only-whitespace-p} > @c @fcnindex{slime-oos} > @c @fcnindex{slime-open-inspector} > @c @fcnindex{slime-open-stream-to-lisp} > @c @fcnindex{slime-output-buffer} > @c @fcnindex{slime-output-filter} > @c @fcnindex{slime-overlay-note} > @c @fcnindex{slime-parse-context} > @c @fcnindex{slime-parse-context} > @c @fcnindex{slime-parse-extended-operator-name} > @c @fcnindex{slime-parse-extended-operator-name/apply} > @c @fcnindex{slime-parse-extended-operator-name/cerror} > @c @fcnindex{slime-parse-extended-operator-name/defmethod} > @c @fcnindex{slime-parse-extended-operator-name/make-instance} > @c @fcnindex{slime-parse-toplevel-form} > @c @fcnindex{slime-pattern-path} 2262a2439 > @c @fcnindex{slime-point-moves-p} 2263a2441,2442 > @c @fcnindex{slime-pop-to-other-window} > @c @fcnindex{slime-post-command-hook} 2264a2444,2449 > @c @fcnindex{slime-pprint-event} > @c @fcnindex{slime-pre-command-hook} > @c @fcnindex{slime-presentation-around-click} > @c @fcnindex{slime-presentation-around-or-before-point} > @c @fcnindex{slime-presentation-around-point} > @c @fcnindex{slime-presentation-expression} 2265a2451,2455 > @c @fcnindex{slime-presentation-start-p} > @c @fcnindex{slime-presentation-stop-p} > @c @fcnindex{slime-presentation-whole-p} > @c @fcnindex{slime-presentations-around-point} > @c @fcnindex{slime-preserve-zmacs-region} 2266a2457,2458 > @c @fcnindex{slime-pretty-package-name} > @c @fcnindex{slime-pretty-print-presentation-at-mouse} 2267a2460,2466 > @c @fcnindex{slime-prin1-to-string} > @c @fcnindex{slime-print-apropos} > @c @fcnindex{slime-print-check-error} > @c @fcnindex{slime-print-check-failed} > @c @fcnindex{slime-print-check-ok} > @c @fcnindex{slime-process} > @c @fcnindex{slime-process-available-input} 2271a2471,2476 > @c @fcnindex{slime-propertize-region} > @c @fcnindex{slime-property-bounds} > @c @fcnindex{slime-property-position} > @c @fcnindex{slime-push-definition-stack} > @c @fcnindex{slime-qualify-cl-symbol} > @c @fcnindex{slime-qualify-cl-symbol-name} 2274a2480,2481 > @c @fcnindex{slime-quit-sentinel} > @c @fcnindex{slime-random-words-of-encouragement} 2275a2483,2494 > @c @fcnindex{slime-read-from-minibuffer} > @c @fcnindex{slime-read-interactive-args} > @c @fcnindex{slime-read-object} > @c @fcnindex{slime-read-package-name} > @c @fcnindex{slime-read-port-and-connect} > @c @fcnindex{slime-read-swank-port} > @c @fcnindex{slime-read-symbol-name} > @c @fcnindex{slime-read-system-name} > @c @fcnindex{slime-read-test-name} > @c @fcnindex{slime-reading-p} > @c @fcnindex{slime-recenter-window} > @c @fcnindex{slime-recently-visited-buffer} 2277c2496,2497 < @c @fcnindex{slime-register-lisp-implementation} --- > @c @fcnindex{slime-region-for-defun-at-point} > @c @fcnindex{slime-reify-old-output} 2278a2499 > @c @fcnindex{slime-reinitialize-inferior-lisp-p} [internal] 2279a2501 > @c @fcnindex{slime-remove-edits} 2280a2503,2504 > @c @fcnindex{slime-remove-old-overlays} > @c @fcnindex{slime-remove-presentation-properties} 2281a2506,2508 > @c @fcnindex{slime-repl-abort-read} > @c @fcnindex{slime-repl-add-to-input-history} > @c @fcnindex{slime-repl-at-prompt-end-p} 2283a2511,2512 > @c @fcnindex{slime-repl-buffer} > @c @fcnindex{slime-repl-call-with-handler} 2287,2290c2516,2517 < @c @fcnindex{slime-repl-compile-and-load} < @c @fcnindex{slime-repl-compile-system} < @c @fcnindex{slime-repl-compile/force-system} < @c @fcnindex{slime-repl-defparameter} --- > @c @fcnindex{slime-repl-current-input} > @c @fcnindex{slime-repl-delete-current-input} 2293,2294c2520,2532 < @c @fcnindex{slime-repl-load-system} < @c @fcnindex{slime-repl-load/force-system} --- > @c @fcnindex{slime-repl-eval-string} > @c @fcnindex{slime-repl-find-prompt} > @c @fcnindex{slime-repl-grab-old-input} > @c @fcnindex{slime-repl-grab-old-output} > @c @fcnindex{slime-repl-history-replace} > @c @fcnindex{slime-repl-in-input-area-p} > @c @fcnindex{slime-repl-input-line-beginning-position} > @c @fcnindex{slime-repl-insert-prompt} > @c @fcnindex{slime-repl-insert-result} > @c @fcnindex{slime-repl-kill-input} > @c @fcnindex{slime-repl-load-history} > @c @fcnindex{slime-repl-matching-input-regexp} > @c @fcnindex{slime-repl-merge-histories} 2295a2534 > @c @fcnindex{slime-repl-move-output-mark-before-prompt} 2300,2301c2539 < @c @fcnindex{slime-repl-pop-directory} < @c @fcnindex{slime-repl-pop-packages} --- > @c @fcnindex{slime-repl-position-in-history} 2305,2306d2542 < @c @fcnindex{slime-repl-push-directory} < @c @fcnindex{slime-repl-push-package} 2308c2544,2548 < @c @fcnindex{slime-repl-read-mode} --- > @c @fcnindex{slime-repl-read-history} > @c @fcnindex{slime-repl-read-history-filename} > @c @fcnindex{slime-repl-read-string} > @c @fcnindex{slime-repl-recenter-if-needed} > @c @fcnindex{slime-repl-replace-input} 2309a2550,2557 > @c @fcnindex{slime-repl-return-string} > @c @fcnindex{slime-repl-safe-load-history} > @c @fcnindex{slime-repl-safe-save-merged-history} > @c @fcnindex{slime-repl-save-all-histories} > @c @fcnindex{slime-repl-save-history} > @c @fcnindex{slime-repl-save-merged-history} > @c @fcnindex{slime-repl-send-input} > @c @fcnindex{slime-repl-send-string} 2311c2559,2561 < @c @fcnindex{slime-repl-shortcut-help} --- > @c @fcnindex{slime-repl-show-abort} > @c @fcnindex{slime-repl-show-maximum-output} > @c @fcnindex{slime-repl-update-banner} 2312a2563 > @c @fcnindex{slime-reset-repl-markers} 2315c2566,2573 < @c @fcnindex{slime-restart-inferior-lisp-aux} --- > @c @fcnindex{slime-restart-sentinel} [internal] > @c @fcnindex{slime-run-one-test} > @c @fcnindex{slime-run-tests} > @c @fcnindex{slime-run-when-idle} > @c @fcnindex{slime-safe-encoding-p} > @c @fcnindex{slime-same-line-p} > @c @fcnindex{slime-save-some-lisp-buffers} > @c @fcnindex{slime-scheme-mode-hook} 2317c2575,2581 < @c @fcnindex{slime-select-lisp-implementation} --- > @c @fcnindex{slime-scratch-buffer} > @c @fcnindex{slime-search-call-site} > @c @fcnindex{slime-search-method-location} > @c @fcnindex{slime-search-property-change-fn} > @c @fcnindex{slime-search-suppressed-forms} > @c @fcnindex{slime-secret} > @c @fcnindex{slime-select-connection} 2318a2583 > @c @fcnindex{slime-send} 2319a2585 > @c @fcnindex{slime-set-connection-info} 2320a2587 > @c @fcnindex{slime-set-inferior-process} 2321a2589,2607 > @c @fcnindex{slime-set-state} > @c @fcnindex{slime-set-truncate-lines} > @c @fcnindex{slime-setup-command-hooks} > @c @fcnindex{slime-setup-connection} > @c @fcnindex{slime-setup-first-change-hook} > @c @fcnindex{slime-severity-face} > @c @fcnindex{slime-severity-label} > @c @fcnindex{slime-sexp-at-point} > @c @fcnindex{slime-sexp-at-point-or-error} > @c @fcnindex{slime-shared-lisp-mode-hook} > @c @fcnindex{slime-show-apropos} > @c @fcnindex{slime-show-buffer-position} > @c @fcnindex{slime-show-definitions} > @c @fcnindex{slime-show-description} > @c @fcnindex{slime-show-last-output} > @c @fcnindex{slime-show-last-output-region} > @c @fcnindex{slime-show-note} > @c @fcnindex{slime-show-note-counts} > @c @fcnindex{slime-show-source-location} 2322a2609,2612 > @c @fcnindex{slime-show-xrefs} > @c @fcnindex{slime-simple-complete-symbol} > @c @fcnindex{slime-simple-completions} > @c @fcnindex{slime-sldb-level=} 2324a2615,2617 > @c @fcnindex{slime-start-lisp} > @c @fcnindex{slime-start-swank-server} > @c @fcnindex{slime-swank-port-file} 2325a2619,2624 > @c @fcnindex{slime-switch-to-scratch-buffer} > @c @fcnindex{slime-symbol-at-point} > @c @fcnindex{slime-symbol-end-pos} > @c @fcnindex{slime-symbol-name-at-point} > @c @fcnindex{slime-symbol-start-pos} > @c @fcnindex{slime-sync} 2327c2626 < @c @fcnindex{slime-temp-buffer-mode} --- > @c @fcnindex{slime-sync-to-top-level} 2328a2628,2633 > @c @fcnindex{slime-temporarily-highlight-note} > @c @fcnindex{slime-test-expect} > @c @fcnindex{slime-test-failure} > @c @fcnindex{slime-test-heading} > @c @fcnindex{slime-test-message} > @c @fcnindex{slime-test-should-fail-p} 2331c2636 < @c @fcnindex{slime-thread-control-mode} --- > @c @fcnindex{slime-thread-insert} 2333a2639,2640 > @c @fcnindex{slime-to-feature-keyword} > @c @fcnindex{slime-to-lisp-filename} 2335a2643,2659 > @c @fcnindex{slime-trace-query} > @c @fcnindex{slime-tree-at-point} > @c @fcnindex{slime-tree-decoration} > @c @fcnindex{slime-tree-default-printer} > @c @fcnindex{slime-tree-delete} > @c @fcnindex{slime-tree-for-note} > @c @fcnindex{slime-tree-for-severity} > @c @fcnindex{slime-tree-indent-item} > @c @fcnindex{slime-tree-insert} > @c @fcnindex{slime-tree-insert-decoration} > @c @fcnindex{slime-tree-insert-list} > @c @fcnindex{slime-tree-insert-references} > @c @fcnindex{slime-tree-leaf-p} > @c @fcnindex{slime-tree-print-with-references} > @c @fcnindex{slime-tree-toggle} > @c @fcnindex{slime-typeout-active-p} > @c @fcnindex{slime-typeout-message} 2336a2661 > @c @fcnindex{slime-underline-color} 2338a2664 > @c @fcnindex{slime-update-autodoc-cache} 2340a2667,2672 > @c @fcnindex{slime-update-modeline-package} > @c @fcnindex{slime-urge-bytecode-recompile} > @c @fcnindex{slime-use-sigint-for-interrupt} > @c @fcnindex{slime-user-first-name} > @c @fcnindex{slime-visit-source-path} > @c @fcnindex{slime-wait-condition} 2347,2348c2679,2685 < @c @fcnindex{slime-xref-mode} < @c @fcnindex{slime-xref-quit} --- > @c @fcnindex{slime-window-config-fingerprint} > @c @fcnindex{slime-with-output-end-mark} > @c @fcnindex{slime-with-rigid-indentation} > @c @fcnindex{slime-write-string} > @c @fcnindex{slime-xref} > @c @fcnindex{slime-xref-buffer} > @c @fcnindex{slime-xref-cleanup} From jeffrey at cunningham.net Mon Jan 15 04:26:44 2007 From: jeffrey at cunningham.net (Jeffrey Cunningham) Date: Sun, 14 Jan 2007 20:26:44 -0800 Subject: [hunchentoot-devel] Re: [slime-devel] slime-texi patch In-Reply-To: <8757cb490701142021s382216e6s78e99cdb1c23c7b9@mail.gmail.com> References: <8757cb490701141710v7ce8f4dcy9f949f1a2bc736fc@mail.gmail.com> <20070115023523.GA3324@achilles.olympus.net> <8757cb490701141954y42735fa0i2b14a6034e9eaba4@mail.gmail.com> <20070115041235.GA5049@achilles.olympus.net> <8757cb490701142021s382216e6s78e99cdb1c23c7b9@mail.gmail.com> Message-ID: <20070115042643.GA5908@achilles.olympus.net> Sorry. I'll fix it. --Jeff On Sun Jan 14, 2007 at 08:21:57PM -0800, Bill Clementson wrote: > Hi Jeff, > > You posted to the hunchentoot/tbnl list instead of the slime list. > From lam at tuxfamily.org Mon Jan 15 18:41:47 2007 From: lam at tuxfamily.org (Nicolas Lamirault) Date: Mon, 15 Jan 2007 19:41:47 +0100 Subject: [hunchentoot-devel] Problem with redirect ... Message-ID: <87odp0uo7o.fsf@no-log.org> hello, i have a problem with my Hunchentoot application. i would like to test redirect, so i create this function : (defun handle-redirect () (hunchentoot:redirect "/clappa/index")) and for debugging : CL-USER> (setf hunchentoot:*catch-errors-p* nil) NIL so, in the browser, http://localhost/mytest/redirect i have this : invalid number of arguments: 1 [Condition of type SB-INT:SIMPLE-PROGRAM-ERROR] Restarts: 0: [TERMINATE-THREAD] Terminate this thread (#) Backtrace: 0: ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN)) #) and slime is disconnected. in the buffer *slime-events* i have this : ("invalid number of arguments: 1" " [Condition of type SB-INT:SIMPLE-PROGRAM-ERROR]" nil nil) (("TERMINATE-THREAD" "Terminate this thread (#)")) ((0 "((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN))\n #)") (1 "(SWANK::CALL-WITH-BINDINGS\n ((*PRINT-PRETTY* . T) (*PRINT-LEVEL* . 4) (*PRINT-LENGTH* . 10)\n (*PRINT-CIRCLE* . T) (*PRINT-READABLY*)\n (*PRINT-PPRINT-DISPATCH* . #)\n (*PRINT-GENSYM* . T) (*PRINT-BASE* . 10) (*PRINT-RADIX*)\n (*PRINT-ARRAY* . T) ...)\n #)") (2 "(SWANK::DEBUG-IN-EMACS #)") (3 "((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN))\n #\n #)") (4 "(SWANK::CALL-WITH-REDIRECTED-IO\n #\n #)") (5 "(SWANK::CALL-WITH-CONNECTION\n #\n #)") (6 "(INVOKE-DEBUGGER #)") (7 "(HUNCHENTOOT::MAYBE-INVOKE-DEBUGGER\n #)") (8 "(SIGNAL #)") (9 "(ERROR SB-INT:SIMPLE-PROGRAM-ERROR)") (10 "(SB-KERNEL::INVALID-ARG-COUNT-ERROR-HANDLER\n #\n #.(SB-SYS:INT-SAP #XB6B130AC)\n #\n (77))") (11 "(SB-KERNEL:INTERNAL-ERROR\n #.(SB-SYS:INT-SAP #XB6B12D9C)\n #)") (12 "(\"foreign function: call_into_lisp\")") (13 "(\"foreign function: funcall2\")") (14 "(\"foreign function: interrupt_internal_error\")") (15 "(\"foreign function: sigtrap_handler\")") (16 "(CLAPPA-WEB::HANDLE-ERROR)") (17 "(HUNCHENTOOT::START-OUTPUT NIL)") (18 "(HUNCHENTOOT::PROCESS-REQUEST\n ((:HOST . \"82.225.177.13:9998\")\n (:USER-AGENT\n . \"Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.8.0.7) Gecko/20060830 Firefox/1.5.0.7 (Debian-1.5.dfsg+1.5.0.7-2)\")\n (:ACCEPT\n . \"text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5\")\n (:ACCEPT-LANGUAGE . \"fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3\")\n (:ACCEPT-ENCODING . \"gzip,deflate\")\n (:ACCEPT-CHARSET . \"ISO-8859-1,utf-8;q=0.7,*;q=0.7\")\n (:KEEP-ALIVE . \"300\") (:CONNECTION . \"keep-alive\")) ..)") (19 "(HUNCHENTOOT::PROCESS-CONNECTION\n # From edi at agharta.de Mon Jan 15 19:20:26 2007 From: edi at agharta.de (Edi Weitz) Date: Mon, 15 Jan 2007 20:20:26 +0100 Subject: [hunchentoot-devel] Problem with redirect ... In-Reply-To: <87odp0uo7o.fsf@no-log.org> (Nicolas Lamirault's message of "Mon, 15 Jan 2007 19:41:47 +0100") References: <87odp0uo7o.fsf@no-log.org> Message-ID: On Mon, 15 Jan 2007 19:41:47 +0100, Nicolas Lamirault wrote: > (16 "(CLAPPA-WEB::HANDLE-ERROR)") > > someone have any idea how can i debug this ? What does CLAPPA-WEB::HANDLE-ERROR do? From lam at tuxfamily.org Mon Jan 15 19:53:26 2007 From: lam at tuxfamily.org (Nicolas Lamirault) Date: Mon, 15 Jan 2007 20:53:26 +0100 Subject: [hunchentoot-devel] Problem with redirect ... In-Reply-To: (Edi Weitz's message of "Mon, 15 Jan 2007 20:20:26 +0100") References: <87odp0uo7o.fsf@no-log.org> Message-ID: <87ejpwukw9.fsf@no-log.org> i would like to define a web page when someone try to access an unknown page : ;; (defun handle-error () ;; "Modify the Hunchentoot error dispatcher." ;; (make-web-page #p"error.html")) and in the init file : ;;(setf hunchentoot:*http-error-handler* 'handle-error) i remove this code from my web service and i haven't got any error with my redirect test ! But if i reload my web service with my handle-error and i try to open a page that is doesn't exist, my handle-error works and print the error page. Edi Weitz writes: > On Mon, 15 Jan 2007 19:41:47 +0100, Nicolas Lamirault wrote: > >> (16 "(CLAPPA-WEB::HANDLE-ERROR)") >> >> someone have any idea how can i debug this ? > > What does CLAPPA-WEB::HANDLE-ERROR do? > -- Nicolas Lamirault -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From edi at agharta.de Mon Jan 15 20:56:05 2007 From: edi at agharta.de (Edi Weitz) Date: Mon, 15 Jan 2007 21:56:05 +0100 Subject: [hunchentoot-devel] Problem with redirect ... In-Reply-To: <87ejpwukw9.fsf@no-log.org> (Nicolas Lamirault's message of "Mon, 15 Jan 2007 20:53:26 +0100") References: <87odp0uo7o.fsf@no-log.org> <87ejpwukw9.fsf@no-log.org> Message-ID: On Mon, 15 Jan 2007 20:53:26 +0100, Nicolas Lamirault wrote: > i would like to define a web page when someone try to access an > unknown page : > > ;; (defun handle-error () > ;; "Modify the Hunchentoot error dispatcher." > ;; (make-web-page #p"error.html")) > > and in the init file : > > ;;(setf hunchentoot:*http-error-handler* 'handle-error) http://weitz.de/hunchentoot/#*http-error-handler* "[...] a function designator for a function of one argument [...]" > i remove this code from my web service and i haven't got any error > with my redirect test ! Sure: "The function gets called if the responsible handler has set a return code other than +HTTP-OK+ or +HTTP-NOT-MODIFIED+ and *HANDLE-HTTP-ERRORS-P* is true." From lam at tuxfamily.org Tue Jan 16 10:09:24 2007 From: lam at tuxfamily.org (Nicolas Lamirault) Date: Tue, 16 Jan 2007 11:09:24 +0100 Subject: [hunchentoot-devel] Problem with redirect ... In-Reply-To: (Edi Weitz's message of "Mon, 15 Jan 2007 21:56:05 +0100") References: <87odp0uo7o.fsf@no-log.org> <87ejpwukw9.fsf@no-log.org> Message-ID: <871wlv706j.fsf@no-log.org> thanks a lot ! with your help and your documentation my web app is working well. Edi Weitz writes: > On Mon, 15 Jan 2007 20:53:26 +0100, Nicolas Lamirault wrote: > >> i would like to define a web page when someone try to access an >> unknown page : >> >> ;; (defun handle-error () >> ;; "Modify the Hunchentoot error dispatcher." >> ;; (make-web-page #p"error.html")) >> >> and in the init file : >> >> ;;(setf hunchentoot:*http-error-handler* 'handle-error) > > http://weitz.de/hunchentoot/#*http-error-handler* > > "[...] a function designator for a function of one argument [...]" > >> i remove this code from my web service and i haven't got any error >> with my redirect test ! > > Sure: > > "The function gets called if the responsible handler has set a > return code other than +HTTP-OK+ or +HTTP-NOT-MODIFIED+ and > *HANDLE-HTTP-ERRORS-P* is true." > -- Nicolas Lamirault -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available URL: From edi at agharta.de Wed Jan 17 00:22:56 2007 From: edi at agharta.de (Edi Weitz) Date: Wed, 17 Jan 2007 01:22:56 +0100 Subject: [hunchentoot-devel] New release 0.4.14 Message-ID: Changelog: Version 0.4.14 2007-01-17 More meaningful results for RAW-POST-DATA Download: http://weitz.de/files/hunchentoot.tar.gz Cheers, Edi. From edi at agharta.de Wed Jan 17 09:20:41 2007 From: edi at agharta.de (Edi Weitz) Date: Wed, 17 Jan 2007 10:20:41 +0100 Subject: [hunchentoot-devel] New release 0.5.0 Message-ID: ChangeLog: Version 0.5.0 2007-01-17 More flexible behaviour of RAW-POST-DATA Robustified PARSE-CONTENT-TYPE Download: http://weitz.de/files/hunchentoot.tar.gz Cheers, Edi. From ndj at hivsa.com Wed Jan 17 09:24:03 2007 From: ndj at hivsa.com (Nico de Jager) Date: Wed, 17 Jan 2007 11:24:03 +0200 Subject: [hunchentoot-devel] setuid & setguid Message-ID: <200701171124.03136.ndj@hivsa.com> Hi all Form the Hunchentoot documentation: "On Unix you can use setuid and setgid to change the UID and GID of the process directly after the server has been started. (You might want to do this if you're using a privileged port like 80.) setuid and setgid can be integers (the actual IDs) or strings (for the user and group name respectively)." Does this work on Linux? Will this change the uid and gid of the running lisp image or only of certain threads? In my instance, I start my LispWorks image as root in order to start the server on port 443, and then wish to change the Hunchentoot image to a uid/gid with less privileges. Supplying the :setuid and :setgid parameters have no effect, though, the uid is still shown as root with ps/top. I am running LispWorks 5.0.1 and Debian Sarge backports (kernel 2.6.16) with hunchentoot 0.4.12. Thanks. Nico From edi at agharta.de Wed Jan 17 10:01:43 2007 From: edi at agharta.de (Edi Weitz) Date: Wed, 17 Jan 2007 11:01:43 +0100 Subject: [hunchentoot-devel] setuid & setguid In-Reply-To: <200701171124.03136.ndj@hivsa.com> (Nico de Jager's message of "Wed, 17 Jan 2007 11:24:03 +0200") References: <200701171124.03136.ndj@hivsa.com> Message-ID: On Wed, 17 Jan 2007 11:24:03 +0200, Nico de Jager wrote: > Form the Hunchentoot documentation: > "On Unix you can use setuid and setgid to change the UID and GID of > the process directly after the server has been started. (You might > want to do this if you're using a privileged port like 80.) setuid > and setgid can be integers (the actual IDs) or strings (for the user > and group name respectively)." > > Does this work on Linux? Works for me - see below. > Will this change the uid and gid of the running lisp image or only > of certain threads? It calls setuid(2) and setgid(2) respectively which set the values "of the current process" - see the man pages. > In my instance, I start my LispWorks image as root in order to start > the server on port 443, and then wish to change the Hunchentoot > image to a uid/gid with less privileges. Supplying the :setuid and > :setgid parameters have no effect, though, the uid is still shown as > root with ps/top. CL-USER 13 > (lisp-implementation-type) "LispWorks" CL-USER 14 > (lisp-implementation-version) "5.0.1" CL-USER 15 > (software-type) "Linux" CL-USER 16 > (software-version) "2.6.17-2-686" CL-USER 17 > (sys:call-system-showing-output "id") ; id ; uid=0(root) gid=0(root) groups=0(root) 0 CL-USER 18 > (hunchentoot:start-server :port 80 :setuid "edi" :setgid "users") # CL-USER 19 > (sys:call-system-showing-output "id") ; id ; uid=1000(edi) gid=100(users) groups=0(root) 0 CL-USER 20 > (hunchentoot:start-server :port 81) Error: Failed to create socket. Syscall BIND failed: Permission denied (13). 1 (abort) Quit process. Type :b for backtrace, :c