Column width values are fixed and have been chosen for every column according with sane probable values. The goal was to fit everything in a console with a length of 80 characters. This leads in extreme cases, as the one shown, to misalignments.
Making the column width variable depending on the output requires a lot of work and might not be implemented very soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am looking into this, and see if I can find a solution. Because of pfcalc internal workings there is currently no way for me to know in advance the length of the output data.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Proposed quick fix: make sure that no output line exceeds 80 characters in length by using scientific notation (e.g. 1.2E+06 instead of 1200000). This might lead to some precision loss, but this is not an issue since all accurate and complete data can be dumped to a file using the -o parameter.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Column width values are fixed and have been chosen for every column according with sane probable values. The goal was to fit everything in a console with a length of 80 characters. This leads in extreme cases, as the one shown, to misalignments.
Making the column width variable depending on the output requires a lot of work and might not be implemented very soon.
I am looking into this, and see if I can find a solution. Because of pfcalc internal workings there is currently no way for me to know in advance the length of the output data.
Proposed quick fix: make sure that no output line exceeds 80 characters in length by using scientific notation (e.g. 1.2E+06 instead of 1200000). This might lead to some precision loss, but this is not an issue since all accurate and complete data can be dumped to a file using the -o parameter.