On 20 April 2012 03:37, Nico Golde <n...@ngolde.de> wrote:
> Hi,
> * Ivan Kanakarakis <ivan.ka...@gmail.com> [2012-04-20 01:54]:
> > On 20 April 2012 02:24, Connor Lane Smith <c...@lubutu.com> wrote:
> > > On 19 April 2012 23:51, Connor Lane Smith <c...@lubutu.com> wrote:
> [...]
> > however if one wants to connect to more than one server
> > and has a different password for that other server then
> > the env var doesn't help, scriptwise talking.
> >
> > ofcourse one can reset the var and invoke the new ii isntance,
> > but if you're doing that in a script and you don't want to be
> > including the passwd within the script then this cant work.
>
> Why not, the script could read it from a file not? Even though I don't see
> the
> difference. Whoever can read that script likely can also read the file.
>
> > well, what I have in mind with that ^ is something like:
> > $ IRCPASS="fooo" connect.sh
> > and connect.sh fires up two ii instances to connect to
> > two different server which need a different password.
> >
> > I think a nice thing to do that would also resolve the
> > naming choice would be to have -k or some other argument
> > mean that ii should read the -k flag as an env var. so
> > $ ii -k IRCPASS
> > would getenv("IRCPASS"), and
> > $ ii -k OFTCPASS
> > would getenv("OFTCPASS")
> > etc
>
> I agree this is actually also a very nice solution! I will think about
> that a
> little before I commit.
>
>
any news on this ?
do you think any of the propused ideas will reach upstream ?
> Cheers
> Nico
>
--
*Ivan c00kiemon5ter V Kanakarakis* >:3
