I didn't know about kkp package. Need to try it out - especially on MacOS there are still performance issues (that I work on) so having workable terminal with all the keybinds available would be helpful.
By the way, recently Kitty introduced variable sized text, which probably could be integrated in Emacs, too, to have my favorite feature - font resize per frame :)
I can highly recommend KKP. It works very well in Kitty, and it even lets you map super keybindings, swap modifier keys, etc. I also used it on MacOS to get a low-latency frame on big hiDPI screens where the Cocoa GUI becomes quite unusable.
It also works fine in many other terminals like iTerm2 and Ghostty. Last I tried, they don’t report Super though.
This article is mostly about using emacs -nw which will depend on a bunch of things like how terminal input is handled! With regular Emacs, as a GUI, I typically split as well but I prefer vterm over M-x shell.
I have used it between 1995 and somewhere around 2006, always as graphical application, and for a while mostly XEmacs, which had much better graphical features.
Using it on the terminal only over telnet when a remote X session wasn't possible.
My main interaction is from the GUI where I just leave it open for days at a time. So this article stems from some of the frustrations I had using it in the terminal and not finding the same behavior I was used to.
I didn't know about kkp package. Need to try it out - especially on MacOS there are still performance issues (that I work on) so having workable terminal with all the keybinds available would be helpful.
By the way, recently Kitty introduced variable sized text, which probably could be integrated in Emacs, too, to have my favorite feature - font resize per frame :)
I can highly recommend KKP. It works very well in Kitty, and it even lets you map super keybindings, swap modifier keys, etc. I also used it on MacOS to get a low-latency frame on big hiDPI screens where the Cocoa GUI becomes quite unusable.
It also works fine in many other terminals like iTerm2 and Ghostty. Last I tried, they don’t report Super though.
Split the screen: c-x 2, 2nd window in shell-mode with M-x shell, everything is fine. Am i missing something here?
This article is mostly about using emacs -nw which will depend on a bunch of things like how terminal input is handled! With regular Emacs, as a GUI, I typically split as well but I prefer vterm over M-x shell.
It genuinely never ocurred to me that you use emacs somewhere outside the terminal.
It's quite nice for the following reasons:
- Image previews (for file management with dired/dirvish)
- PDF viewing
- In-buffer images (e.g. profile pictures in git log with Magit)
- Browsing simple HTML pages (e.g. API docs)
There's probably more I've yet to discover.
M-X calc and/or imaxima with embedded Gnuplot generated plots.
There are dozens of us running it outside of a terminal. Dozens!
I have used it between 1995 and somewhere around 2006, always as graphical application, and for a while mostly XEmacs, which had much better graphical features.
Using it on the terminal only over telnet when a remote X session wasn't possible.
My main interaction is from the GUI where I just leave it open for days at a time. So this article stems from some of the frustrations I had using it in the terminal and not finding the same behavior I was used to.
Using it in GUI mode, you’ll end up using the terminal inside Emacs!
And there's EXWM if you want to keep going. I guess people have also tried to set emacs as their init process.
Yup: https://github.com/a-schaefers/systemE
Well there's the GUI version. vim also have it.