From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: registry and the gnus-summary-line-format
Date: Tue, 21 Feb 2017 21:49:25 +0000 [thread overview]
Message-ID: <871surqknu.fsf@mat.ucm.es> (raw)
In-Reply-To: <87o9xvs8ce.fsf@ericabrahamsen.net>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
> Uwe Brauer <oub@mat.ucm.es> writes:
> The `list' was supposed to go outside the plist-get. Here's a version that
> uses `char-to-string', which I think is more explicit:
> (defun gnus-registry-article-marks-to-chars (headers)
> "Show the marks for an article by the :char property."
> (let* ((id (mail-header-message-id headers))
> (marks (when id (gnus-registry-get-id-key id 'mark))))
> (mapconcat (lambda (mark)
> (char-to-string
> (plist-get
> (cdr-safe
> (assoc mark gnus-registry-marks))
> :char)))
> marks "")))
It seems that my message was not sent (in case of a possible double
posting, sorry)
Great, thanks!! Very much! Now it works as expected. I suggest to push
that change to master!
Now I am getting curious and want to try gnorb with the registry but as
I said is there is a bug of the sort
[-- Attachment #2: gnorb-bug.txt --]
[-- Type: text/plain, Size: 610 bytes --]
Error updating the summary line [2 times]
format: Symbol’s function definition is void: gnus-user-format-function-gInvalid face reference: font-lock-comment-warn-face
Invalid face reference: font-lock-comment-warn-face [19 times]
nnimap read 0k from imap.gmail.com
format: Symbol’s function definition is void: gnus-user-format-function-gInvalid face reference: font-lock-comment-warn-face
Invalid face reference: font-lock-comment-warn-face [3 times]
Updating buffer list...
Formats have changed, recompiling...done
Updating buffer list...done
Commands: m, u, t, RET, g, k, S, D, Q; q to quit; h for help
prev parent reply other threads:[~2017-02-21 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 21:45 Uwe Brauer
2017-02-20 1:06 ` Eric Abrahamsen
2017-02-21 12:01 ` Uwe Brauer
2017-02-21 16:28 ` Eric Abrahamsen
2017-02-21 18:18 ` Uwe Brauer
2017-02-21 18:23 ` Uwe Brauer
2017-02-21 18:32 ` Eric Abrahamsen
2017-02-21 20:08 ` Uwe Brauer
2017-02-22 0:34 ` Eric Abrahamsen
2017-02-22 9:25 ` Uwe Brauer
2017-02-22 16:59 ` Eric Abrahamsen
2017-02-22 17:38 ` Uwe Brauer
2017-02-21 21:49 ` Uwe Brauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871surqknu.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).