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
Hm, that's strange. The stacktrace shows that the error happens when jabber-otr--ensure-started calls get-buffer-process with no arguments, but in the current version, there is no such call... Do you have the latest version? Do you have any local changes?
oh sorry that was the error message after i tried to 'fix' it .. but the actual error is in (process-live-p jabber-otr-process) that throws an error saying that there is no process attached with the buffer ...will paste the actual message once i get back to my desk
(Debugger entered--Lisp error: (wrong-number-of-arguments get-buffer-process 0) (get-buffer-process) (or (get-buffer-process) (process-live-p jabber-otr-process)) (if (or (get-buffer-process) (process-live-p jabber-otr-process)) nil (jabber-otr-start)) jabber-otr--ensure-started() jabber-otr-encrypt() call-interactively(jabber-otr-encrypt) (progn (call-interactively sym-com)) (if helm-M-x-always-save-history (progn (call-interactively sym-com))) (let\* ((history (progn (let\* ((--cl-var-- extended-command-history) (i nil) (--cl-var-- nil)) (while (consp --cl-var--) (setq i (car --cl-var--)) (if (comman$ helm-M-x() call-interactively(helm-M-x nil nil)
The text was updated successfully, but these errors were encountered: