A short blog post on defining some custom #emacs #eshell wrappers for some common jj commands I use.
https://www.alcarney.me/blog/2026/eshell-integration/
Thanks to @xenodium and the Bending Emacs series for the inspiration!
A short blog post on defining some custom #emacs #eshell wrappers for some common jj commands I use.
https://www.alcarney.me/blog/2026/eshell-integration/
Thanks to @xenodium and the Bending Emacs series for the inspiration!
So … how many people so far today have told you that it was almost certainly a recording of an eshell session, which was then copied into the animations by animators; the process used for other scenes and revealed later by the person who did these effects? Basically the terminal user's equivalent of motion capture.
Got to be more than one. (-:
https://web.archive.org/web/20111007222352/http://jtnimoy.net/workviewer.php?q=178
Or that have pointed out Xorg in the process list? There's probably something to be inferred from those window widgets, too.
Alas, I strongly suspect that the person who did this died in the first year of COVID.
How cute! A disposable #Emacs #eshell for quick tasks:
```
(defun my/eshell-toggle ()
(interactive)
(let ((eshell-buffer-name "*eshell-toggle*"))
(if (get-buffer-window eshell-buffer-name)
(delete-windows-on eshell-buffer-name t)
(progn
(select-window (split-root-window-below))
(eshell)))))
```
Quick and dirty, there are better alternatives out there (e.g. https://github.com/karthink/popper ?) - but it works!
Today i tried some #git operation from #emacs #eshell and there is no color output so i explored whether i can display color output. Turns out we can using
```git config --global color.ui always```
which worked like charm. I use #windows for work so #magit is out of reach for me due to #git slowness.
Hello fellow #emacs users! I'm having problem with #eshell #python and #poe on macos
Running a task involving "clear" command throws an error. Trying to troubleshoot it, I run a command with "which clear" and the response is "/usr/bin//clear".
This causes the execution error.
This is running as expected on any other terminal emulator.
Any clue? Maybe @andros has had any similar experience?
Thanks!