|
From: | Kenneth Loafman |
Subject: | Re: [Duplicity-talk] bash completion for duplicity |
Date: | Fri, 29 Jun 2018 09:15:50 -0500 |
btw. i've contacted the author of the script. reply:
https://twitter.com/mikeyneuling/status/1011917702057766912
j
On Wed, 27 Jun 2018, edgar.soldin--- via Duplicity-talk wrote:
> yeah,
>
> would have to be implemented cleanly of course. see no disadvantage though in having command line parameters parsed earliest.
>
> but it's all rhetorical anyway as long as nobody implements argparse first ;).. ede/duply.net
>
> On 26.06.2018 21:10, Kenneth Loafman wrote:
>> Reading through the docs, it wants to execute duplicity during the autocomplete to get the options, and leave no side effects. That could be problematic.
>>
>> ...Ken
>>
>>
>> On Tue, Jun 26, 2018 at 7:54 AM edgar.soldin--- via Duplicity-talk <address@hidden <mailto:address@hidden>> wrote:
>>
>> On 26.06.2018 14:49, Aaron wrote:
>> > Without digging into the detail, this:
>> > http://argcomplete.readthedocs.io/en/latest/
>> > apparently automatically collects options for bash completion from argparse, which feels like a sensible approach.
>> >
>> > Moving from Optparse to Argparse is on the roadmap already anyway:
>> > https://bugs.launchpad.net/duplicity/+bug/1480565
>>
>>
>> agreed, this approach looks much cleaner than a manually maintained list of options.. ede/duply.net <http://duply.net>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden <mailto:address@hidden>
>> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
[Prev in Thread] | Current Thread | [Next in Thread] |