[tahoe-lafs-trac-stream] [tahoe-lafs] #166: command line order is problematic

[tahoe-lafs]

#166: command line order is problematic
---------------------------+-----------------------------------------------
     Reporter:  zandr      |      Owner:  warner
         Type:  defect     |     Status:  assigned
     Priority:  major      |  Milestone:  eventually
    Component:  code-      |    Version:  0.6.1
  frontend-cli             |   Keywords:  security usability unix mac error
   Resolution:             |
Launchpad Bug:             |
---------------------------+-----------------------------------------------

Comment (by davidsarah):

 Greg Troxel wrote on tahoe-dev:
 > 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.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/166#comment:15>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage