This is probably another question you ^_^.
I am starting to get more familiar with the RDataFrame and how to efficiently use it, thank you for your previous help.
While learning RDataFrame, and while exploring a dataset, I find the ROOT interpreter very valuable to quickly try some things out. This is actually one of the reasons I am trying to adopt RDataFrame. However, my typing skills (and memory) could improve, so rather frequently my commands have one typo or another. See below.
With some typos, ROOT will gracefully point out what I did wrong, with some there is a very large crash report, and with some the uncaught exception ends the session.
I was wondering if there is a way to make at least the last case more tolerant to typos?
Maybe there is some way to catch the exceptions?
Example - First error is gracefully handled, second error ends the session.
root  auto h =fnode.Hist1D("not_available_name") ROOT_prompt_4:1:15: error: no member named 'Hist1D' in 'ROOT::RDF::RInterface<ROOT::Detail::RDF::RNodeBase, void>' auto h =fnode.Hist1D("not_available_name") ~~~~~ ^ root  auto h =fnode.Histo1D("not_available_name") libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: Unknown column: not_available_name
ROOT Version: 6.22.99
Platform: MacOS & Centos 7
Compiler: clang 11.03 & gcc 9.3.0