desktop: add trailing semicolon to Keywords and expand keyword list

[add-uos]

Add 'resources', 'monitoring', 'performance' keywords to improve discoverability in desktop search. Also add trailing semicolon for consistency with the Categories style in the same file.

Ref: https://specifications.freedesktop.org/desktop-entry/1.0/value-types.html
Ref: https://specifications.freedesktop.org/desktop-entry/latest/value-types.html
Ref: https://specifications.freedesktop.org/desktop-entry/latest/recognized-keys.html

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3a37497f-62fd-4998-9b58-4ffa36c6a0b9

📥 Commits

Reviewing files that changed from the base of the PR and between 89eaede and bcbebfe.

📒 Files selected for processing (1)

• htop.desktop

---

📝 Walkthrough

Walkthrough

The Keywords field in htop.desktop is expanded from system;process;task to system;process;task;resources;monitoring;performance;, adding three keywords that better describe htop's functionality. The trailing semicolon is included to comply with the XDG Desktop Entry specification requirement that semicolon-separated list values be terminated with a delimiter.

Poem

Three keywords join the list today,
Resources, monitoring lead the way.
Performance follows, keywords grow.
A trailing semicolon seals the flow.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[BenBE]

I think while addressing this, we also could add some related tags like resources and monitoring. Any others that might be worth including?

Also, from the linked docs, the trailing ; is marked as SHOULD (only if no keywords are present, a single ; is marked as MUST).

[add-uos]

@BenBE Thank you for the feedback! I agree that expanding the keywords would be helpful for discoverability. I'd like to propose adding resources, monitoring, and performance, so it would become:

Keywords=system;process;task;resources;monitoring;performance;

Regarding the trailing semicolon — while the latest spec marks it as SHOULD, I thought it would be nice to keep it consistent with the existing Categories style in the same file, which already uses a trailing semicolon. That said, if removing the trailing semicolon is preferred for alignment with the latest spec, I'm fine with that too!

[BenBE]

Those additions sound reasonable. Just wanted to avoid changing that file just to add a semicolon that's optional. ;-)

Can you update the PR by amending its commit to include these additional keywords?

[add-uos]

Okay, I'll update it right away.