Hello! Sorry for the incorrect submission format, here it is in a correct and
polished manner.
Let me know of yout thoughts.
Cheers!
___
Password-Store mailing list
Password-Store@lists.zx2c4.com
On Tue, Feb 7, 2017 at 1:57 PM, Alexandre Pujol wrote:
> Moreover, from a technical point of view I see a mess coming when you
> will need to manage the 10th overwriting of the same core command. What
> about classic extension compatibility with the overwritten core command?
>
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
When you put it like this, I have to agree. Using a different name for
the new/changed command is not a big deal.
However, the help command showing help for the extensions is one feature
of the patch that I would like to see added to pass.
Furthermore, what extensions are missing is
Well, you can't override more than once because you can't have 2 files
with the same name. This allows users more freedom, they can choose to
use internal commands or extensions. The pass core isn't touched.
Current extensions are not affected at all. Also, users wanting to use
an extension that
Ok, after a while going round and round I realized of an easier way, to
keep it simple stupid:
check_extension_and_load show "$@" || cmd_show "$@"
Here goes the patch attached.
Thanks!
On 02/06/2017 06:33 PM, Lars Flitter wrote:
> Hi,
>
> I like the idea of overriding the built in pass