homomorphic-padawan · 2022-12-19 12:31
Blytheway · 2022-12-19 15:38
Great having a blog post for this. I enjoyed your talk!
CartanAnnullator · 2022-12-19 16:48
Because we can!
stuudente · 2022-12-19 17:18
Note that eshell's regex isn't portable.
Are the any workarounds?
centzon400 · 2022-12-19 20:36
One wonders why this does not get as much coverage as nushell and friends.
paretoOptimalDev · 2022-12-19 21:34
Isn't that what the "Improvement: Non-Emacs Regexps" section of the article addresses?
bhrgunatha · 2022-12-20 03:17
pcre2el has been a sanity saver for me ever since I first discovered it. elisp regex hurts my brain.
Downtown_Opinion_768 · 2022-12-20 12:38
[howardism.org](https://howardism.org) refuses to connect
Pay08 · 2022-12-20 13:58
Does your browser reject http?
Downtown_Opinion_768 · 2022-12-20 14:24
Yes, that was it. I'm in now. Thanks!
JDRiverRun · 2022-12-20 19:02
Use `rx`: less brain hurt (actually super convenient).
bhrgunatha · 2022-12-21 02:59
I have used it, but the main reason I stick with pcre2el is the cross compatibility with other tools and I use vterm rather than eshell.
The article give some good use cases for eshell so I might give it a more serious try.
Ephemere · 2022-12-21 18:33
I wish I could get better use of eshell. It seems to have some amazing strengths, and I haven’t even touched many of the interactive lisp expressions listed in the article. However I deal fairly regularly with curses and curses adjacent command line programs, and it seems to utterly fail to render such things. The most basic example being running top outputs something unintelligible.
If anyone knows of a way to allow such things to render properly please let me know, as I’d love to use eshell over term.
sebhoagie · 2022-12-21 23:59
I guess the idea using eshell is to *stay in Emacs* so instead of top you would `M-x proced`.
Pay08 · 2022-12-22 16:44
Take a look at the eshell-visual-commands variable.