How to Get in Touch About gedit

Updated

To reach the gedit project, use the two channels listed in the "Getting in Touch" section of gedit-text-editor.org: report bugs through the project's bug tracker, or join the discussion on Discourse under the Applications category with the gedit tag. These are community channels run by the project, not a general customer-support desk, so responses come from maintainers and other users rather than a guaranteed service window.

The two official channels

Purpose Where to go What to expect
Report a bug The project's bug-reporting channel linked from the "Getting in Touch" section A tracked issue that maintainers and contributors can triage
Ask questions, discuss, or follow up Discourse, in the Applications category, under the gedit tag Threaded community discussion with other users and project participants

Reporting a bug

  1. Confirm the problem is in gedit itself and not in your desktop environment or a plugin — the site describes gedit as a general-purpose editor with good GNOME integration, so desktop-level issues may belong elsewhere.
  2. Go to gedit-text-editor.org and open the "Getting in Touch" section to reach the bug-reporting link.
  3. Describe what you did, what you expected, and what happened instead, and note your gedit version and operating system.
  4. Submit and keep the issue reference so you can respond to follow-up questions.

Expected result: your report becomes a tracked item the project can act on. A common snag is filing a duplicate — search existing reports for the same symptom before submitting.

Joining the discussion on Discourse

  1. Open Discourse and navigate to the Applications category.
  2. Filter or browse by the gedit tag to find existing threads.
  3. Search the tag before posting, since your question may already be answered.
  4. Start a new topic under the same category and tag if nothing matches, and include enough detail for others to reproduce your situation.

Expected result: your question lands where gedit users and contributors look for it. The main pitfall is posting in a general category without the gedit tag, which makes the thread harder to find.

Choosing the right channel

  • Use the bug channel when something is broken and should be fixed.
  • Use Discourse when you need help, want to compare approaches, or want to discuss a feature.
  • Do not expect a private support contract: the site presents these as community contact points, and no service-level commitments are stated.

Background that helps your message

gedit is a general-purpose text editor that is easy to learn and comfortable to use. Its development began in 1998 alongside the GNOME project, and it is released under Free/Libre Open Source software licenses. Mentioning that you are using it for simple notes versus enabled advanced features for software development can help others understand your setup when you post.