Andy Kipp

@Pakbon thanks for diving into this. What about this code: https://github.com/xonsh/xonsh/blob/c347bfbe8cbb0b34cd11d87a0ec28e6027c29121/xonsh/procs/pipelines.py#L402-L405 Is it what you mentioned [here](https://github.com/xonsh/xonsh/issues/5877#issuecomment-3077603589)?

I have an example from Copilot: ```xsh from xonsh.events import events import inspect def list_registered_events(): out = [] for name, evt in events.__dict__.items(): if name.startswith("_"): continue try: from xonsh.events import...

As I remember @jaraco @Qyriad @melund are Windows users so I would like to ask you to share your best setting of Windows environment (not WSL), recommendations or mention issues.

1. I think it's related to #5941. I can repeat the issue in 0.20.0 by running: ```xsh showcmd diff -U 0 --strip-trailing-cr --label /dev/shm/\#5a17e19e45e6960b3358735e4508334376cac475\#.\~\;53fff09077ac6b50d6ba4e426ecd74be173ea82c\~ --label \#\ ``` In 0.19.0 it's...

Minimal example to repeat hanging in 0.20.0 (related to https://github.com/xonsh/xonsh/pull/5941): ```xsh showcmd echo a#b;c ``` Workaround is using quotes or python substitution: ```xsh showcmd echo 'a#b;c' showcmd echo @('a#b;c') ```

> Now, since I was authed to JupyterHub, it wasn't anonymous access, but things seemed to be happy/healthy. @JohnOmernik could you please share your solution configs or algos or as...

> return ["$UV_PYTHON=@(__xonsh__.imp.sys.executable)", "uv", *args] This is not working because return_command alias returns exactly the list of arguments of a new command. It's a new feature to support env variables....

xonsh uses https://github.com/prompt-toolkit/python-prompt-toolkit so I'm recommending to open the issue there

As a start point - how to change build process - https://github.com/xonsh/xonsh/pull/5948

@jnoortheen I think before next release we need to solve this. The best to me is to heve the release note like: * Feature description (#commitnum #prnum, @commitername1, @commitername2)