Skip to content

docs(best-shell-practices): update instructions and screenshots for Konsole#453

Draft
Wittusus wants to merge 6 commits into
ublue-os:mainfrom
Wittusus:update-shell-practices
Draft

docs(best-shell-practices): update instructions and screenshots for Konsole#453
Wittusus wants to merge 6 commits into
ublue-os:mainfrom
Wittusus:update-shell-practices

Conversation

@Wittusus

@Wittusus Wittusus commented May 2, 2026

Copy link
Copy Markdown

Summary

The default terminal on Bazzite (KDE variant) is Konsole, not Ptyxis. This PR corrects the documentation to reflect that.

Changes

  • Replace references to Ptyxis with Konsole throughout the page
  • Update navigation instructions to match Konsole's UI (hamburger menu → Settings → Configure Konsole → Profiles)
  • Update the command field description to match Konsole's terminology ("Command" box instead of "Use Custom Command")
  • Replace both screenshots with up-to-date ones showing Konsole

Testing

Verified locally with `just mkdocs serve`."

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the 'Best Shell Practices' documentation to align with the actual default terminal environment provided by Bazzite. By correcting the terminal name, navigation paths, and visual aids, the documentation now provides accurate guidance for users looking to configure their shell settings.

Highlights

  • Terminal Documentation Update: Updated the documentation to correctly identify Konsole as the default terminal for Bazzite instead of Ptyxis.
  • UI Navigation Instructions: Revised the configuration steps to accurately reflect the Konsole menu structure and settings interface.
  • Visual Assets: Replaced outdated screenshots with new images corresponding to the Konsole terminal interface.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@Wittusus Wittusus marked this pull request as ready for review May 2, 2026 14:07

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation to reflect that Konsole is now the default terminal for Bazzite, replacing Ptyxis. The changes include updated instructions for changing the shell and new screenshots. Feedback was provided regarding a typo in the text, the need to update the corresponding Czech translation for consistency, and a recommendation to host images locally within the repository's image folder using absolute paths and descriptive alt text for better accessibility and robustness.

Comment thread src/Advanced/Best_Shell_Practices.md Outdated
Comment thread src/Advanced/Best_Shell_Practices.md Outdated
Comment thread src/Advanced/Best_Shell_Practices.md Outdated
Wittusus and others added 2 commits May 2, 2026 16:10
Remove duplicated word

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@Wittusus

Wittusus commented May 2, 2026

Copy link
Copy Markdown
Author

I did the change so the docs follow Bazzite 44 newest changes which removed Ptyxis as the default terminal

@nicknamenamenick

Copy link
Copy Markdown
Collaborator

This is a good change. I might make adjustments to have both examples since GNOME images still ship Ptyxis. I'll review this later when I have more time and it will probably get merged regardless. Thanks!

@Wittusus

Wittusus commented May 2, 2026

Copy link
Copy Markdown
Author

@nicknamenamenick if it's planned for the Gnome version to include Ptyxis in the future, let me know, I can make the adjustments to include both

@nicknamenamenick

Copy link
Copy Markdown
Collaborator

@nicknamenamenick if it's planned for the Gnome version to include Ptyxis in the future, let me know, I can make the adjustments to include both

GNOME images have it now and will probably for the unforeseeable future. Even the upstream Fedora Silverblue uses Ptyxis.

@Wittusus Wittusus marked this pull request as draft May 2, 2026 20:00
@nicknamenamenick

Copy link
Copy Markdown
Collaborator

I could probably finish this, but only in English since language translations are something I'm not comfortable doing personally.

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.

2 participants