* raf: > I suppose a shell alias or function could take care of that without > needing to type the extra option (e.g.: alias postqq='postqueue -j | > postqf').
Indeed. In typical Unix-pipeline fashion, PostQF reads from stdin and writes to stdout per default, and it is up to the user to provide the required input. A shell alias would do nicely. > Also, the -a (after) and -b (before) options probably shouldn't be > mutually exclusive. Someone might want to see messages that arrived > between two and three hours ago, for example. You might have a point, I'll need to think about it. For the time being you can pipe data through "postqf -a 3h | postqf -b 2h" to achieve the desired result. > One last thing, the README.md file recommends installing into a venv, > but it doesn't then explain the steps necessary to run postqf > afterwards. If one follows the recommended installation steps in which the venv is activated, one only needs to type "postqf" in the shell window. See also my next comment below. > I'd recommend adding instructions or a wrapper script for postqf that > gets installed (somehow) Fortunately that's already taken care of. Quoting the documentation: "The pip installation process adds a launcher executable postqf, either site-wide or in the Python virtual environment. In the latter case, the launcher will be placed into the directory .venv/bin which is automatically added to your PATH variable when you activate the venv environment as shown above." I use a PEP 517 style build process, and "pip install" conveniently takes care of generating the launcher. Also, thanks for your feedback. -Ralph
