Like rcirc, you should be able to setq a variable before you launch rudel to have it simply work with the settings (server, user, color, etc.) you have written in your .emacs file.
I would suggest to do this with a custom function rather a set of global variables.
An alternative could be a customization option that manages connections. A new session initiation backend could be implemented that would read this option and offer all configured connections by name.
join a session with customized join data
There is an attachment demonstrating the first alternative.
Starting from bzr:235, the second alternative (mentioned in the comment before the previous) is implemented.
To define default connections, the option rudel-configured-connections can be customized. Connections (or sessions in Rudel terminology) can then be chosen by their configured name when running `rudel-join-session'.
Looks good, but the docstring for rudel-configured-sessions should probably list out what keywords are used. (:host vs :hostname, etc)
Actually, I can't get this to work myself. What am I doing wrong here?
`((:name "sonian" :backend obby
:server "sobby" :username ,user-login-name :color "white"
:global-password "" :user-password "")))
If I set this, it allows me to enter "sonian" as the session name, but it still prompts me for all the connection settings it used to.
To make your example work without any questions, I had to change the following:
:server -> :host
add :port 6522 (or whatever you use)
add :encryption t
Are you sure it asked for everything (even the specified parts)? When I tried it, only the missing data was prompted for.
The docstring definitely needs improvement. Maybe an example. Unfortunately, it is impossible to list all options, since each backend comes with its own set of options.
No, you're right; making those changes did the trick; thanks. An example will definitely help.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.