Output of results

[tessus]

I was trying to use fend in a scripted way to behave similar to numfmt.

$ numfmt --to=iec --format=%.2f 1845842429
1.72G

With fend I have to decide on a unit beforehand, e.g. MiB or GiB either by using a specfic conversion or appropriate divisor:

> 1845842429 bytes in MiB to 0dp
approx. 1760 MiB
> 1845842429 /1024 /1024 to 0dp
approx. 1760
> 1845842429 bytes in GiB to 2dp
approx. 1.71 GiB
> 1845842429 /1024 /1024 /1024 to 2dp
approx. 1.71

Now I have 2 questions:

1. Is it possible to suppress "approx." in the output?
2. Is there a way to output the result with separators? e.g. 1,760 MiB

(Please note that I am not asking for a feature like printing bytes in powers of 1024.)

[printfn]

1. Is it possible to suppress "approx." in the output?

Yes, you can suppress that by prefixing your calculation with @noapprox. For example @noapprox 1845842429 bytes in MiB to 0dp becomes 1760 MiB. I should really improve the documentation for this as it is currently only documented in the changelog.

2. Is there a way to output the result with separators? e.g. 1,760 MiB

This is not currently supported but it is on my roadmap and I'll see if I can get it implemented soonish.

[tessus]

Yes, you can suppress that by prefixing your calculation with @noapprox

Awesome, thanks. Would you accept a PR to add this as a note under the section Number formats?

This is not currently supported but it is on my roadmap

Cool. How would that work? With something like @usesep

[printfn]

A PR would be great! Not quite sure yet how I’d handle the thousands separators; I’m quite tempted to enable them by default with an option to disable them.

[tessus]

PR is coming up after my next beer... ;-) Btw, there's also a bug in the docs, which I'll fix at the same time.

I’m quite tempted to enable them by default with an option to disable them.

I don't envy you for having to make that decision. Thousand separators are great for reading a number, but not so much for processing in scripts. I honestly wouldn't know how I would make that decision.
However, if it is not too much work I'd probably allow people to set the default behavior in the the config.