[PATCHES] improve extensions support

[David A.]

One thing that would assist the extension developers is if pass
wouldn't use so many aliases.

show = ls = list
find = search
insert = add
delete = rm = remove
rename = mv
copy = cp

It leaves less choices for the extensions to use.  Pick one for each
and stick with it.  Or perhaps designate one as the primary
untouchable name but allow the others to be overridden.

To be fair, though, I like that pass accepts these aliases and if I
were writing it I probably would have done the same.  I'd be fine with
leaving it as-is but then my scripts that interact with pass aren't
written to appear as subcommands.  I don't subscribe to the notion
that every enhancement to pass has to be a built-in.

But, I can certainly see how opening these aliases up would help
extension writers who might want to modify the way an official
subcommand operates by choosing a similarly logical name for their
custom subcommand.


On Tue, 7 Feb 2017 16:41:22 +0100, David Izquierdo
<thecofee at gmail.com> wrote:

>Although my first thought on overriding pass commands was of 
>celebration, I do think it misses the point. Once you need to overwrite 
>pass itself, you might as well modify the actual script. Also, enforcing 
>extensions to use their own namespace seems safer in the long run. 
>Someone mentioned before the risk of a rogue facebook.com extension...
>
>
>In the end, typing `pass insert2` isn't much different from `pass 
>insert`. Add in a more imaginative name, and the need for overriding the 
>default insert is close to null.