Arch Linux User Repository

Maybe it has something to do with this item from the release notes?

*** mu4e

    - Use the gnus-based message viewer as the default; the new viewer has quite
      a few extra features compared to the old, mu4e-specific one, such as
      faster crypto, support for S/MIME, syntax-highlighting, calendar
      invitations and more.

      The new view is superior in most ways, but if you still depend on
      something from the old one, you can use:
      #+begin_example
      ;; set *before* loading mu4e; and restart emacs if you want to change it
      ;; users of use-packag~ should can use the :init section for this.
      (setq mu4e-view-use-old t)
      #+end_example

      (The older variable ~mu4e-view-use-gnus~ with the opposite meaning is
      obsolete now, and no longer in use).

Yes, I did. I have downgraded mu, then mu4e worked as usual. I upgraded again, now it is 1.6.1, run mu init and mu index. but error remains. Any special settings in .emacs I need to consider?

@dordow: did you update mu init ?

call mu init with your preferred parameters (maildir, email addresses), and then call mu index

I use mu with mu4e, and I have trouble with the latest upgrade to 1.6.0. In the message view the message is not formatted, it looks as if it is in raw format, and there is an error message: "error in process filter: No buffer named mu4e-view".

I run mu init, but this did not help. Do I need to adjust any settings in the .emacs file?

I have noticed that a new version of mu is available, 1.6.1.

Thanks in advance

Nothing to be sorry for :) Thanks for trying to improve this package!

Oh, ok, I didn't know that. Sorry for the noise!

No, it wont fail. make depends on guile and make is required to be installed on any system that wants to build packages. It probably makes sense to add guile to makedepends though.

Warning, as you made it, the first time someone try to build mu and has never dealt with guile, it will fail as guile is only an optdepends. You must move it to real depends array to ensure it's there.

I think you are right. Thanks for pointing that out.

Hi,

I'm wondering if this package really need the double dependence on guile and guile2.0.

As you build it with the --enable-guile switch, I think only guile is required and guile2.0 should be removed. I've just test in on my side with only guile as a dependency: it built fine and doesn't break at runtime… I found no reference to specifically guile2.0 on the upstream project, they always refer to guile 2.x.