Aetf

Isn't this #6458?

To special handle secret-tool we have to figure out a way to identify secret-tool. Obviously just checking for `/usr/bin/secret-tool` isn't reliable due to reasons in #6458.

The process name can be even easier to change, e.g. just rename a script to `secret-tool`. So I think client fingerprinting is still necessary if we ever want to special...

@ioogithub due to various limitations (mostly discussed in #6458), KPXC only remembers the decision for as long as both the client and the KPXC processes are running. This works fine...

> kmscon-patched-git + libtsm-patched-git wrote as Out-of-date "Out-of-date" .... AUR packages don't simply become out of date because there are new commits... https://wiki.archlinux.org/title/Arch_User_Repository#Flagging_packages_out-of-date That being said, I do have limited...

Makes sense. Could you rebase?

I created an AUR package: https://aur.archlinux.org/packages/unftp, source here: https://github.com/Aetf/PKGBUILDs/tree/master/unftp Haven't created a PR yet as I'm not sure how unftp wants to handle version updates. Maybe also use aurpublish and...

Archlinux AUR is one git repository per package (https://wiki.archlinux.org/title/AUR_submission_guidelines#Publishing_new_package_content). I use git subtree for all AUR packages I manage, as it keeps a single copy of clean history in both...

> a couple of script utilizing the Linux util secret-tool (getting API tokens for CLI commands,...) This is the expected behavior for secret-tool, because that's a short-living process. That will...

@gapodo which dialog are you talking about? I see you have "prompt to unlock database before searching" checked. Maybe what you saw is the database unlock dialog?