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

Configurable delay for automatic dictionary correction suggestions

Open
  • Is something wrong?
#1,255 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
accessibility, desktop

Research direction

Start with Sources/Fluid/Services/AutomaticDictionaryCorrectionTracker.swift at the linked beta tag and inspect handleObservedSelectionChange and its existing 3-second and 1-second delays. Then trace the Learn from my corrections setting to find where its controls are defined and how settings are stored. Done means offering the four requested delay values with 3 seconds as the default and avoiding timer resets for duplicate selection ranges; the issue says the local experiment has not been manually validated in the target editor.

Written by the indexing model from the issue text.

Description

Problem

After manually replacing a misrecognized word, the dictionary suggestion can take long enough to appear that it seems broken. In my recent testing it eventually appeared after I stopped interacting with the editor.

Environment: FluidVoice 1.6.13-beta.1, macOS 26.6.2, Apple Silicon. Learn from my corrections is enabled and set to ask after one correction. This happened in the ChatGPT/Codex desktop editor. The delay was not measured, and I have not isolated a reproducible mouse-movement trigger.

Proposed option

Add a prompt delay setting next to Learn from my corrections, with 0.75, 1, 2, and 3 seconds. Keep 3 seconds as the default. The shorter choices would let users opt into faster suggestions while accepting that a pause in the middle of editing might trigger a prompt.

There is also a related behavior worth fixing: in the beta source, handleObservedSelectionChange schedules a new evaluation for every selection notification, even if the selected range has not changed. Ignoring duplicate range notifications should prevent those events from repeatedly postponing evaluation. Actual text edits and selection changes would still reset the appropriate timer.

Source: AutomaticDictionaryCorrectionTracker.swift at v1.6.13-beta.1. The existing delays are 3 seconds for inactivity and 1 second after a completion signal.

Related to #272. Would this small settings option and duplicate-notification fix be an acceptable scope for a contribution? A local experimental patch is being compiled and tested; this issue requests approval for the upstream UI change, and no PR has been submitted.

Codex helped inspect the source and draft this proposal. The local patch has not yet been manually validated in the target editor.

Dominant language
Swift
Stars
11.9k
Forks
863
Avg merge
1d 7h
Merged PRs (30d)
37

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 altic-dev/FluidVoice

All issues in altic-dev/FluidVoice

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.