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

🐞 macOS Text Editing Keys Not Fully Working

Open
#1,903 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
macos, swift
Domain
desktop

Research direction

Start by reproducing the Option-based readline commands in CodeEdit.app on macOS, especially Ctrl-Opt-f and Ctrl-Opt-b, and inspect the app's keyboard handling entry points. Done means the listed macOS text-editing commands move the cursor or perform their command without producing a beep.

Written by the indexing model from the issue text.

Description

bug other P1
Description

I utilise the readline style text commands supported by macOS such as Ctrl-f and Ctrl-b to move forward and backwards a character, normally I would be able to use Ctrl-Opt-f and Ctrl-Opt-b to move forward and backward a whole word, inside of CodeEdit.app this does not work and I am met with the macOS beep sound.

If you could get this functionality setup and fixed I would definitely consider using this application for all coding that can'd be done in Xcode.

You can see the full list of supported commands here under Move around within a document.

To Reproduce
  1. open a file in the app
  2. try to use readline commands that utilise Option
  3. hear the beep
Expected Behavior

The cursor should move forward or backward a word, or perform whichever other command you input via the keyboard.

Version Information

CodeEdit: Version 0.3.2-alpha (43)
macOS: Version 15.1 Beta (24B5070a)
Xcode: Version 16.0 (16A242d)

Additional Context

No response

Screenshots

No response

Dominant language
Swift
Stars
23k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 CodeEditApp/CodeEdit

All issues in CodeEditApp/CodeEdit

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.