File: TODO

package info (click to toggle)
optcomplete 1.2-10
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 168 kB
  • ctags: 106
  • sloc: python: 558; sh: 13; makefile: 9
file content (39 lines) | stat: -rw-r--r-- 1,201 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
=================
TODO: optcomplete
=================


- bug: we need a better way to pass the COMP_WORDS array to the program, lest
  the space delimited arguments will be split (bleh). perhaps use a random
  string to do this.

- provide more completers.




.. end

- how will it work with my multiple subcommand framework?

- see if we can support csh.

- we could add an option that would make the short options automatically expand
  to long options, this depends how the shell treats our answers.

- optcomplete: write and publish the insight document about optcomplete, with 3
  volets:

  1. documentation, in file
  2. options parsing and help
  3. graying/filter vs. programmable completion

  - Unix has had the great tradition of the command-line interface (note: just
    another interface);

  - this has nurtured an environment where genericity has been given
    importance, and incidentally, modularity. these conditions make for
    software that is more robust: there is more reuse since the functionality
    is more generic, and modularity forces the programmer to have to deal with
    interfaces, which in turn indices the need for better design and thinking
    of the code.