You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our PDF a case like /bin/echo \$USER should not be covered, since it states that \ shouldn't be covered at all. Same goes for env -i $MINISHELL_PATH"/"$EXECUTABLE, since env should not accept any options or arguments. I'm assuming the PDF for all campuses is the same.
Should we create a new folder called extra where we move all of those tests there, to prevent confusion, but still keep them for people who want to try them, since this is not mandatory to cover?
The text was updated successfully, but these errors were encountered:
Maybe, but it's a minor thing. If you are that bored, you are welcome :D Env -i is only there to check for segfaults which you can protect in like 2 minutes or take the challenge and make it work, you will see interesting things.
The same goes for the escape characters.
In our PDF a case like
/bin/echo \$USER
should not be covered, since it states that\
shouldn't be covered at all. Same goes forenv -i $MINISHELL_PATH"/"$EXECUTABLE
, sinceenv
should not accept any options or arguments. I'm assuming the PDF for all campuses is the same.Should we create a new folder called
extra
where we move all of those tests there, to prevent confusion, but still keep them for people who want to try them, since this is not mandatory to cover?The text was updated successfully, but these errors were encountered: