changemewtf / codewalk Goto Github PK

When codewalk is run without any arguments provided, it looks for files with basename examples and uses the extension to decide what command to use to run the file.

If there are multiple files with basename examples, it runs the one with the most recent modification time.

A command line option can be provided to codewalk which causes output from a previous example to be displayed, as opposed to the example printed last.

# examples.rb
colors = %w(red white blue)

print "\nEXAMPLE 1\n"
puts "pop() from the end: #{colors.pop()}"

print "\nEXAMPLE 2\n"
puts "shift() from the start: #{colors.shift()}"

$ codewalk ruby examples.rb
shift() from the start: red

$ codewalk -e1 ruby examples.rb
pop() from the end: blue

Thoughts:

• Having to put the -e1 in the middle of the already-typed command would be time-consuming and error-prone.
• But putting -e1 at the end would be ambiguous: is the option being passed to codewalk or to the command codewalk is running (in this case ruby examples.rb)?
• Perhaps the answer is codewalk -r"ruby examples.rb" -e1
• Or codewalk <(ruby examples.rb) -e1
• Or codewalk ruby examples.rb -- -e1
• Or codewalk -r ruby -f examples.rb -e1
• Or codewalk -f examples.rb -e1 and require a shebang/executable file
• Or codewalk ruby examples.rb 1, where ruby, examples.rb and 1 are all positional parameters, as opposed to the current functionality which just evaluates "$@"