Docs about BeanShell can be found at the obvious place: http://www.beanshell.org/

As for the patch, I would assume you would like to see just the patch for BeanShell alone, I will extract it and post it to the gui mailing list.

What CLI do you mean? I do only know LimeWire as a GUI program. BeanShell has an option to start a telnet listener, so adding this code to the LimeWire.bsh file that is read upon startup would make the BeanShell console available via telnet, would that be what you are looking for?

You should put some of my requerying code into your version. - They'll hire somebody to gun you down.

The CLI is in com.limegroup.gnutella.Main (as opposed to com.limegroup.gnutella.gui.Main) in the core module. It is very minimal and I'd love to see it get more functionality.

I wouldn't so much like a direct telnet opening for security reasons; the CLI on the other hand can be tunelled over ssh and I can use 'screen' with it ;-))

Oh well, that one is pretty primitive. I like to be able to at least interact in a sensible way for just the standard things, so I control my LimeWire remotely using ssh and a tunneled VNC connection, works great and allows one as a developer to exercise the GUI as well.

What about encouraging people to leave their LW running with a "while away" sub-menu for the "Repeat Search"?

Better yet, I'd like LW to automatically re-search for the key terms of inactive downloads "while away."

this option would become available in the downloads pane (rather than reactivating overly broad queries) . . .

--if it had been active at least once (i.e--there is a source out there that has been manually found and initiated by the user)

--if there has been no keyboard or mouse action for 1 or 2 hours. (allows refreshing downloads overnight or while at work).

Would a limited automatic search once every 1 or 2 hours from an otherwise inactive machine be harmful or easily abused?