Max Vozeler <max@hinterhof.net>
sender-time Sent at 16:44 (GMT+02:00). Current time there: 6:33 PM.
to MiKael NAVARRO <klnavarro@gmail.com>
date Fri, Jul 30, 2010 at 16:44

Hi MiKael,

On Wed, Jul 28, 2010 at 11:35:36AM +0200, MiKael NAVARRO wrote:

> In fact I have chosen this syntax (use options instead of passing
> arguments) because is more easy to control and in the futur I plan to
> allow multiple commands to be launched and executed in a given order
> (ex ./yagtd-cli.py --list "" --add "Tasktext @context p:project"
> --order "5 project").

Makes sense!

> > Perhaps some of that typing-friendlyness could be put into
> > yagtd-cli syntax directly.
>
> I don't wish integrate some of that typing-friendlyness
> because this imply a maintenance of these commands into yagtd-cli.py,
> while today, with my mechanism, options are created automatically
> (as soon as it is added in yagtd.py).

Understood. These are sound arguments for choosing the option-
with-arguments syntax over the more free-form syntax.

> > But then I'm also very happy using
> > something like the above, so consider me one happy user. :)
>
> I will be happy too, if you accept to publish your shell script into
> my yaGTD package ?
> It could help somebody in the same situation...

Yes, of course. :)

The shell function I sent is not robust, though. If you are
considering to include it, let me send you a better version in
a small shell script. (see attached)

Thanks and best regards,

Max

(file #9640)

Max Vozeler <max@hinterhof.net>
sender-time Sent at 15:38 (GMT+02:00). Current time there: 6:29 PM.

Hello MiKaël,

gna.org won't allow me to add comments to the task, it says
my user account is not authorized. Something to change maybe?

I would add more comments, but I will just send them in this
email instead, maybe we can later paste the conversation into
the gna.org task ticket.

On Sat, Jul 24, 2010 at 06:48:28PM +0200, MiKaël NAVARRO wrote:

> I have written a wrapper script 'yagtd-cli.py' allowing to run commands
> non-interactively (see help: $ yagtd-cli.py --help).
>
> This wrapper dynamically inspect main GTD class:
> - to find all implemented commands (with associated docstring),
> - and create an option to yagtd-cli.py script.
>
> But, the syntax is somewhat different:
> $ yagtd-cli.py --list "" todo.txt
> $ yagtd-cli.py --add "Text @work p:customer2" todo.txt
> $ yagtd-cli.py --order "5" todo.txt
>
> P.S.:
> - All commands option need a string argument or an empty string "";
> - An auto-save is done automatically before exiting the script;
> - Multiple commands can be submitted, but the order is not preserved (yet).
>
> Could you test this script (attached to this task #7119)?
> Thanks in advance.

yagtd-cli.py has been working perfectly for me over the last
two days, thank you very much!

The syntax is working fine for me. Although I must admit that
I find it a bit difficult to remember having to apply correct
quoting of the command arguments.

That's why I've been using a small shell function which IMHO
gives a typing-friendlier interface:

y() {
cmd=$1; shift; args="$*"
yagtd-cli.py --${cmd} "$args" ~/todo.txt
}

This allows me to say:

$ y add Tasktext @context p:project
$ y listall

Perhaps some of that typing-friendlyness could be put into
yagtd-cli syntax directly. But then I'm also very happy using
something like the above, so consider me one happy user. :)

Also I like the --help output a lot.

Thanks and best regards,
Max

This item has been reassigned from the project yaGTD - Yet Another Getting Things Done. bugs tracker to your tracker.

The original report is still available at bugs #16268

Following are the information included in the original report:

[field #0] Item ID: 16268
[field #1] Group ID: 1970
[field #2] Open/Closed: Open
[field #3] Severity: 1 - Wish
[field #4] Privacy: Public
[field #8] : Unknown bugs Field Display Type
[field #9] Category: None
[field #10] Submitted by: mvz
[field #11] Assigned to: None
[field #12] Submitted on: Thursday 07/15/2010 at 16:30
[field #13] Summary: Provide way to run commands non-interactively
[field #14] Original Submission: I notice that I often start yagtd only to run a single command and then immediately exit from the yagtd shell.

Having some way to run the command non-interactively would make yagtd even more efficient and fun to use for me. :)

It would be great if yagtd could, for example, be passed a command on invocation like this:

$ yagtd todo.txt add Text @work p:customer2
Task #204 added

$ yagtd todo.txt listall
...
[field #16] Item Group: None
[field #17] Status: Works For Me
[field #18] Component Version: None
[field #19] Operating System: None
[field #20] Reproducibility: None
[field #21] Size (loc): None
[field #22] Fixed Release: None
[field #23] Planned Release: None
[field #24] Effort: 0.00
[field #28] Priority: 5 - Normal
[field #31] Percent Complete: 0%
[field #33] Release: None
[field #58] Custom Select Box #1: None
[field #59] Custom Select Box #2: None
[field #60] Custom Select Box #3: None
[field #61] Custom Select Box #4: None
[field #62] Custom Select Box #5: None
[field #63] Custom Select Box #6: None
[field #64] Custom Select Box #7: None
[field #65] Custom Select Box #8: None
[field #66] Custom Select Box #9: None
[field #67] Custom Select Box #10: None