pileon / shelley Goto Github PK

Design, requirements, use-cases or user stories, initial milestones.

after

  git clone [email protected]:pileon/shelley.git
  mkdir _Build
  cd _Build
  cmake ..
  make

[ 33%] Building CXX object src/CMakeFiles/shelley.dir/shelley.cpp.o
/usr/src/Shells/shelley/src/shelley.cpp: In function ‘void {anonymous}::execute_command(const command&)’:
/usr/src/Shells/shelley/src/shelley.cpp:49:59: error: ‘strerror’ was not declared in this scope; did you mean ‘stderr’?
49 | std::cerr << "shelley: " << cmd[0] << ": " << strerror(errno) << '\n';
| ^~~~~~~~
| stderr
/usr/src/Shells/shelley/src/shelley.cpp: In function ‘void {anonymous}::wait()’:
/usr/src/Shells/shelley/src/shelley.cpp:57:81: error: ‘strerror’ was not declared in this scope; did you mean ‘stderr’?
57 | std::cerr << "Error waiting for child process: " << errno << ' ' << strerror(errno) << '\n';
| ^~~~~~~~
| stderr
/usr/src/Shells/shelley/src/shelley.cpp: In function ‘void {anonymous}::process_commands(const std::vector<std::vector<std::__cxx11::basic_string > >&)’:
/usr/src/Shells/shelley/src/shelley.cpp:81:75: error: ‘strerror’ was not declared in this scope; did you mean ‘stderr’?
81 | std::cerr << "Error forking process: " << errno << ' ' << strerror(errno) << '\n';
| ^~~~~~~~
| stderr
make[2]: *** [src/CMakeFiles/shelley.dir/build.make:76: src/CMakeFiles/shelley.dir/shelley.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:98: src/CMakeFiles/shelley.dir/all] Error 2
make: *** [Makefile:91: all] Error 2

Add more unit-testing

Testing the functions in the utility namespace.
Testing get_input.

Testing the whole process-fork-wait mechanism is hard, as is the process-fork-exec mechanism.

Show a simple prompt so the user knows when to input commands.

Simple function to change directory.

No special path-parsing (like ~) handled

Check entered commands for built-in commands.

Currently will only support the cd command.

Add build-target to run code coverage using the unit-tests.

Will simply split on white-space.

1. Multiple white-space are translated into a single space (' ').
2. Store sub-strings into a collection
3. The first element in the collection (at index 0) is the command

Do the prompting, command parsing and command execution in a loop.

Read a single line of input from standard input and store in a string.

This is a simple step to prepare for command sequencing later.

A build-target to run Valgrind with the unit tests.

Make use of the Travis CI continuous integration system.

Should only build develop, master and the release branches.

Specifically handle tilde-paths, like e.g.

• ~/path for paths relative to the users home directory
• ~user/path for paths relative to another user