Comment 4 for bug 819038

Where is the config file format documented in the clicompanion source tree? Should a section be added to the man page documenting it?

On a related note: why does data/clicompanion2.config use ? for each parameter to be prompted for, but .clicompanion in the same source tree uses @ for the same purpose? Consistency would be nice. Again, where is this aspect of the file format documented? What happens if those characters should appear verbatim in a command in the library -- can they be escaped somehow?

How do people who already have customized command libraries from the earlier versions upgrade -- does this fix include automated conversion to the new file format?

In general, is using any single USASCII character as a field delimiter really appropriate? All ASCII characters are possible in command lines that people may want to add to clicompanion, so just picking a different one does not fully solve the underlying issue, does it? I suspect ut just makes a different set of commands impossible to store.

A more comprehensive fix may be to use a "real database" (sqlite perhaps?) to store this information. This could also allow future enhancements to tag each command entry with which packages it needs, which version of which distribution it works on, etc.

Overall, just changing from : to tab as the field delimiter does not look to me like a full solution to the underlying issue.