Description of problem:

The default search sorting tends to produce output that is arranged by line length. This makes it very hard to easily and quickly scan the output.

For example if you were expecting a package with a <name>-postfix to logically follow on the next line after the <name>, you might find it halfway down the list from <name>

A contrived example would be searching for "rust" expecting that all "rust" packages be grouped, in order to find a package you know is named "rust-" but are unsure of the postfix and expect the postfix might describe the required package or provide an easily digested hint:


============ Name & Summary Matched: rust ============
rust.x86_64 : The Rust Programming Language
rust-doc.x86_64 : Documentation for Rust
rust-gdb.noarch : GDB pretty printers for Rust
rust-lldb.noarch : LLDB pretty printers for Rust
rust-std-static.i686 : Standard library for Rust
rust-std-static.x86_64 : Standard library for Rust
python3-rust2rpm.x86_64 : Convert Rust packages to RPM
p11-kit-trust.x86_64 : System trust module from p11-kit
rust-src.noarch : Sources for the Rust standard library
p11-kit-trust.i686 : System trust module from p11-kit
python3-rustcfg-tests.noarch : Tests for python3-rustcfg
rustfmt.x86_64 : Tool to find and fix Rust formatting issues
python3-rustcfg.noarch : Rust cfg expression parser in python
rust-srpm-macros.noarch : RPM macros for building Rust source packages
rust-debugger-common.noarch : Common debugger pretty printers for Rust
rust-analysis.x86_64 : Compiler analysis data for the Rust standard library
perl-Module-Install-TrustMetaYml.noarch : Trusts META.yml list of dependencies
rust-packaging.x86_64 : RPM macros for building Rust packages on various architectures


In this case "rust-analysis" may have been the desired package. Searching for a python package perhaps, this issue is exacerbated a great deal. 


Expected results:

Do not break expected UX. The usual output sorting for a CLI tool of most sorts, is to output sorted alphanumerically by default unless the user specifies otherwise.

DNF should not attempt to provide a default behaviour that is contrary to established and expected UX. Or at the very least there should be a CLI switch option or config setting to select the required search output behaviour.