Replies: 1 comment
|
We can work on extending our functions later, but rn we gotta work on cleaning up our project’s codebase to make it ready for the future, while also making sure that every functionality that’s provided/worked upon, gets to be used properly. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🔴 CRITICAL FIXES (MUST HAVE)
│
├ ✅ DONE─ #94: Terminal raw mode cleanup on panic/exit
│ └─ Impact: User can recover from crashes (UX critical)
│
├─ #93: Proper POSIX signal handling (SIGINT/SIGTSTP/SIGCHLD)
│ └─ Impact: Ctrl-C/Ctrl-Z/job control reliability
│ └─ Subtasks:
│ ├─ Implement signal-hook based handlers
│ ├─ Fix process group management (setpgid/tcsetpgrp)
│ ├─ Add zombie process cleanup
│ └─ Write comprehensive signal tests
│
└─ #95: Job table race conditions
└─ Impact:
fg,bg,jobsreliability✅ TOKENIZATION & EXPANSION$VAR, $ {VAR}, $?, $ #, etc.)
├─ ✅ DONE: shlex tokenization (PR #103)
├─ ✅ DONE: globset + shellexpand (PR #103)
│
└─ TODO: Variable expansion (
└─ Implement in parser.rs
└─ Priority: High (scripts rely on this)
📝 DOCUMENTATION
├─ Write CONTRIBUTING.md with v3.1 focus
├─ Add "Known Limitations" section to README
│ └─ Signal handling in progress, avoid backgrounding
└─ Link to GitHub Discussions for troubleshooting
-# Special thanks to copilot for the Roadmap
All reactions