mu4e~headers-buffer

[Larrabee Strow]

I just got latest git HEAD version complied for Mac OS. mu index work, etc.

When I jump to the inbox after starting up mu4e in emacs I get tons of
errors on mu4e~headers-buffer.

I set

(setq debug-on-message "void: mu4e~headers-buffer")

and got the following (which repeats for a long time)

Debugger entered--Lisp error: "error in process filter: Symbol’s value as
variable is void: mu4e~headers-buffer"
recursive-edit()
debug(error "error in process filter: Symbol’s value as variable is void:
mu4e~headers-buffer")
recursive-edit()
debug(error "error in process filter: Symbol’s value as variable is void:
mu4e~headers-buffer")
recursive-edit()


This is the git log entry for what I compiled

commit f8a5daa6663bac3338acfc814c097e290c0a7c38
Author: djcb <***@djcbsoftware.nl>
Date: Sun Sep 2 16:43:06 2018 +0300

[Dirk-Jan C. Binnema]

Post by Larrabee Strow
I just got latest git HEAD version complied for Mac OS. mu index work, etc.
When I jump to the inbox after starting up mu4e in emacs I get tons of
errors on mu4e~headers-buffer.
I set
(setq debug-on-message "void: mu4e~headers-buffer")
and got the following (which repeats for a long time)
Debugger entered--Lisp error: "error in process filter: Symbol’s value as
variable is void: mu4e~headers-buffer"
recursive-edit()
mu4e~headers-buffer")
recursive-edit()
mu4e~headers-buffer")
recursive-edit()
This is the git log entry for what I compiled
commit f8a5daa6663bac3338acfc814c097e290c0a7c38
Date: Sun Sep 2 16:43:06 2018 +0300

When I check the mu4e source:

% grep mu4e~headers-buffer *.el
mu4e-headers.el: (let* ((buf (get-buffer-create mu4e~headers-buffer-name))
mu4e-utils.el: (get-buffer mu4e~headers-buffer-name))
mu4e-vars.el:(defconst mu4e~headers-buffer-name "*mu4e-headers*"

there's indeed no such symbol; there used to be a symbol like that in
old (pre 1.0) versions though, so either you have some old code lying
around (perhaps didn't restart emacs?).

Or, alternatively, you're using some mu4e extension that uses the old
symbol. If so, it's best to ask the extension builders (who really
shouldn't be using 'mu4e~'-prefixed internal symbols, but some do).

Kind regards,
Dirk.

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

[LLS Strow]

Thank, I cloned a completely fresh copy and it worked, although I could not
find mu4e~headers-buffer anywhere in the original directory. Anyway, it is
working.

I was going to document how I got mu to compile on the Mac, but tried it
again on a different Mac and now can't get it to compile, but I'm sure this
has nothing to do with mu, more likely missing libraries etc. I use
"brew" to set things up.

I'll keep trying, but I now have the executable so I am good to go.

Larrabee

Post by Dirk-Jan C. Binnema

Post by Larrabee Strow
I just got latest git HEAD version complied for Mac OS. mu index work,

etc.

Post by Larrabee Strow
When I jump to the inbox after starting up mu4e in emacs I get tons of
errors on mu4e~headers-buffer.
I set
(setq debug-on-message "void: mu4e~headers-buffer")
and got the following (which repeats for a long time)
Debugger entered--Lisp error: "error in process filter: Symbol’s value

as

Post by Larrabee Strow
variable is void: mu4e~headers-buffer"
recursive-edit()
debug(error "error in process filter: Symbol’s value as variable is
mu4e~headers-buffer")
recursive-edit()
debug(error "error in process filter: Symbol’s value as variable is
mu4e~headers-buffer")
recursive-edit()
This is the git log entry for what I compiled
commit f8a5daa6663bac3338acfc814c097e290c0a7c38
Date: Sun Sep 2 16:43:06 2018 +0300

% grep mu4e~headers-buffer *.el
mu4e-headers.el: (let* ((buf (get-buffer-create
mu4e~headers-buffer-name))
mu4e-utils.el: (get-buffer mu4e~headers-buffer-name))
mu4e-vars.el:(defconst mu4e~headers-buffer-name "*mu4e-headers*"
there's indeed no such symbol; there used to be a symbol like that in
old (pre 1.0) versions though, so either you have some old code lying
around (perhaps didn't restart emacs?).
Or, alternatively, you're using some mu4e extension that uses the old
symbol. If so, it's best to ask the extension builders (who really
shouldn't be using 'mu4e~'-prefixed internal symbols, but some do).
Kind regards,
Dirk.
--
Dirk-Jan C. Binnema Helsinki, Finland
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C