[tahoe-dev] tahoe -d is awkward

[Karn Kallio]

> > I'm trying to gradually get more serious in my tahoe usage - private
> > grid and backups, not just playing with the pubgrid.
> > 
> > I now on several machines have client directories ~/.tahoe-pubgrid and
> > ~/.tahoe-gdt.  I have separate server processes on server machines.
> > 
> > So, I find myself doing
> > 
> > tahoe deep-check -d ~/.tahoe-gdt --add-lease --repair
> > tahoe deep-check -d ~/.tahoe-pubgrid --add-lease --repair
> > 
> > and naturally would like to have aliases
> > 
> >   tahoep () { tahoe -d ${HOME}/.tahoe-pubgrid $*; }
> >   tahoeg () { tahoe -d ${HOME}/.tahoe-gdt $*; }
> > 
> > but that won't work, because one must do "tahoe command [options]".
> > Since -d is about everything, it would be nice if it were accepted at
> > the beginning.
> > 
> > So:
> >   is this already an open ticket?
> >   
> >   if not, do people think my desire is sensible?
> >   
> >   how do others who use the CLI deal with this?
> 
> In bash you could try something like this:
> 
> tahoep () { local cmd=$1; shift 1; echo $cmd -d ${HOME}/.tahoe-pubgrid $*; }

But replace the echo with tahoe of course.  By error I sent the test.

tahoep () { local cmd=$1; shift 1; tahoe $cmd -d ${HOME}/.tahoe-pubgrid $*; }