Remove $FreeBSD$: one-line nroff pattern

Remove /^\.\\"\s*\$FreeBSD\$$\n/

Tell the world how to convert gigabytes to bytes with units(1) easily

It turns out that units(1) is not as horrible to use in scripts
as I initially thought. When the --terse flag is combined
with a

Tell the world how to convert gigabytes to bytes with units(1) easily

It turns out that units(1) is not as horrible to use in scripts
as I initially thought. When the --terse flag is combined
with an appropriate output format (set via --output-format),
units(1) is actually capable of producing very nice results.
For example:

units -o %0.f -t '4 gigabytes' bytes

is is just going to print out the expected value of 4294967296.

There is no time to waste. People have to know about it.

I am adding an example for this at the top of the examples section
because this is what users are most likely looking for.

Approved by: bcr (mentor)
Differential Revision: https://reviews.freebsd.org/D24096

show more ...

Merge ^/head r357408 through r357661.

units(1): Refactor the manual page and update usage information

Changes to units.1:

- Change the description to a more descriptive "conversion calculator".
- Sort options.
- Split the description i

units(1): Refactor the manual page and update usage information

Changes to units.1:

- Change the description to a more descriptive "conversion calculator".
- Sort options.
- Split the description into sections to make it easier to navigate the
manual page.
- Improve the description of various options.
- Document the default value of the output format.
- Use more mdoc macros for better readability.
- Document the behavior of the PATH environmental variable.
- Improve examples.
- Add sections: EXIT STATUS, DIAGNOSTICS, and HISTORY.
- Document that units(1) cannot convert negative values and it handles long
unit lists poorly.
- Update the documentation of the -V flag to match the implementation.
units(1) prints its version and the units data file instead of its
version and usage information.

Changes to units.c:

- Update usage information.
- Sort longopts elements.

This commit does not attempts to change the current behavior of units(1).
What's left to do is probably defining a better versioning (at the moment
units(1) always reports "FreeBSD units" as its version) and changing the
behavior of the -V flag to only print version.

Reviewed by: allanjude (earlier version), bcr
Approved by: bcr (mentor)
Differential Revision: https://reviews.freebsd.org/D18977

show more ...

Merge ^/head r343202 through r343319.

Correct a typo: was -> way.

Submitted by: Larry Hynes
MFC after: 3 days
Sponsored by: The FreeBSD Foundation

Merge ^/head r322398 through r322746.

MFhead@r322451

Correct the -H longopt equivillant

PR: 209876
Submitted by: <kdrakehp AT zoho DOT com>
Approved by: bcr (mentor)
Differential Revision: https://reviews.freebsd.org/D11988

Merge ^/head r313644 through r313895.

Escape No to avoid confusion with the No macro

Reported by: make manlint
MFC after: 2 days

Bring a little more compability with GNU units 2.12
- notionally support a 'history file' flag. This doesn't do much now,
but is there to prevent scripts written against GNU units from
breaking
-

Bring a little more compability with GNU units 2.12
- notionally support a 'history file' flag. This doesn't do much now,
but is there to prevent scripts written against GNU units from
breaking
- correctly gracefully quit rather than exit (this will make it easier
to support a history file in the future)
- remove the "t" flag from fopen which was there to support windows. We
have not supported windows since at the latest, the introduction of
capsicum.

show more ...

Rename units.lib -> definitions.units
- this matches GNU units 2.12
add ISO country codes from units 2.12

IFC @r269962

Submitted by: Anish Gupta (akgupt3@gmail.com)

Merge head from 7/28

Sync to HEAD@r269943.

units(1): Add support for output-format
Add support for the output-format argument. This also exposes subtle
rounding differences between GNU units and our units.

units: Support start of line comments with '#'
Modern GNU units(1) supports comments anywhere with '#' but take the easy route for now and at least support start of line # comments.

units(1): Add 'terse' support
terse output is used when calling units from another script.

units(1): Add 'help' flag
- Add support for --help for compatibility
- Make usage() static

units(1): Fix man page
Igor walks one way. I walked the other.

Reported by: wblock

units(1): add long options
Things brings additional compatibility with units 2.10

Discussed with: wblock (man page)

use .Mt to mark up email addresses consistently (part3)

PR: 191174
Submitted by: Franco Fichtner <franco at lastsummer.de>

MFC @ r266724

An SVM update will follow this.

Merge head