Skip to content

Merge pull request #1 from GideonBature/dev #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 59 commits into
base: dev
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
59 commits
Select commit Hold shift + click to select a range
0dee673
proto remove value
wrightkhlebisol Jul 20, 2023
8395bfd
remove value at key
wrightkhlebisol Jul 20, 2023
b845793
fix struct next
wrightkhlebisol Jul 22, 2023
345b891
add node to list
wrightkhlebisol Jul 22, 2023
451c629
remove value from node
wrightkhlebisol Jul 22, 2023
5150104
fix conflict
wrightkhlebisol Jul 22, 2023
15bc18a
Tokenize env
wrightkhlebisol Jul 22, 2023
44a1c97
proto correct return for exis_cmd
wrightkhlebisol Jul 22, 2023
a8b8211
return exit code
wrightkhlebisol Jul 22, 2023
435b9df
fix undeclared var head
wrightkhlebisol Jul 22, 2023
d89f848
pointer for strtok
wrightkhlebisol Jul 25, 2023
7f76c21
doc struct
wrightkhlebisol Jul 25, 2023
de3583b
Fix conflicts
wrightkhlebisol Jul 25, 2023
271b186
fixed linkedlist
wrightkhlebisol Jul 25, 2023
a437728
free list
wrightkhlebisol Jul 25, 2023
39eda65
remove main
wrightkhlebisol Jul 25, 2023
a1f20a9
Merge pull request #1 from GideonBature/dev
wrightkhlebisol Jul 25, 2023
bb57b9d
insert end
wrightkhlebisol Jul 25, 2023
ef632f2
remove null point for lineptr
wrightkhlebisol Jul 25, 2023
0289d01
fix header conflict
wrightkhlebisol Jul 25, 2023
9a16fb2
resolve merge conflict
GideonBature Jul 25, 2023
a104a7e
exit with code
wrightkhlebisol Jul 25, 2023
97e9063
check that argv error code exists
wrightkhlebisol Jul 25, 2023
97ae423
Fix accented chars
wrightkhlebisol Jul 25, 2023
f82505d
fix merge errors
wrightkhlebisol Jul 25, 2023
1d4e4c6
setenv, unsetenv
wrightkhlebisol Jul 25, 2023
649935b
uncomment send unsetenv
wrightkhlebisol Jul 25, 2023
9f9182d
ignore swap files
wrightkhlebisol Jul 25, 2023
97955ab
Fix betty errors
wrightkhlebisol Jul 25, 2023
8791d72
recieve head in exec_builtin
wrightkhlebisol Jul 25, 2023
7ebc8e7
refactor set unset env
wrightkhlebisol Jul 25, 2023
469ab6f
indent for betty
wrightkhlebisol Jul 25, 2023
f1d8e0a
Fix betty errors
wrightkhlebisol Jul 25, 2023
ef780d9
betty error fix
wrightkhlebisol Jul 25, 2023
9a39aef
documentation for struct
wrightkhlebisol Jul 25, 2023
766b5d4
fix betty
GideonBature Jul 26, 2023
d4386c1
implement the cd built-in function and fix the global variable issue
GideonBature Jul 26, 2023
7c84497
fix whole code for full compilation
GideonBature Jul 26, 2023
90ab2da
initialize lineptr with NULL
GideonBature Jul 26, 2023
4aa30f7
add a return statement to env_cmd
GideonBature Jul 26, 2023
e0ec559
remove return statement from env_cmd
GideonBature Jul 26, 2023
5d9af9c
Print all node
wrightkhlebisol Jul 26, 2023
50fc326
tokenize env prop
wrightkhlebisol Jul 26, 2023
a74aaac
prototype print_all and init_env
wrightkhlebisol Jul 26, 2023
2c949eb
Fix merge conflicts
wrightkhlebisol Jul 26, 2023
9c512a4
fix conflict
wrightkhlebisol Jul 26, 2023
acb1d61
fix betty return error
wrightkhlebisol Jul 26, 2023
a7a4175
refactor initi head
wrightkhlebisol Jul 26, 2023
3851b28
Fix memory leaks
wrightkhlebisol Jul 26, 2023
d603c6a
betty fix
wrightkhlebisol Jul 26, 2023
56085ad
return 127
wrightkhlebisol Jul 26, 2023
41159d7
add readme file
GideonBature Aug 9, 2023
01dd235
add everything you need to know readme file
GideonBature Aug 9, 2023
1be3638
add approaching the project readme file
GideonBature Aug 9, 2023
752691a
add readme file for framework
GideonBature Aug 9, 2023
fbee2b8
add pair programming readme file
GideonBature Aug 9, 2023
afb8fa4
final arrangement of the readme file
GideonBature Aug 9, 2023
c635f3d
remove vscode hidden directory
GideonBature Aug 9, 2023
06bc9c9
remove test directory
GideonBature Aug 9, 2023
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,3 +1,6 @@
simple_shell_project
allowed_functions
test
*.swp
*.out
hsh
6 changes: 0 additions & 6 deletions .vscode/settings.json

This file was deleted.

8 changes: 4 additions & 4 deletions AUTHORS.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# This file lists all contributors to the repository.

Caleb Ogundiya <calebogundiya@gmail.com>
Gideon Bature <infoaboutgideon@gmail.com>
# This file lists all contributors to the repository.
Caleb Ogundiya <calebogundiya@gmail.com>
Gideon Bature <infoaboutgideon@gmail.com>
833 changes: 291 additions & 542 deletions README.md

Large diffs are not rendered by default.

28 changes: 28 additions & 0 deletions concepts/approaching/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
Approaching a Project
=====================

It can be difficult to know how to approach a project. You’ve read resources and tried some examples, and now it’s time to apply what you know. Where do you start? The following framework can help you focus how you approach a project.

Read the steps below and think about how you would follow them for a task.

1. Read the task or challenge.
2. Rephrase it in your own words.
3. Verify expected behavior by getting example inputs and outputs.
4. Whiteboard your solution with words.
5. Walk through your solution with an example as if you were a machine. Do only what is written down. Correct your solution if needed.
6. Whiteboard your solution with pseudocode.
7. Walk through your solution with an example as if you were a machine. Do only what is written down. Correct your solution if needed.
8. Whiteboard your solution with code.
9. Walk through your solution with an example as if you were a machine. Do only what is written down. Correct your solution if needed.
10. Write your code on your computer. _\[Note: This is this first time you are using your computer! Only when you know_ **exactly** _what to code.\]_
11. Test your code on your computer.
12. Debug if necessary.
13. You complete the task or challenge!

Be sure to break your task or project into smaller and smaller pieces, until you are comfortable solving each piece with the above steps.

When you are in step 10, “Write your code on your computer”, you should code each piece one at a time and debug right after each small step to make sure everything works properly. This will also prevent you from having to debug multiple pieces at the same time and thus, will make your life much easier.

---

Copyright © 2023 ALX, All rights reserved.
Loading