[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1897: CLI: add a way to change an existing alias without directly editing the aliases file

[Tahoe-LAFS]

#1897: CLI: add a way to change an existing alias without directly editing the
aliases file
-------------------------------+-------------------------------------------
     Reporter:  davidsarah     |      Owner:  daira
         Type:  defect         |     Status:  assigned
     Priority:  normal         |  Milestone:  soon
    Component:  code-          |    Version:  1.9.2
  frontend-cli                 |   Keywords:  cli tahoe-add-alias usability
   Resolution:                 |
Launchpad Bug:                 |
-------------------------------+-------------------------------------------

Comment (by warner):

 Meh, I'm kind of in favor of just having people edit the file. I think we
 need at least one alias-manipulating command for the sake of discovery,
 but I'm not super-convinced that we need modification and removal
 commands.

 That said, I wouldn't object if someone really wanted to add them. Just be
 cognizant of secret dircaps showing up in .bash_history and globally-
 visible 'ps' listings. You can create an alias without revealing it that
 way, but you can't add one safely. If we do want to enable modification,
 we might want to make the user paste in the new dircap via a `raw_input()`
 prompt. At that point it starts to look easier to tell people how to edit
 the aliases file :).

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1897#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage