-qi should prepend a single space to key-value delimitator colons.

[RokeJulianLockhart]

Generally, requests for new features should be opened as a Discussion first. There, feedback from the community can be collected and possible solutions can be discussed. Consider maintaining a design outline in the top post and update it as the discussion progresses. After a plan of action has solidified an issue for actually implementing it can be created.

Consequently, to answer:

1. Is your feature request related to a problem?

2. Describe the solution you'd like

The output of rpm -qi, of which the immediately undermentioned is a verbatim example:

Name        : code
Version     : 1.103.2
Release     : 1755709837.el8
Architecture: x86_64
Install Date: Mon 25 Aug 2025 19:31:22 BST
Size        : 453507130
License     : Multiple, see https://code.visualstudio.com/license
Signature   : RSA/SHA256, Wed 20 Aug 2025 18:15:13 BST, Key ID eb3e94adbe1229cf
Source RPM  : code-1.103.2-1755709837.el8.src.rpm
Build Date  : Wed 20 Aug 2025 18:10:40 BST
Build Host  : c967556ec000000
Packager    : Visual Studio Code Team <vscode-linux@microsoft.com>

...would be slightly easier to parse, and more readable, if each key-value-delimitative colon were prepended by a space:

Name         : code
Version      : 1.103.2
Release      : 1755709837.el8
Architecture : x86_64
Install Date : Mon 25 Aug 2025 19:31:22 BST
Size         : 453507130
Signature    : RSA/SHA256, Wed 20 Aug 2025 18:15:13 BST, Key ID eb3e94adbe1229cf
Source RPM   : code-1.103.2-1755709837.el8.src.rpm
Build Date   : Wed 20 Aug 2025 18:10:40 BST
Build Host   : c967556ec000000
Packager     : Visual Studio Code Team <vscode-linux@microsoft.com>

This is how PowerShell outputs PSObject values in List form.

Describe alternatives you've considered

None.

[pmatilai]

Yeah the one with more space is easier to look at, as trivial as it may be. Opened #3919 for this.

Thanks for the suggestion.