https://github.com/azersd/minishell
https://github.com/azersd/minishell
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/azersd/minishell
- Owner: AzerSD
- Created: 2023-04-21T01:51:19.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2023-10-28T20:11:07.000Z (over 2 years ago)
- Last Synced: 2025-02-15T19:52:49.272Z (over 1 year ago)
- Language: C
- Size: 4.13 MB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.MD
Awesome Lists containing this project
README
references:
bash_manual
bash_source_code
## Features
- [ ] Structure
- [x] Init
- [x] Input
- [x] Lexer
- [x] Parser
- [ ] Expand
- [x] Special Parameters: One of `@`, `*`, `#`, `?`, `-`, `$`, `!`, or `0`
- [x] A Variables name
- [x] A variable name surrounded by `{` and `}`
- [x] An arithmetic expansion, surrounded by `(` and `)`
- [ ] A command substitution, surrounded by `((` and `))`
- [ ] Positional Parameters `$0`, `$1`, `$n`, `$#`, `$@` and `$*`
- [x] Ast
- [x] Execution
- [ ] Builtins
- [x] Line editing
- [x] Simple and advanced line editing
- [x] Edit the line where the cursor is positionned
- [x] Move cursor left or right
- [x] Up and Down arrows to navigate in the history
- [ ] Enter Insert mode with `alt+i` and exit it with `alt+i`
- [ ] Copy and paste with `alt+C` `alt+v`
- [ ] Move word per word left or right `alt+LEFT` `alt+RIGHT`
- [ ] Go to beginning or end of a line. `home` `end`
- [ ] Move to top or bottom line. `alt+UP` `alt+DOWN`
- [ ] Waits for the end of a quote or double quote.
- [ ] ctrl+D and ctrl+C usable when editing a line or in multi-line.
- [ ] Multiline line editing
- [x] Builtins with their POSIX options (For more info type `help` once in the shell)
- [x] `cd` | `chdir`
- [x] `echo`
- [x] `exit`
- [x] `env`
- [x] `setenv`
- [x] `unsetenv`
- [x] `unset`
- [x] `export`
- [x] `history`
- [x] `pwd`
- [x] Exec
- [x] Executing commands stored in path with their parameters
- [x] Error handling and return value handling
- [x] Redirections handled : `>`, `<`, `<<` and `>>`
- [x] Pipes `|`
- [ ] Logical operators `&&` and `||`
- [x] Backquotes "‘" (TODO)
- [ ] Ihibitors """ (double quote), "’" (simple quote) et "\" (backslash).
- [ ] `;`
- [ ] `\n` handling where `\n` can be used as a `;`. Example: `ls \n ls` == `ls ; ls`
- [x] Prompt
- [x] Multi line editing with `\`, `'` and `"`
- [x] History handles the multi-line editing
- [ ] Shell
- [ ] This shell proposes multiple options to enhance user experience
- [ ] `h` This option will display help for all options as described here
- [ ] `v` Verbose mode
- [ ] `d` Debug mode (Enables the logger). A log file will be created where the binary exists. This option requires a log level from 0 to 7
- [ ] `t` Test mode. This mode will test the module `X` with `Y` parameter as follows : `-t X Y`. Can be used with modules `env` `ast` `parser` `lexer` `ast`
- [ ] `c` Command. Use this option to send a command to the shell and get it's output
- [ ] `C` Color. Use this option to enable color in the shell
- [ ] `l` Disables the termcaps. This is a debug option and not a feature ! To be used lightly
- [x] Signals
- [x] We kill all childs when we get a signal that kills the program so no zombie process is left behind
- [ ] Autocompletion
- [ ] Dynamic autocompletion
- [ ] Autocompletes binaries from `PATH`
- [ ] Autocompletes files and paths
- [ ] Autorefreshing with a new input from the user: modification of the list of possibility. TODO WIP
- [x] Environ
- [x] Local Variables are available
- [x] Normal environment is used when the shell is started
- [x] Uses the `=` syntax (`VAR=VALUE`)
- [x] Default env is given when **42sh** is started with env -i (TODO to be customized)
- [x] Message to warn the User when **42sh** is started without an env
- [x] Bonuses
- [x] Heredocs "<<".
- [x] File descriptors aggregation
- [x] History
- [x] A menu is printed when the history fil is to big
- [x] The history is printed in the log when exiting the program
- [ ] History research `ctrl+R.`
have fun. Programming can be a lot of fun, and if you’re not generally having fun, you’re not in the right mindset to be programming. Tired or unhappy programmers make mistakes, and debugging code tends to take much longer than writing it correctly in the first place! Often you can save yourself some time by going to bed, getting a good night’s sleep, and coming back to a problem in the morning.