Re: [EPIC] [RFD] On loading startup scripts before connecting...
Me too. On 5/15/05, Dave Kratter <[EMAIL PROTECTED]> wrote: > Count me in favor of defaulting to the -B behavior. > > On Sun, May 15, 2005 at 03:47:06PM -0500, Jeremy Nelson wrote: > > Historically, ircII clients have loaded your startup script (~/.ircrc) > > after you make your first connection to the server. This has been to > > permit you to change usermode, join channels, create windows, etc, in > > your startup script, all of which you can't really do before you connect. > > > > EPIC has the -B command line option which permits you to load your startup > > script at boot time, and not at connect time. If you want to do some action > > at connect time with the -B command line option, you use /on connect. > > > > In EPIC5, we have been scripting a great deal of functionality that used to > > be hardcoded into the client. Unless you use the -B command line option, > > these features are not available to you until you connect. This is become > > more of a problem. > > > > Thus, it is necessary to discuss whether the -B option should become the > > default (that ~/.ircrc always be loaded at boot time, rather than at connect > > time), and a new command line option be added to turn that off. > > > > Please share how you feel about this change. > > Jeremy > > ___ > > List mailing list > > List@epicsol.org > > http://epicsol.org/mailman/listinfo/list > > > > -- > > [EMAIL PROTECTED] > irc.colosolutions.net operator > > You have reached the end of the Internet. Please turn back. > > ___ > List mailing list > List@epicsol.org > http://epicsol.org/mailman/listinfo/list > ___ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
Re: [EPIC] [RFD] On loading startup scripts before connecting...
>* At 2005-05-15T15:47-0500, Jeremy Nelson wrote:
>:
>| Thus, it is necessary to discuss whether the -B option should become the
>| default (that ~/.ircrc always be loaded at boot time, rather than at connect
>| time), and a new command line option be added to turn that off.
>
>Another alternative is to add an .epicrc or something that would get
>loaded right away, and leave the .ircrc behaviour as it is. Since, I
>imagine, you'd want that sometimes.
One option that has been presented is to help people wrap their startup
scripts to simulate backwards compatability, to wit:
on #^connect -1 * {
... your old ircrc goes here ...
@hookctl(remove -1)
}
This would give a reasonable approximation of present behavior...
Jeremy
___
List mailing list
List@epicsol.org
http://epicsol.org/mailman/listinfo/list
Re: [EPIC] [RFD] On loading startup scripts before connecting...
* At 2005-05-15T15:47-0500, Jeremy Nelson wrote: : | Thus, it is necessary to discuss whether the -B option should become the | default (that ~/.ircrc always be loaded at boot time, rather than at connect | time), and a new command line option be added to turn that off. Another alternative is to add an .epicrc or something that would get loaded right away, and leave the .ircrc behaviour as it is. Since, I imagine, you'd want that sometimes. -- Stian Sletner ___ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
Re: [EPIC] [RFD] On loading startup scripts before connecting...
On Sun, 2005-05-15 at 15:47 -0500, Jeremy Nelson wrote: > Thus, it is necessary to discuss whether the -B option should become the > default (that ~/.ircrc always be loaded at boot time, rather than at connect > time), and a new command line option be added to turn that off. > > Please share how you feel about this change. I recently coded support into my script for randomizing my nick (and suspending channel joins) until I can log in to the Undernet channel service and activate host hiding. There were several things that made this difficult to do, and one of them is remembering to pass -B to epic when I start it. So, in summary, I'm in favor of making -B be the default. -- Kevin L. Mitchell <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part ___ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
Re: [EPIC] [RFD] On loading startup scripts before connecting...
Count me in favor of defaulting to the -B behavior. On Sun, May 15, 2005 at 03:47:06PM -0500, Jeremy Nelson wrote: > Historically, ircII clients have loaded your startup script (~/.ircrc) > after you make your first connection to the server. This has been to > permit you to change usermode, join channels, create windows, etc, in > your startup script, all of which you can't really do before you connect. > > EPIC has the -B command line option which permits you to load your startup > script at boot time, and not at connect time. If you want to do some action > at connect time with the -B command line option, you use /on connect. > > In EPIC5, we have been scripting a great deal of functionality that used to > be hardcoded into the client. Unless you use the -B command line option, > these features are not available to you until you connect. This is become > more of a problem. > > Thus, it is necessary to discuss whether the -B option should become the > default (that ~/.ircrc always be loaded at boot time, rather than at connect > time), and a new command line option be added to turn that off. > > Please share how you feel about this change. > Jeremy > ___ > List mailing list > List@epicsol.org > http://epicsol.org/mailman/listinfo/list > -- [EMAIL PROTECTED] irc.colosolutions.net operator You have reached the end of the Internet. Please turn back. ___ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
[EPIC] [RFD] On loading startup scripts before connecting...
Historically, ircII clients have loaded your startup script (~/.ircrc) after you make your first connection to the server. This has been to permit you to change usermode, join channels, create windows, etc, in your startup script, all of which you can't really do before you connect. EPIC has the -B command line option which permits you to load your startup script at boot time, and not at connect time. If you want to do some action at connect time with the -B command line option, you use /on connect. In EPIC5, we have been scripting a great deal of functionality that used to be hardcoded into the client. Unless you use the -B command line option, these features are not available to you until you connect. This is become more of a problem. Thus, it is necessary to discuss whether the -B option should become the default (that ~/.ircrc always be loaded at boot time, rather than at connect time), and a new command line option be added to turn that off. Please share how you feel about this change. Jeremy ___ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
