David Strobach
David Strobach
The traceback is hidden within the `` element under the "Traceback (if applicable)" heading of the OP.
> Can we parallelize completions instead? We already have `$COMPLETION_IN_THREAD` (defaults to `False`).
I just tried your test on my oldish laptop equipped with i5-5200U and a 5400RPM spinning drive. It is currently dedicated to WSL testing. Even on WSL(!) the bash completer...
Hi @jnoortheen, do you think `xog` xontrib (#3896) would suit your needs?
You can, of course, use [`$XONSH_TRACEBACK_LOGFILE`](https://xon.sh/envvars.html#xonsh-traceback-logfile) variable without using the xontrib. The xontrib only creates temporary file for the log and adds `xog` command to print it.
> I have checked the code but I don't get where the traceback gets written to the file. See `$XONSH_TRACEBACK_LOGFILE` :wink:
The message about `$XONSH_TRACEBACK_LOGFILE` is already there: https://github.com/xonsh/xonsh/blob/286b177555691a905cbe5045c35a7ffee0a1dc97/xonsh/tools.py#L988-L992
OK, thanks for clarification. I got confused by the fact that the _executeStop(true)_ call is done from within the `if (period_id !== s.period.period_id) {` block which made me think it's...
Turns out that I'm not *that* bad in reading JS code. Simple `console.log(...)` revealed that the _executeStop(true)_ gets indeed called only for the first trade in a period. So for...
@jflorian, I have updated the README (see 48a564f50fc9869b86e2aba99ceb1ef39a206fe0). The KCM dialog is self-explanatory in my opinion, so no need to further instruct the user.