search for: ohmy

Hi all, I recently noticed something really weird in url_for results let''s say that we have something like this somewhere in code <pre> URL1:<%=url_for( {:action=>''foobar''}.merge({''action''=>''ohmy''}) )%> URL2:<%=url_for( {''action''=>''ohmy''}.merge({:action=>''foobar''}) )%> </pre> and then please consider following two cases... case 1. webrick, ruby 1.8.4, rails 1.0 result: URL1:.../foobar URL2:.../foobar case...

...ping between my documents' filenames and the URLs where I hope search users to find them is, uh..., strange. The simplest thing (to me) would be to run omindex for each document, e.g. omindex --no-delete -U /cool-url-1 /funky/doc/file-blah.pdf omindex --no-delete -U /cool-url-7 /doc/funky/ohmy/blah-file.txt ... and so on... Of course, this doesn't work because the pathnames don't signify directories. I'm guessing the same thing can be done with 'scriptindex' -- but I really want what just plain old omindex does. A horrible? way might be to copy each document into...

Hi - attached is a patch to enable building DragonEgg (x86_64) for LLVM3.3 and LLVM3.4. That is, add these changes to the 3.3 release, and it becomes possible to build DragonEgg against a llvm3.4 compiler. Regards, Richard Gorton Cognitive Electronics rcgorton at cog-e.com ---------- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: