You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(use-package olivetti :ensuret)
(use-package git-gutter
:ensuret:config (global-git-gutter-mode +1))
;; I didn't use it, but if you like;; (use-package evil;; :ensure t;; :config (evil-mode))
Actions to solve the issue
If it can't be fixed
I think this is an important problem that worth noting in README.
I'd like to find some hack to re-enable the distractin-free looking automatically after it's lost. (If I can.. but I'm not sure since I'm not yet faimlar with Emacs)
My attampt to find the hack
I could do one of the follows to re-enable the distraction-free looking:
M-: (run-hooks 'write-file-functions) RET
Type ESC (or some key) to show which-key in minibuffer
For which-key, I used the following configuration:
The manipulation of the margins is pretty rudimentary in Emacs, so it's unlikely to ever have multiple modes that set the margins happily coexist. If you're looking for a way to indicate git changes at the side of the window I think a mode that uses the fringe will probably work better.
Edit
Update:
In Emacs27.1 git-gutter is not conflicting with olivetti on my computer! You may not need to take care, either!
In short
Olivetti uses margins and it often conflicts with git-gutter. git-gutter-fringe works well in GUI and for terminal I made a hack (gist).
Summary
It happens if git-gutter is loaded. It may be related to #42.
When changes are saved, current window with buffer in
olivetti-mode
loses distraction-free looking:Steps to reproduce
init.el
.olivetti-mode
RETinit.el for reproduction
Enable
use-package
:And then the packages:
Actions to solve the issue
If it can't be fixed
My attampt to find the hack
I could do one of the follows to re-enable the distraction-free looking:
(run-hooks 'write-file-functions)
RETESC
(or some key) to showwhich-key
in minibufferFor
which-key
, I used the following configuration:Thank you
edit: typo and indentations
The text was updated successfully, but these errors were encountered: