phantom draft messages crashing mu4e-compose-new

[Peter Salazar]

Hey everyone,

So having resolved the error I was getting with my (setq mu4e-compose-complete-only-personal t) setup, I got mu4e up and running. Everything seemed to be working perfectly. But now I get this strange error message (pasted below) every time I do mu4e-compose-new. Looking at the error message, I went into bash and tracked down and rm'd all the files mentioned, e.g. .#20160314-2008c5-infinity:2,DS@ -> j...@Infinity.local.48252. 

But then after I restart Emacs + mu4e and do mu4e-compose-new, the error happens again and those files are there in my directory again. 

Anyone know what's going on? Thanks if anyone can help!

Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)

>(nil 1048576)

  (if (> (nth 7 (file-attributes (buffer-file-name))) (* 1024 1024 dotspacemacs-large-file-size)) (progn (if (y-or-n-p "This is a large file, open literally to avoid performance issues?") (progn (setq buffer-read-only t) (buffer-disable-undo) (fundamental-mode)))))

  spacemacs/check-large-file()

  run-hooks(find-file-hook)

  after-find-file(t t)

  find-file-noselect-1(#<buffer 20160314-e5fbba-infinity:2,DS> "~/Dropbox/mail/gmail/drafts/cur/20160314-e5fbba-infinity:2,DS" nil nil "~/Dropbox/mail/gmail/drafts/cur/20160314-e5fbba-infinity:2,DS" nil)

  find-file-noselect("/Users/jay/Dropbox/mail/gmail///drafts/cur/20160314-e5fbba-infinity:2,DS" nil nil nil)

  find-file("/Users/jay/Dropbox/mail/gmail///drafts/cur/20160314-e5fbba-infinity:2,DS")

  mu4e-draft-open(new nil)

  byte-code("\306\301!\210 \307\301\310\311#\210\312\313!\210\314\315\316\217\210\317 \210\212db\210\n\314\211\2039\f@ \320\321 \322\"\321 \323\"\"\210\fA\211\204$+\324!\210\325\314!\210

\326\235\203N\327 \210\202Q\330 \210\306\301!\210\307\301\310\311#\210\331 \210\332 \207" [original-msg mu4e-compose-parent-message includes att --dolist-tail-- compose-type make-local-variable put permanent-local t run-hooks mu4e-compose-pre-hook nil (mu4e-draft-open compose-type original-msg) ((quit (byte-code "\300 \210\301\302!\210\303\304\305\"\207" [kill-buffer message "[mu4e] Operation aborted" throw --cl-block-mu4e~compose-handler-- nil] 3))) mu4e~draft-insert-mail-header-separator mml-attach-file plist-get :file-name :mime-type mu4e~compose-set-friendly-buffer-name set-buffer-modified-p (new forward) message-goto-to message-goto-body mu4e~compose-hide-headers mu4e-compose-mode] 6)

  mu4e~compose-handler(new)

  mu4e-compose(new)

  mu4e-compose-new()

  call-interactively(mu4e-compose-new record nil)

  command-execute(mu4e-compose-new record)

  helm-M-x(nil "mu4e-compose-new")

  call-interactively(helm-M-x nil nil)

  command-execute(helm-M-x)

[Dirk-Jan C. Binnema]

Hi Peter,

On Monday Mar 14 2016, Peter Salazar wrote:

> Hey everyone,
>
> So having resolved the error I was getting with my (setq
> mu4e-compose-complete-only-personal t) setup, I got mu4e up and running.
> Everything seemed to be working perfectly. But now I get this strange error
> message (pasted below) every time I do mu4e-compose-new. Looking at the
> error message, I went into bash and tracked down and rm'd all the files

> mentioned, e.g. *.#20160314-2008c5-infinity:2,DS*@ ->

> j...@Infinity.local.48252.
>
> But then after I restart Emacs + mu4e and do mu4e-compose-new, the error
> happens again and those files are there in my directory again.
>
> Anyone know what's going on? Thanks if anyone can help!
>

Please always mention the versions of emacs, mu4e you are using, when
reporting issues.

> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>
>>(nil 1048576)
> (if (> (nth 7 (file-attributes (buffer-file-name))) (* 1024 1024
> dotspacemacs-large-file-size)) (progn (if (y-or-n-p "This is a large file,
> open literally to avoid performance issues?") (progn (setq buffer-read-only
> t) (buffer-disable-undo) (fundamental-mode)))))
> spacemacs/check-large-file()
> run-hooks(find-file-hook)
> after-find-file(t t)
> find-file-noselect-1(#<buffer 20160314-e5fbba-infinity:2,DS>
> "~/Dropbox/mail/gmail/drafts/cur/20160314-e5fbba-infinity:2,DS" nil nil
> "~/Dropbox/mail/gmail/drafts/cur/20160314-e5fbba-infinity:2,DS" nil)

It seems the error points to some hook set by spacemacs, which checks
for file-size and warns if it's too big.

The hook seems to assume the file already exists in the file system,
which it doesn't. For that reason, the file-size check fails.

I'd recommend taking it up with the spacemacs folks.

Kind regards,
Dirk.

--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C

[Jay Dixit]

Hi Dirk,

Sounds good, will do. And got it, will include version information in the future. Thanks for the quick response! 

e:d...@djcbsoftware.nl           w:www.djcbsoftware.nl