Hello,
Matt Price writes:
> so, I think there is an infinite loop generated between yas--auto-fill and
> orgalist--auto-fill:
Yasnippet and Orgalist are somewhat incompatible because Yasnippet is
not playing nice with other minor modes. Instead of advising functions,
it stores them and installs
I'm using orglist and mu4e but not yas-auto-fill. I don't see this
issue.
Tim
Matt Price writes:
> so, I think there is an infinite loop generated between yas--auto-fill and
> orgalist--auto-fill:
>
> --
> Debugger entered--Lisp error: (error "Lisp nesting exceeds
> ‘max-lisp-eval
so, I think there is an infinite loop generated between yas--auto-fill and
orgalist--auto-fill:
--
Debugger entered--Lisp error: (error "Lisp nesting exceeds
‘max-lisp-eval-depth’")
current-left-margin()
move-to-left-margin()
forward-paragraph()
yas--auto-fill()
orgalist--aut
Hi Matt,
> and also are other people seeing the same issue?
Yes, I have also seen this using orgalist + mu4e-compose-mode.
Josiah
On Wednesday, 5 Sep 2018 at 08:40, Matt Price wrote:
> I've just started enabling orgalist in message-mode, and it's awesome.
> However, I'm getting very frequent variable binding depth errors, possibly
[...]
> maybe some of theseshould be turned off! my init files are a bit of a mess
> aright n
I've just started enabling orgalist in message-mode, and it's awesome.
However, I'm getting very frequent variable binding depth errors, possibly
because of conflicts with other packages. When orgalist is turned off, all
the errors go away. When it's turned on, my *Messages* buffer starts to
look l
