Arch Linux User Repository

@lbortoli: make sure you are running bash. Then the following should display a list: todo<TAB><TAB><TAB> or todo.sh<SPACE><TAB><TAB>

Hello! I just installed this package and it seems that bash completion is not working.

@billypilgrim: bash completion now works out-of-the-box again.

@dreieck: Thanks. Should be fixed in the next release/update. If you want, you can follow the progress of the github issue (see URL below) and maybe test the fix before the next release, for example, by copying the check() function from todotxt-git's PKGBUILD and run the tests.

I have added unser XDG_CONFIG_HOME in the PKGBUILD in build(), check() and package() and I get a failing check() with
* FAIL 1: no config file
* FAIL 2: custom action (default location 2)
* FAIL 5: config file (global config file)

It had to do that I have $TODO*-variables set.

I had to also unset those variables in addition to $XDG_CONFIG_HOME in check().

check() succeeds for me if I add to it:

  unset XDG_CONFIG_HOME
  unset TODO_DIR
  unset TODOTXT_FINAL_FILTER
  unset TODO_ACTIONS_DIR
  unset TODO_NOTES_DIR
  unset TODO_NOTE_TAG
  unset TODOTXT_SORT_COMMAND
  unset TODO_CONF_DIR
  unset TODO_FILE
  unset TODO_NOTE_EXT

Here, for completeness, the error I get in check() with only unset XDG_CONFIG_HOME:

==> Starting check()...
rm -rf tests/test-results "tests/trash directory"*
cd tests && ./t0000-config.sh 
cd tests && ./t0001-null.sh 
cd tests && ./t0002-actions.sh 
cd tests && ./t0100-code-nobacktick.sh 
*   ok 1: no old-style backtick command substitution 1
* FAIL 1: no config file

    todo.sh > output 2>&1 || test_cmp expect output

*   ok 2: no old-style backtick command substitution 2
* FAIL 1: custom action (default location 1)

    mkdir .todo.actions.d
    cp foo .todo.actions.d/
    todo.sh foo > output;
    test_cmp expect output && rm -rf .todo.actions.d

* passed all 2 test(s)*   ok 1: null ls

*   ok 2: config file (default location 1)
cd tests && ./t1000-addlist.sh 
* FAIL 2: custom action (default location 2)

    mkdir -p .todo/actions
    cp foo .todo/actions/
    todo.sh foo > output;
    test_cmp expect output && rm -rf .todo/actions

*   ok 3: config file (default location 2)*   ok 2: null list

*   ok 3: custom action (env variable)
*   ok 4: config file (default location 3)* failed 2 among 3 test(s)

make: *** [Makefile:96: tests/t0002-actions.sh] Error 1
make: *** Waiting for unfinished jobs....
*   ok 1: basic add/list 1
* FAIL 5: config file (global config file)

    cp test.cfg "$TODOTXT_GLOBAL_CFG_FILE"
    todo.sh > output;
    test_cmp expect output && test -f used_config &&
        rm -f "$TODOTXT_GLOBAL_CFG_FILE"

*   ok 3: null list filter
*   ok 6: config file (command line)
*   ok 7: config file (env variable)
*   ok 2: basic add/list 2
*   ok 8: config file (minimal)
* failed 2 among 8 test(s)*   ok 4: null lsp

make: *** [Makefile:96: tests/t0000-config.sh] Error 1
*   ok 3: basic add/list 3
*   ok 5: null listpri*   ok 4: basic add/list 4

*   ok 5: basic list filtering 1
*   ok 6: null listpri a
*   ok 6: basic list filtering 2
*   ok 7: case-insensitive filtering 1
*   ok 7: null lsa
*   ok 8: case-insensitive filtering 2
*   ok 9: add with symbols 1
*   ok 8: null list
*   ok 10: add with symbols 2
*   ok 11: add with symbols 3
*   ok 9: null list filter
*   ok 12: add with spaces 1
*   ok 10: null lsc
*   ok 13: add with spaces 2
*   ok 11: null listcon
*   ok 12: null lsprj
*   ok 14: add with spaces 3
*   ok 13: null listproj
*   ok 14: null lf
*   ok 15: add with CR 1
*   ok 15: null listfile
*   ok 16: null listfile foo.txt
* passed all 16 test(s)*   ok 16: add with CR 2

*   ok 17: add to file without EOL 1
*   ok 18: add to file without EOL 2
* passed all 18 test(s)
==> ERROR: A failure occurred in check().

That seemed to do the trick. Thanks!

Maybe that has changed. According to the current instructions: https://github.com/todotxt/todo.txt-cli/wiki/Quick-Start-Guide#optional

. /usr/share/bash-completion/completions/todo

Nope. Is that necessary? I didn't have to do that before...

@billypilgrim: it is working for me. Do you "source" the completion file in Bash?