[tahoe-dev] tahoe -d is awkward

[Greg Troxel]

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?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20110406/9f6543f0/attachment.pgp>