Change how the rebound command is used

[shobrook]

Instead of executing files with the rebound command, I think it would be more user-friendly to execute the file normally, get a compiler error, and then type rebound to fetch that error and display the CLI. For example, the Python workflow would be:

1. Run $ python test.py
2. Program fails and returns an error message
3. User runs $ rebound to prompt the CLI

[kdbeall]

@shobrook Why not do the following?

python test.py | rebound

You can pipeline even further

python test.py | grep 'error:...' | rebound

I saw you had a feature request for extracting keywords from the
stack trace. Grep could do this.

[shobrook]

Well, that's kinda what running $ rebound test.py already does. It executes $ python test.py, pipes the stderr, and then prompts the CLI.

I think it would be more user-friendly to run the file normally and then run $ rebound to prompt the CLI. That way you not only cut out the "Display Stack Overflow results? [Y/n]" prompt, but you don't have to change how you normally run files.

[kezhenxu94]

As far as I know, there is no register (or anything else) in Shell to store the output of the last command, if you re-execute the last command (say the python test.py command), there may be side effects, therefore it may be difficult to achieve this.

[shobrook]

Yeahhh it doesn't look like this is doable :(