Repository navigation
add seance as a desktop search keyword - #11
Merged
Merged
Conversation
no1msd
changed the title
seance as a desktop keyword.
Owner
|
Thanks @mintchaos for the fix! Landed on PR CI passed, including the explicit GUI suites. The source and installed desktop entries also passed validation, and GIO reads the new ASCII search keyword correctly. |
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Searching for
seancedoes not find Séance in launchers that do not fold accents, as reported with Vicinae. Add the ASCII spelling to the desktop entry’s search keywords so those launchers can find it, while retaining the displayed name and existing keywords.Validation:
zig build; validation of both source and installed desktop entries withdesktop-file-validate; GIO inspection of the installed keywords; 167 unit tests; 24 E2E tests and three Ghostty integration tests under Xvfb; six Codex wrapper tests. The optional live Codex test was skipped.