Package Details: mu 1.12.5-1

Git Clone URL: https://aur.archlinux.org/mu.git (read-only, click to copy)
Package Base: mu
Description: Maildir indexer/searcher and Emacs client (mu4e)
Upstream URL: http://www.djcbsoftware.nl/code/mu
Licenses: GPL-3.0-or-later
Submitter: xyproto
Maintainer: mroethke
Last Packager: mroethke
Votes: 45
Popularity: 0.34
First Submitted: 2019-03-27 09:21 (UTC)
Last Updated: 2024-05-03 17:46 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

slondr commented on 2021-11-15 00:53 (UTC)

When I try to update to the new version, I get a bunch of errors related to libffi, followed by:

error: found development files for Guile 3.0, but /usr/bin/guile3 has effective version

Is this a known bug?

emacsomancer commented on 2021-10-24 18:27 (UTC) (edited on 2021-10-24 18:27 (UTC) by emacsomancer)

there seemed to be a difference in version for 1.6.8 between the tar.xz and tar.gz sources. In any case, with the update to 1.6.9, the correct version is shown.

dordow commented on 2021-10-24 12:51 (UTC)

Yes, mu -V now shows 1.6.9. I had to restart Emacs because mu4e complained about version mismatch.

mroethke commented on 2021-10-24 12:10 (UTC)

Fixed with 1.6.9

mroethke commented on 2021-10-24 10:35 (UTC)

It seems the tag is on the wrong commit. The one right before bumping the version. So it should probably contain everything it was supposed to, but still reports the old version. I contacted the maintainer. I will fix this myself, if he does not respond soonish.

dordow commented on 2021-10-24 08:47 (UTC)

Yes, confirm, although I have upgraded mu and the PKGBUILD file says 1.6.8.

emacsomancer commented on 2021-10-23 18:23 (UTC)

mu -V still seems to report 1.6.7?

dordow commented on 2021-08-08 11:55 (UTC) (edited on 2021-08-08 11:56 (UTC) by dordow)

Many thanks for these hints. The 'mu4e-view-*' are the culprits indeed. They are still used in BBDB customization, see mu4e manual. I have removed them and it seems that BBDB integration still works, at least auto-completion.

milouse commented on 2021-08-01 15:56 (UTC) (edited on 2021-08-01 15:57 (UTC) by milouse)

@dordow yes with this new release, mu4e now uses gnus as default viewer for the messages. You can either use the following variable to stick with the old view system (setq mu4e-view-use-old t) (however, as it is now deprecated, maybe one day it will be removed?), or try to adopt the new view (like I did). As you, I prefer the text view by default and achieve something good with the following settings:

(setq gnus-inhibit-images t ;; don't include pictures in messages
      ;; Use a custom date/time format in the Date mail header
      gnus-article-date-headers 'user-defined
      gnus-article-time-format "%A %d %B %Y à %R"
      ;; Use specific faces for To and Flags headers to look like the old mu4e view
      gnus-header-face-alist '(("From" nil gnus-header-from)
                               ("Subject" nil gnus-header-subject)
                               ("Newsgroups:.*," nil gnus-header-newsgroups)
                               ("To:" nil gnus-header-from)
                               ("Flags:" nil font-lock-builtin-face)
                               ("" gnus-header-name gnus-header-content))
      ;; Improve default order for headers
      gnus-sorted-header-list '("^From:" "^Reply-To:" "^To:" "^Cc:" "^Subject"
                                "^Date:" "^Flags:")
    ;; Never try to load html version of email by default
    mm-text-html-renderer 'w3m-standalone
    mm-discouraged-alternatives '("text/html"))

If you use the new Gnus message view, you should also check in you own config (.emacs file) that you don't keep old and deprecated variables related to mu4e-view. You must look for all variables beginning by mu4e-view and remove them as they won’t work anymore (I think that’s why you had an error message saying error in process filter: No buffer named mu4e-view: you probably have an old setting trying to do something in mu4e-view, but it is no more there.

dordow commented on 2021-07-31 20:01 (UTC)

OK, it does now format the message without error but as a single line so the message is still unreadable. The same with emacs in command line mode. It looks as if all line breaks are removed. Before migrating, the messages were in text mode (which I prefer), now they seem to be in a somewhat more fancy format

« First ‹ Previous 1 2 3 4 5 Next › Last »