bastion

exactly.

but everybody got ~~their rocks off~~ catharsis and the feeling was expressed - even though the reason for the feeling was never addressed.

doubt

I mean sure you can use the chaos to try and get cover for something specific. But generally, people rioting are on-tilt and looking for easy targets that look like their oppressors. Then, everybody gets catharsis and the riot disappears.

It's just lazy. but, better than nothing, i guess.

rioting is not the answer. if you are going to take action, be careful and deliberate.

yeah, really lets you lay down sick code like a mad hacker. I love it.

I was just about to say that I'd be raising an error, not returning a string.

I see you understand the code well.

fair. there's a lot of only kinda ~~gun~~ fun stuff after that side from the good stuff. i gave up at math.

but where is the couple kissing?

you can zoom.

Succinctness, mainly. but honestly, that succinctness ~~call~~ can also be mostly acquired using sh.py, which is what I normally use if I'm using python as a sort of shell scripting - mostly because sh.py is a very minimal requirement, whereas Xonsh has quite a few dependencies.

addendum: I'd say, if you're already using Xonsh, and aren't really looking to share your script with anyone other than Xonsh users or your own systems, you'd probably like to use .xsh scripts. But if you're looking to share your script, use sh.py.

Yeah, I think if I wasn't familiar with Python, it'd be nushell all the way.

thanks, good thread.

It's a superset of python, so valid python should run fine. Imports into your shell are doable, too -- for example, I import path.Path in my xonshrc, so it's always available when I hit the shell. I don't often have to use Path, because regular shell commands are often more straightforward. But when I do, it's nice to have it already loaded. Granted, that could get kooky, depending on what you import and execute.

You can associate/shebang Xonsh with .xsh files, or run "xonsh foo.xsh" - and that works like "bash foo.sh" would, except using xonsh syntax, of course.

It's not Bash compatible - copypasta of scripts may not work out. But it's a good shell with some typical shell semantics.

there are some great plugins, too - like autovox, which allows you to create python venvs associated with specific subfolders. so, cd myproject does the equivalent of cd myproject; . path/to/venv/bin/activate.

overall, there definitely is some jank, but it's a great tool and I love it.