Finally it means you need two separate sets of keys to do almost the same thing inside or outside of Emacs. Pretty nasty and pointless!
You can also solve this by going in the other direction by making Emacs your window manager. I moved to EXWM a few years ago and have never looked back, it’s incredible how much better basically all of my workflows have become. It also doesn’t really need any frequent handholding, I seem to touch this config about once per month.
This post reminds me of another nested version of this problem that some EXWM users have: Applications (especially browsers) with tabs, which they’d prefer to move into Emacs as well.
I tried one-tab-per-window inside exwm with firefox but it was significantly slower to create a new window than creating a new tab, so I ended up having to ditch it. Hadn’t tried it with one of the webkit ones; maybe once I get forced to stop using exwm by wayland I’ll give it a shot. Is it easy to configure surf with emacs keys? When I looked at it years ago it didn’t look straightforward.
I don’t use surf, but there are similarpatches for dwm. I added emacs keys to tabbed (haven’t published the patch yet), and it was pretty easy there too. I’m guessing surf would be similar to these other suckless projects.
Glad to see this. I have a similar set of hacks, so may try switching to this package.
I also have a bunch of hacks to try to open a new frame every time a new buffer opens, since switching buffers in one frame (and usually leaving the old buffer open!) drives me crazy.
A more flexible approach to this is shackle. I have been meaning to try this out for quite some time (as I share the opinion in the blog post), but I haven’t come around to it yet.
You can also solve this by going in the other direction by making Emacs your window manager. I moved to EXWM a few years ago and have never looked back, it’s incredible how much better basically all of my workflows have become. It also doesn’t really need any frequent handholding, I seem to touch this config about once per month.
This post reminds me of another nested version of this problem that some EXWM users have: Applications (especially browsers) with tabs, which they’d prefer to move into Emacs as well.
And even if you don’t use exam - this problem becomes less significant the more you live inside Emacs. So that’s one motivation to do things in Emacs.
surf is a handy little browser for this sort of thing
I tried one-tab-per-window inside exwm with firefox but it was significantly slower to create a new window than creating a new tab, so I ended up having to ditch it. Hadn’t tried it with one of the webkit ones; maybe once I get forced to stop using exwm by wayland I’ll give it a shot. Is it easy to configure surf with emacs keys? When I looked at it years ago it didn’t look straightforward.
I don’t use surf, but there are similar patches for dwm. I added emacs keys to tabbed (haven’t published the patch yet), and it was pretty easy there too. I’m guessing surf would be similar to these other suckless projects.
Glad to see this. I have a similar set of hacks, so may try switching to this package.
I also have a bunch of hacks to try to open a new frame every time a new buffer opens, since switching buffers in one frame (and usually leaving the old buffer open!) drives me crazy.
A more flexible approach to this is shackle. I have been meaning to try this out for quite some time (as I share the opinion in the blog post), but I haven’t come around to it yet.
A previous effort in this direction was OneOnOneEmacs.