Skip to content

Change default sort mode to BottomUp (AUR-first) and update manpage#1455

Open
hereparvezali wants to merge 1 commit into
Morganamilo:masterfrom
hereparvezali:feat/default-bottomup
Open

Change default sort mode to BottomUp (AUR-first) and update manpage#1455
hereparvezali wants to merge 1 commit into
Morganamilo:masterfrom
hereparvezali:feat/default-bottomup

Conversation

@hereparvezali
Copy link
Copy Markdown

What: Change default sort mode to BottomUp so interactive searches show AUR packages first. Update man/paru.8 to reflect new default.

Why: Matches common user expectations (yay-like AUR-first). Users can still override via CLI flags or config.

Testing: Built with cargo build --release and verified interactive behavior.

@hereparvezali hereparvezali changed the title Change default sort mode to BottomUp (AUR-first) and update manpageChange default sort mode to BottomUp (AUR-first) and update manpage Change default sort mode to BottomUp (AUR-first) and update manpage Dec 11, 2025
@pfeifferj
Copy link
Copy Markdown
Collaborator

the non bottomup behaviour matches pacman's behaviour (e.g. pacman -Ss) and users can just configure their preference in the conf

@hereparvezali
Copy link
Copy Markdown
Author

@pfeifferj I think it is inconvenient. lot of people use paru but not all people edit configs always. for better UX it should be in.

@pfeifferj
Copy link
Copy Markdown
Collaborator

paru wraps pacman, so matching pacman's default behavior is the more consistent choice.

I would argue that if this is indeed as inconvenient for users as you say it is, then surely they will look into the config options- that's exactly what config files are for.

changing the default means users who expect pacman-like behavior would now need to configure around it instead, which seems like trading one group's convenience for another's without a clear benefit.

@PaddiM8
Copy link
Copy Markdown

PaddiM8 commented Jan 24, 2026

changing the default means users who expect pacman-like behavior would now need to configure around it instead, which seems like trading one group's convenience for another's without a clear benefit.

That is true, but I would bet that the vast majority of users prefer the yay-like behaviour. If I search for something that yields a lot of results (which is most of the time), obviously I want the most relevant result to be the most visible one. If the most relevant result is at the top of the list, I have to scroll all the way at the top to see it, which is not feasible in a lot of cases. I struggle to see why anyone would prefer that and everyone I have talked to about paru vs. yay has agreed with this. I would like to recommend paru to people because it is great in every other way, but it makes more sense to recommend yay since it does not need to be configured to have good UX. I don't think it's bad for a wrapper to improve the behaviour of the program it wraps around.

@pfeifferj
Copy link
Copy Markdown
Collaborator

pfeifferj commented Jan 24, 2026

hey @PaddiM8 I talked to Lu about it a few weeks ago, and we landed on this: #1493.

curious to hear your thoughts on this compromise, where the new default behaviour would be TopDown ordering for non-interactive operations, and BottomUp ordering for interactive menus where users select packages

@PaddiM8
Copy link
Copy Markdown

PaddiM8 commented Jan 24, 2026

@pfeifferj That sounds ideal to me! Very nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants