alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mu4e: don't change context when already running

Browse Source 
This is for the case where mu4e-compose trigger mu4e~start, as found by
thierryvolpiatto.
This commit is contained in:
djcb
2016-01-03 15:53:58 +02:00
parent 5e13d31450
commit 785d888b42
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
mu4e/mu4e-utils.el
View File

@ -777,14 +777,13 @@ first.
If mu4e is already running, execute function FUNC (if non-nil). If mu4e is already running, execute function FUNC (if non-nil).
Otherwise, check various requirements, then start mu4e. When Otherwise, check various requirements, then start mu4e. When
successful, call FUNC (if non-nil) afterwards." successful, call FUNC (if non-nil) afterwards."
;; maybe switch the context
(mu4e~context-autoswitch nil mu4e-context-policy)
;; if we're already running, simply go to the main view ;; if we're already running, simply go to the main view
(if (mu4e-running-p) ;; already running? (if (mu4e-running-p) ;; already running?
(when func ;; yes! run func if defined (when func (funcall func)) ;; yes! run func if defined
(funcall func))
(progn (progn
;; no! do some checks, set up pong handler and ping the server ;; no! try to set a context, do some checks, set up pong handler and ping
;; the server maybe switch the context
(mu4e~context-autoswitch nil mu4e-context-policy)
(lexical-let ((func func)) (lexical-let ((func func))
(mu4e~check-requirements) (mu4e~check-requirements)
;; set up the 'pong' handler func ;; set up the 'pong' handler func