Giter Site home page Giter Site logo

42minishell's Introduction

landing-page-gif

๐Ÿ‘‹ Hello, I'm Conrad

๐Ÿ’ญ About Me

  • 42Heilbronn Student (Part of the 42Network)
  • Programmer
  • Gamer
  • Anime enjoyer
  • Always trying to learn something new

๐Ÿ“Š Github Stats

Isometric view of contributions in the last year. Language pie is based on recent commits

โœจ Overview



๐Ÿ”ง Skills:

Tech:

My Skills

Tools:

My Skills

Currently Learning:

My Skills

Tech: C, JavaScript, TypeScript, Vue, HTML, CSS, TailwindCSS
Tools: Github, Git, Stackoverflow, VSCode
Currently Learning: C++, Go

โœ‰๏ธ Get In Touch

Don't hesitate to reach out to me, whether you have a question, want to hang out, or even play a game โ€“ just give me a ping!

42minishell's People

Contributors

harshkumbhani avatar realconrad avatar

Watchers

 avatar

Forkers

harshkumbhani

42minishell's Issues

Exit status

Get correct exit status

During testing, I encountered some inconsistencies regarding the exit status code.

minishell: syntax error near unexpected token |
minishell> echo $?
258

This should not give 258 as return value. It should return 2

ctrl+c returns 0 as exit status, but should return 130.

minishell> "
minishell: unclosed quotes 
minishell> echo $?
0

returns 0 as exit status but should also return 2.

ENV fix

  1. Create a 2D array.
  2. Create Array utils for copying stuff and removing stuff

bug fixing

  • Fix the space after single and double quote.
  • Fix the waitpid for every single command as a while loop.
  • For EXPORT builtin, sorting in ascending order.
  • EXIT builtin.

Create custom built-ins

The shell must implement the following builtins:

  • echo with option -n
  • cd with only a relative or absolute path
  • pwd with no options
  • export with no options
  • unset with no options
  • env with no options or arguments
  • exit with no options

Add doxygen comments

Add doxygen comments for:

  • Lexer
  • Parser
  • Expander
  • Signals
  • Executor
  • Utils
  • Builtins
  • Structs

No collapsing pipes

Collapsing pipes

try the following command in bash and then in your shell:

cat /dev/urandom | ls

# or

cat /dev/random | ls

You will see that your shell is continuously waiting for the EOF of /dev/random/ which will never be reached and therefore your shell is getting unusable. In that scenario, your pipe should collapse and also close the filestream from cat /dev/random.

Check file access

Check if I have access to the files and return an appropriate error and error code

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.