Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature]: Run the Script pane with Ctrl+Enter (⌘+Enter on macOS)

Open Beginner friendly
#773 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
83/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust

Research direction

Start with sqlbox.rs to follow the existing Ctrl+Enter handling, then find the Script pane's Run button and script editor. Keep the shortcut limited to editor focus and share its execution path with the button; preserve Enter and suggestion-list behavior. Update the tooltip and docs/user-guide/analysis.md, then add the described test verifying the script runs without changing its text.

Written by the indexing model from the issue text.

Description

enhancement
Before you start
What problem does this solve?

The Script pane (Analyze › Script) can only be run with its Run button. While writing and testing a script, every run means leaving the keyboard for the mouse, and then clicking back into the box to keep editing.

The SQL pane already runs its query with Ctrl+Enter (sqlbox.rs, documented in docs/user-guide/data.md), so the Script pane is the odd one out.

Proposed solution

With the focus in the Script box, Ctrl+Enter (⌘+Enter on macOS, egui::Modifiers::COMMAND) runs the script, as the Run button does:

  • The key is taken before the box sees it, so it runs the script and does not break the line. This is how sqlbox.rs does it.
  • It only applies while the Script box has the focus. Elsewhere the key does nothing new.
  • The box keeps the focus after the run, so editing goes on.
  • Plain Enter, and Enter or Tab while the suggestion list is open, keep their current meaning.
  • The Run button and the shortcut share one code path, so they can't drift apart.
  • The Run button's tooltip names the shortcut, and the Script paragraph of docs/user-guide/analysis.md mentions it.
  • A test checks that Ctrl+Enter with the focus in the box runs the script and leaves the text unchanged.
Estimated scope

Small: a minor tweak, small UI change, or text adjustment

Alternatives considered
  • Shift+Enter, as in notebooks. Ctrl+Enter matches the SQL pane, and one shortcut for "run what I typed" across panes is easier to learn.
  • A global keymap entry (keymap.rs). The shortcut only makes sense while the Script box has the focus, so it belongs with the box, as in the SQL pane.
Dominant language
Rust
Stars
1.9k
Forks
268
Avg merge
3h 1m
Merged PRs (30d)
556

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opengeos/RustGIS

All issues in opengeos/RustGIS

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.