Frames only mode
There's a fairly rough screencast showing the kind of things you can do with this here.
In combination with
frames-only-mode I recommend:
- Running emacs as server-client.
- Binding a hotkey to open new emacs frames (see below).
- Using helm, ivy or ido instead of the default completion interface.
Bind this shell command to a hotkey to automatically open a useful buffer in a new frame (usually your most recently viewed buffer which isn't currently open):
emacsclient -c -n -e '(switch-to-buffer nil)'
- Add support for eshell completion
- Fix some customize group weirdness
Integrating with command line git
To make this work nicely with git (e.g. to pop up a new frame when we run git commit from the command line) we need to set the editor to run an emacsclient in a new frame. However, unlike the case for running emacsclient instances from the window manager, we don't want it to detach from the console. We can achieve this by adding the following to the
[core] editor = emacsclient -c
If instead we only used
editor = emacsclient it would try to open a new buffer in an existing frame. This often results in the commit message buffer showing up in a different workspace(!), or in the terminal.
Integration with default emacs completion
If you use the default emacs completion (or ido with a popup completion buffer)
frames-only-mode-use-windows-for-completion can be used to control
*Completions* buffer is displayed in a frame or an emacs window.
The default is to use an emacs window, which works well with any window manager.
*Completions* buffer can be disabled entirely by setting
This mode originated in a blog post which has some additional details.