fancy-chars / strange Symbol for new Mails

90 views
Skip to first unread message

Thorsten Grothe

unread,
May 26, 2016, 5:38:58 PM5/26/16
to mu-discuss
Hello mu-users,

I configured mu4e to use fancy chars, like so

(setq mu4e-use-fancy-chars t)
         
it works fine for all, only new mails got a strange character, see here. I tried DejaVu Sans Mono with the same result, does anybody know what I'm doing wrong?

Regards
Thorsten


Boyan Penkov

unread,
May 26, 2016, 9:23:15 PM5/26/16
to mu-di...@googlegroups.com
What font are you using initially?

I see the same result (with DejaVu Sans Mono) and had always assumed it was due to the incomplete character set.

Can someone more knowledgeable shed some light on this?

Cheers!
--
Boyan Penkov
www.boyanpenkov.com

--
You received this message because you are subscribed to the Google Groups "mu-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mu-discuss+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Dirk-Jan C. Binnema

unread,
May 27, 2016, 2:14:52 AM5/27/16
to mu-di...@googlegroups.com
What 'strange character' do you mean? The ones in the screenshot look
like the expected ones. If you don't like those, you can customize them
using the various mu4e-headers-*-mark variables.

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

Thorsten Grothe

unread,
May 27, 2016, 5:58:14 AM5/27/16
to mu-discuss

What 'strange character' do you mean? The ones in the screenshot look
like the expected ones. If you don't like those, you can customize them
using the various mu4e-headers-*-mark variables.


I mean the empty square in the FLGS column :-)

Regards
Thorsten

Dirk-Jan C. Binnema

unread,
May 31, 2016, 1:47:14 AM5/31/16
to mu-di...@googlegroups.com
That's in fact the expected character... and as mentioned, you can
change it you don't like it.

Thorsten Grothe

unread,
Jun 1, 2016, 3:05:12 AM6/1/16
to mu-di...@googlegroups.com

> That's in fact the expected character... and as mentioned, you can
> change it you don't like it.

sorry for my late responsive I was busy with my job! Thanks for the
hint. Ok I tried to change the symbol with:

(setq mu4e-headers-new-mark '("N" . "✱"))

this changes the star to ✱ but how can I change the second symbol, the
empty square?


Regards

Thorsten Grothe

Nicolas Richard

unread,
Jun 1, 2016, 4:48:51 AM6/1/16
to mu-di...@googlegroups.com
Hi Thorsten,

Thorsten Grothe <bucketh...@gmail.com> writes:
> (setq mu4e-headers-new-mark '("N" . "✱"))
>
> this changes the star to ✱ but how can I change the second symbol, the
> empty square?

I guess it's mu4e-headers-unread-mark. In mu4e-headers.el, the following
are defined:

;; marks for headers of the form; each is a cons-cell (basic . fancy)
;; each of which is basic ascii char and something fancy, respectively
(defvar mu4e-headers-draft-mark '("D" . "⚒") "Draft.")
(defvar mu4e-headers-flagged-mark '("F" . "✚") "Flagged.")
(defvar mu4e-headers-new-mark '("N" . "✱") "New.")
(defvar mu4e-headers-passed-mark '("P" . "❯") "Passed (fwd).")
(defvar mu4e-headers-replied-mark '("R" . "❮") "Replied.")
(defvar mu4e-headers-seen-mark '("S" . "✔") "Seen.")
(defvar mu4e-headers-trashed-mark '("T" . "⏚") "Trashed.")
(defvar mu4e-headers-attach-mark '("a" . "⚓") "W/ attachments.")
(defvar mu4e-headers-encrypted-mark '("x" . "⚴") "Encrypted.")
(defvar mu4e-headers-signed-mark '("s" . "☡") "Signed.")
(defvar mu4e-headers-unread-mark '("u" . "⎕") "Unread.")

;; thread prefix marks
(defvar mu4e-headers-has-child-prefix '("+" . "◼ ") "Parent.")
(defvar mu4e-headers-empty-parent-prefix '("-" . "◽ ") "Orphan.")
(defvar mu4e-headers-first-child-prefix '("\\" . "┗▶") "First child.")
(defvar mu4e-headers-duplicate-prefix '("=" . "≡ ") "Duplicate.")
(defvar mu4e-headers-default-prefix '("|" . "│ ") "Default.")

--
Nicolas.

Thorsten Grothe

unread,
Jun 1, 2016, 5:57:47 AM6/1/16
to mu-di...@googlegroups.com
Nicolas,

* Nicolas Richard: 01.06.2016 (10:48):

> I guess it's mu4e-headers-unread-mark. In mu4e-headers.el, the following
> are defined:

yes indeed !!! Thank you very much, now it works
fine!


Regards

Thorsten Grothe

Reply all
Reply to author
Forward
0 new messages