github/doom-modeline
1
0
Fork 0
mirror of https://github.com/correl/doom-modeline.git synced 2024-11-24 03:00:10 +00:00
Code Issues Projects Releases Packages Wiki Activity

[Docs] FAQ: Why doesn't change of branch reflect in modeline.

Browse source 
https://github.com/seagle0128/doom-modeline/issues/84
https://github.com/seagle0128/doom-modeline/issues/76
This commit is contained in:
Vincent Zhang 2019-01-04 01:01:40 +08:00
parent eeff72172b
commit e252c4420d
1 changed files with 14 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
README.md
View file

@ -188,8 +188,21 @@ Strongly recommend to use
(setq find-file-visit-truename t) (setq find-file-visit-truename t)
``` ```
If the file is controlled by vc, refer to `vc-follow-symlinks`. If the file is controlled by vc, refer to the documentation of
`vc-follow-symlinks`.
1. Can I add my mode-line segments myself? How to do that? 1. Can I add my mode-line segments myself? How to do that?
Of course. Just add the segments into `global-mode-string`. Of course. Just add the segments into `global-mode-string`.
1. Why doesn't change of branch reflect in modeline?
Actually it's related to `magit` and `vc-mode`.
- Workaround:
- Revert the buffers manually.
- `(setq auto-revert-check-vc-info t)` brings the performance issue.
- Refer to:
- [The mode-line information isn’t always
up-to-date](https://magit.vc/manual/magit/The-mode_002dline-information-isn_0027t-always-up_002dto_002ddate.html)
- [Maybe provide an alternative to VC's mode-line
information](https://github.com/magit/magit/issues/2687)