#xonsh — Public Fediverse posts

Attention, terminal #nerd topic ahead: If you want to use the #broot tool[1] in macOS Terminal.app, you have to set "Use Option as Meta key" in Terminals settings as shown here https://github.com/Canop/broot/issues/86#issuecomment-574398860.

Only then ALT-ENTER works to open and close broot and change directories.

To install, `brew install broot`.
If you use #xonsh, `xpip install xontrib-broot` to make the `br` alias available. Then set `$UPDATE_OS_ENVIRON = True` in `~/.xonshrc` file.

[1]: https://dystroy.org/broot/

@tshepang For shells, my daily driver has been #Bash for decades. I try to always be using as modern a version as possible. I still use Bash especially for shell **scripts**. My #Dotfiles are set up to use either (https://github.com/wolf/dotfiles. In particular, see the `shells` directory). Git Bash for Windows, of course, forces the issue for me at work. During my Bash time ) and now) I occasionally try other things. For instance #Xonsh (which just wasn’t for me). Shells can do amazing things but understanding shell scripts is a rarer skill than understanding more popular languages. That’s one reason why, if a shell script gets too complicated, I’ll just write it in Python.

My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".

As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.

Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.

It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".

P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!

My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".

As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.

Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.

It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".

P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!

My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".

As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.

Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.

It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".

P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!

My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".

As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.

Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.

It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".

P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!

My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".

As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.

Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.

It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".

P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!

I think today I need to poke at #Xonsh's container generation so I can unblock #PursuedPyBear's release process.

Yak shaving plus bit rot hurts.

#PyConUS

#Xonsh uses #Python string, which is utf-8, so it lacks the ability to deal with mal-structured file names...

#TechTips: If you accidentally created files with non-unicode file names, you can use`rm --interactive *` to remove them without having to refer to their names (which will either trigger non-utf string error like #Xonsh or no-such-file error in #bash and alike).

Wer Arch Linux (oder eine Variante) nutzt, verwendet zum Installieren in der Regel die Pakete der Distribution oder - sofern man sich der Risiken bewusst ist - auch vertrauenswürdige Pakete aus dem AUR Repo.  Python ist in der Regel aus dem Repo vorinstalliert. Und es bietet sich ja eigentlich auch an, Xonsh ebenfalls so zu installieren...

Mit der Bash kenn' ich mich aus. Bin ja auch schon seit 1996 nahezu ausschließlich mit Linux unterwegs... da lernt man über die Jahre die Shell halt kennen ...

Today is a good day. I built installers for #Python 3.14.0a5 for both Windows and macOS. My little fix to #xonsh immediately landed in a new release that was immediately picked up by #homebrew. They're also shipping Python 3.13.2. Upgrading was seamless.

I also upgraded to WezTerm yesterday and it's awesome. Images in the terminal? Why not! Let's make one with Alpha 5!

You can also test the release on your system by downloading it from
https://www.python.org/download/pre-releases/

Do you use xonsh? Do you hate it when midnight commander doesn't exit into the directory you were in?

This post has the fix:

https://blog.nawaz.org/posts/2018/Apr/xonsh-and-midnight-commander/

#mc #midnightcommander #xonsh

@b0rk I second that list. #fishshell is my daily driver, too. History autocomplete is the killer feature for me and why I stuck to it. Occasionally I'm also experimenting with #nushell and #xonsh

At the beginning I used #fish as a #Linux #shell for many years. Until I had problems with it and switched to #zsh. It's too cumbersome for me now, so I went back to "fish". At the same time I'm testing #xonsh, but I've also had a quick look at #dash, #ksh and #oil.

What do you use and would recommend to me? What are their advantages? Whether it's #POSIX compatible or not doesn't matter, because I don't program or use scripts. Colors are important to me for good readability. Thanks for your input 👍 #Arch #ArchLinux

Zu Anfang habe ich viele Jahre #fish als #Linux #shell genutzt. Bis ich Probleme damit hatte und zu #zsh wechselte. Die ist mir inzwischen zu schwerfällig, deshalb kehrte ich zu "fish" zurück. Parallel teste ich #xonsh, habe mir aber auch schon kurz #dash, #ksh und #oil angesehen.

Was nutzt und würdet ihr mir empfehlen? Was sind deren Vorzüge? Ob #POSIX kompatibel oder nicht, ist egal, da ich weder programmiere noch Scripts nutze. Farben sind mir für eine gute Lesbarkeit wichtig. Danke für euren Input 👍 #Arch #ArchLinux

Learn how to create lightweight Raspberry Pi scripts with Xonsh, a Python shell that lets you write scripts in Python with Bash commands mixed in https://www.makerspace-online.com/snake-shell/
#Python #Shell #Bash #Xonsh #RaspberryPi #OpenSource #makers #script

In this blog post and video, I unveil a virtual environment management script for PowerShell, similar to VOX (originally designed for Xonsh shell). If you’re a PowerShell enthusiast, this one’s for you!
🔗 Read the blog post: https://tessarinseve.pythonanywhere.com/nws/2024-05-22.wiki.html

📄 As a practical use case, I’ve also crafted a Python script that adds TODO free-text annotations to PDF files.
#PowerShell #Python #Productivity #xonsh

If you're not using #OhMyPosh, you're missing out.
Where ever I go, as long as oh-my-posh is with me, it will feel like home.
I just tried #xonsh (a shell that understands python), and by just setting up oh-my-posh, it felt as if I have been using xonsh for a while.

The real benchmark for #llm progress: Make them real good at #bash scripting.

I never want to write another shell script again.

(Unless it's in #xonsh).

🦆📊 Interested in data and databases? Check out this video on DuckDB! Dive into CSV data, apply SQL filters, and visualize with Seaborn within the Xonsh shell! #DuckDB #DataAnalytics #Xonsh #svgbob
https://youtu.be/nSE22tfnq7Y

🦆📊 Interested in data and databases? Check out this video on DuckDB! Dive into CSV data, apply SQL filters, and visualize with Seaborn within the Xonsh shell! #DuckDB #DataAnalytics #Xonsh #svgbob
https://youtu.be/nSE22tfnq7Y

🦆📊 Interested in data and databases? Check out this video on DuckDB! Dive into CSV data, apply SQL filters, and visualize with Seaborn within the Xonsh shell! #DuckDB #DataAnalytics #Xonsh #svgbob
https://youtu.be/nSE22tfnq7Y

🦆📊 Interested in data and databases? Check out this video on DuckDB! Dive into CSV data, apply SQL filters, and visualize with Seaborn within the Xonsh shell! #DuckDB #DataAnalytics #Xonsh #svgbob
https://youtu.be/nSE22tfnq7Y

🦆📊 Interested in data and databases? Check out this video on DuckDB! Dive into CSV data, apply SQL filters, and visualize with Seaborn within the Xonsh shell! #DuckDB #DataAnalytics #Xonsh #svgbob
https://youtu.be/nSE22tfnq7Y

#xonsh #python #shell #vim
Discover the power of Xonsh, a Python-powered shell language and command prompt that lets you mix Python and shell commands seamlessly. This video demonstrates how easy it is to customize the shell with a RC file and integrate it with vim.
https://youtu.be/rq-Ary8u5CE

Which shell/cli do you use most often?
1. Bash
2. Windows PowerShell
3. Zsh
4. Fish
5. Xonsh
#Xonsh #Bash #WindowsPowerShell #Zsh #Fish #shell #cli

after a day of playing around with all #linux shells:

- #xonsh is awesome but a bit clunky
- #nushell is great, will probably be my runner
- #marcel very similar to nushell but treats everything as a Python objects instead of tables. Will come back to this one. No #nix install yet.
- #fish as good as it gets for classic shells
- #zsh, #bash - no real reason to run it unless you're locked into bash ecosystem
- #oilshell - couldn't get it to work but there's a lot of good work here. Next time.

after a day of playing around with all #linux shells:

- #xonsh is awesome but a bit clunky
- #nushell is great, will probably be my runner
- #marcel very similar to nushell but treats everything as a Python objects instead of tables. Will come back to this one. No #nix install yet.
- #fish as good as it gets for classic shells
- #zsh, #bash - no real reason to run it unless you're locked into bash ecosystem
- #oilshell - couldn't get it to work but there's a lot of good work here. Next time.

after a day of playing around with all #linux shells:

- #xonsh is awesome but a bit clunky
- #nushell is great, will probably be my runner
- #marcel very similar to nushell but treats everything as a Python objects instead of tables. Will come back to this one. No #nix install yet.
- #fish as good as it gets for classic shells
- #zsh, #bash - no real reason to run it unless you're locked into bash ecosystem
- #oilshell - couldn't get it to work but there's a lot of good work here. Next time.

after a day of playing around with all #linux shells:

- #xonsh is awesome but a bit clunky
- #nushell is great, will probably be my runner
- #marcel very similar to nushell but treats everything as a Python objects instead of tables. Will come back to this one. No #nix install yet.
- #fish as good as it gets for classic shells
- #zsh, #bash - no real reason to run it unless you're locked into bash ecosystem
- #oilshell - couldn't get it to work but there's a lot of good work here. Next time.

after a day of playing around with all #linux shells:

- #xonsh is awesome but a bit clunky
- #nushell is great, will probably be my runner
- #marcel very similar to nushell but treats everything as a Python object instead of tables. Will come back to this one.
- #fish as good as it gets for classi c shells
- #zsh, #bash - no real reason to run it unless you're locked into bash ecosystem
- #oilshell - couldn't get it to work but there's a lot of good work here. Next time.

While I've been waiting on packages to compile for ELFS I've been playing with xonsh in between builds.

Xonsh is a python-powered shell. I don't often use python, but have started growing a liking to it with xonsh.

It's got some pretty neat features and expands the capabilities of a traditional shell greatly.

What stood out to me the most is the fact that the PATH environment variable is an array and not a string. This is a quirk I've only ever seen in the rc shell from Plan 9. It's actually a really good quirk too! This feature actually makes it easier to script and manipulate the PATH variable in many ways.

While my demonstration is not particularly impressive I think it's kinda neat how python and shell are intertwined in such a nice way.

#python #shellscripting #shell #elfs #xonsh #linux #linuxengineer

While I've been waiting on packages to compile for ELFS I've been playing with xonsh in between builds.

Xonsh is a python-powered shell. I don't often use python, but have started growing a liking to it with xonsh.

It's got some pretty neat features and expands the capabilities of a traditional shell greatly.

What stood out to me the most is the fact that the PATH environment variable is an array and not a string. This is a quirk I've only ever seen in the rc shell from Plan 9. It's actually a really good quirk too! This feature actually makes it easier to script and manipulate the PATH variable in many ways.

While my demonstration is not particularly impressive I think it's kinda neat how python and shell are intertwined in such a nice way.

#python #shellscripting #shell #elfs #xonsh #linux #linuxengineer

While I've been waiting on packages to compile for ELFS I've been playing with xonsh in between builds.

Xonsh is a python-powered shell. I don't often use python, but have started growing a liking to it with xonsh.

It's got some pretty neat features and expands the capabilities of a traditional shell greatly.

What stood out to me the most is the fact that the PATH environment variable is an array and not a string. This is a quirk I've only ever seen in the rc shell from Plan 9. It's actually a really good quirk too! This feature actually makes it easier to script and manipulate the PATH variable in many ways.

While my demonstration is not particularly impressive I think it's kinda neat how python and shell are intertwined in such a nice way.

#python #shellscripting #shell #elfs #xonsh #linux #linuxengineer

While I've been waiting on packages to compile for ELFS I've been playing with xonsh in between builds.

Xonsh is a python-powered shell. I don't often use python, but have started growing a liking to it with xonsh.

It's got some pretty neat features and expands the capabilities of a traditional shell greatly.

What stood out to me the most is the fact that the PATH environment variable is an array and not a string. This is a quirk I've only ever seen in the rc shell from Plan 9. It's actually a really good quirk too! This feature actually makes it easier to script and manipulate the PATH variable in many ways.

While my demonstration is not particularly impressive I think it's kinda neat how python and shell are intertwined in such a nice way.

#python #shellscripting #shell #elfs #xonsh #linux #linuxengineer

While I've been waiting on packages to compile for ELFS I've been playing with xonsh in between builds.

Xonsh is a python-powered shell. I don't often use python, but have started growing a liking to it with xonsh.

It's got some pretty neat features and expands the capabilities of a traditional shell greatly.

What stood out to me the most is the fact that the PATH environment variable is an array and not a string. This is a quirk I've only ever seen in the rc shell from Plan 9. It's actually a really good quirk too! This feature actually makes it easier to script and manipulate the PATH variable in many ways.

While my demonstration is not particularly impressive I think it's kinda neat how python and shell are intertwined in such a nice way.

#python #shellscripting #shell #elfs #xonsh #linux #linuxengineer

#xonsh is a Unix-esque #shell.

xonsh is a dialect of #Python with added shell-based primitives. xonsh effectively acts as a superset of both Python, as well as #sh. xonsh can freely mix Python and shell syntax, with reasonable limitations. xonsh's REPL is also rich with syntax highlighting, autocompletion, and a featured history API.

Website 🔗️: https://xon.sh/

apt 📦️: xonsh

#free #opensource #foss #fossmendations #programming #sysadmin #bash