Popt has a poptReadConfigFile() which is described as doing the following

 The file specified by fn is opened and parsed as a popt configuration file. This allows programs to use program-specific configuration files.

What’s unclear is whether it can only be used to enable aliases, or if it can also be used as a general-purpose configuration file to replace the command-line interface, and if so, what format it should be in.

As no documentation I could find explains it one way or the other, I resorted to reading the code.

The short answer is no. Popt (1.16) cannot read command line parameters from an rc configuration file.

There is an undocumented feature of the popt configuration file parsing, execs, which I hope would serve my purpose, but this is unfortunately not the case. Rather, they allow the execution of other binaries when specific options are seen.

For the sake of completeness, here is an example of the configuration syntax for both aliases and execs. The popt source tree also ships with some examples.

PROGRAM alias --NEWOPT1 --OLDOPT1 --OLDOPT2=VAL2
PROGRAM alias --NEWOPT2 OTHER-PROGRAM

With this configuration file as, e.g., ~/.poptrc, PROGRAM will behave as follows.

• PROGRAM --NEWOPT1 will behave as if PROGRAM --OLDOPT1 --OLDOPT2=VAL2 had been called;
• PROGRAM --NEWOPT2 will exec(3) OTHER-PROGRAM, and terminate when it does.

I’m not quite sure I understand the point of execs…

Related posts:

You know it’s mature when you only need a terminal to run it (CalDAV tools for the console) Exporting the SSL root store from Mac OS X’s Keychain Clearing persistent duplicates in the Kodi music library Resolve escapes in Python strings

Powered by YARPP.