- Does having direct access to Python really make your work in command line faster/easier?
- Is there some paradigms that are more difficult to express in xonsh (redirect, pipes, …)
- Did you happen to encounter bugs, or made mistakes without intent to do it (like overwriting/removing files, …) ?
In other words, without the performance problem, would you continue to use xonsh and recommend it?
Easier for me to write custom commands/aliases. I'm sure I could come up with creative uses for it - just haven't taken the time to do so. Also, I'm not a super sed/awk user, so that's an example where knowing Python helps.
>Is there some paradigms that are more difficult to express in xonsh (redirect, pipes, …)
Haven't run across any. I think a few may be mentioned in the docs, though.
>Did you happen to encounter bugs, or made mistakes without intent to do it (like overwriting/removing files, …) ?
Bugs: Yes - only applicable for Windows. In Windows, environment variables are case-insensitive, but xonsh still treats them as case sensitive (as in setting ABC=5 and subsequently abc=7 ends up with two env vars) caused a problem with bat scripts I ran as part of a build process. Filed a bug - I'm sure they'll fix it.
Anything serious like overwriting/removing? Nope.
Caveat: I'm not a serious, power shell user. For me, just having a decent history, line editor, autocompletion was great. However, there is nothing that I'm used to in zsh in Linux that I clearly miss in xonsh. I'm sure I've thought a few minor things where it'll probably trivial for me to customize xonsh to get that zsh behavior...