Chih-Yao Hsieh

Here are the outputs. ```zsh ❯ mamba list |grep xeus xeus 1.0.3 hf09c4ce_0 conda-forge xeus-cling 0.12.1 h79ef1c8_0 conda-forge ❯ mamba list |grep zeromq zeromq 4.3.4 h1c7c35f_0 conda-forge ❯ otool -L...

For otool output, if you are in MacOS with miniconda, you can do the followings to get your "real xcpp" absolute path. ``` > which xcpp miniconda3/envs/cling/bin/xcpp > otool -L...

Using cling version 0.5 installed from homebrew. Then following https://github.com/root-project/cling/tree/master/tools/Jupyter instruction, and it is still the case that "where is my libclingJupyter" logic seems still does not work. ``` Traceback...

This also happens for any long running scripts, such as `yarn build`, python script, etc. `Ctrl-C` will kill the prompt box - which is not the intention. The expected behavior...