sort output-file targets are no longer extracted as paths

The sort command's output-file flags are no longer treated as write targets for permissions.

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

2Signal: worth watching, 1 to 5

PermissionsArea: what it touches

RemovedKind: in v2.1.233, 14 Aug 26

RemovedSection of the release

What

The special handling that pulled --output=FILE and -oFILE targets out of a sort command was dropped, so sort is now treated like cat, head, tail and wc with plain positional paths only.

Evidence

sort: JM,

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.233 →

The build it came inv2.1.233

14 Aug 2026 · 180 entries, this one is #180.

Use it now20
You'll notice83
Nothing to try yet26
Under the hood51

Either side of it

v2.1.232Older
v2.1.234Newer

Open the release →

Names in this entry

settinghead
The sort command's output-file flags are no longer treated as write targets for permissions.
settingtail
The sort command's output-file flags are no longer treated as write targets for permissions.

Is this right?