Document termios usage analysis in minishell project

[Copilot]

This PR provides a comprehensive analysis of termios usage in the minishell project in response to the question "termios kullaniliyormu bu projede" (Is termios being used in this project?).

Analysis Results

Summary: termios is NOT actually being used in this project.

Key Findings:

1. Documentation vs Implementation Gap: While tcsetattr and tcgetattr are listed as allowed functions in the README.md under the tty section, they are not implemented anywhere in the actual codebase.

2. Current Terminal Handling: The project uses the readline library for all terminal input/output operations instead of direct termios manipulation:

   • readline() for input
   • add_history() for command history
   • Signal handlers for interrupt handling

3. Minimal TTY Usage: Only one tty-related function is actually used:

   if (isatty(STDIN_FILENO))
       init_env((char *[]){PPROMPT, SPROMPT, NULL});

   This check determines if the shell is running interactively to decide whether to show prompts.

Technical Details:

• No termios includes: No #include <termios.h> statements found in any source files
• No raw terminal control: The shell doesn't manipulate terminal attributes directly
• Readline-based approach: All terminal interaction is handled through the readline library, which internally manages terminal settings

Conclusion:

The minishell project is designed to work with high-level terminal libraries (readline) rather than low-level terminal control (termios). This is a common and practical approach for shell implementations, as readline provides robust input handling, history management, and line editing capabilities without requiring direct terminal attribute manipulation.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.