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

Register Machines: a code path is accepted on its file name alone

Open
#318 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
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
desktop

Research direction

Start with the Register Machines Find action and the typed-path entry, which accept any executable matching a code name, and with the job-script check added in 9.1.0 that refuses the screen reader. The proposal needs a per-code identity probe, such as running orca --version or reading the program banner, plus a Check button that reports what was found. Done means Find and the typed path reject a wrong binary and the button shows the identity. The payload names no files, and the maintainers have already planned this for 9.2.0.

Written by the indexing model from the issue text.

Description

Register Machines (Find, and a typed path) accepts any executable whose name matches the code. On one machine the path 'orca' resolved to /usr/bin/orca, the GNOME screen reader, so a job started the screen reader instead of ORCA. Since 9.1.0 the job script refuses that particular file with a message, but the general gap remains.

Proposal: check each code's identity with a harmless command (for example orca --version, or the program's banner) in Find, plus a Check button next to the path that reports what was found.

Planned for 9.2.0.

Dominant language
C
Stars
10
Forks
8
Avg merge
21m
Merged PRs (30d)
1

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 FriendsofECCE/ECCE

All issues in FriendsofECCE/ECCE

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.