awalter-bnl

Just a a quick point, this is a detail but just wanted to capture it. yesterday one of our beamline staff ran into an issue which he didn't understand at...

> Would a better solution be to improve our error message? Agree this would probably be a better solution.

@teddyrendahl, what about the `plan_stubs` `mv` and `mvr` for instance. I think them (and other similar `plan_stubs`) should be wrapped. These are `plan_stubs` that _can_ be run on their own....

I am up for putting all of them out temporarily and seeing which ones users prefer. I _suspect_ option 2 will be widely ignored and that option 1 will be...

I am pausing at this point to allow for feedback on what already exists. As the next step is to go through each of the 'combined plan_stubs' like ``trigger_and_read`` I...

@danielballan is this looking better?

@danielballan That suggestion was so obvious I feel stupid for not thinking of it myself. I have made the change.

FYI the failed tests is in python 3.6 for linux build and is an unrelated timeout error in ``tests/test_callbacks.py/test_broker_base``. This is unrelated to the current work, and is marked as...

So I was about to start adding the custom messages to the ``plan_stubs`` that yield from other ``plan_stubs``, but happened upon a slightly different approach to what was previously suggested....

@danielballan you are correct, sort off, the benefit of my solution is one exception, chained messages where as you have chained exceptions which do not print to the command line...