Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: registry and the gnus-summary-line-format
Date: Tue, 21 Feb 2017 16:34:48 -0800	[thread overview]
Message-ID: <87poibf4gn.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87fuj7z4qb.fsf@mat.ucm.es>

Uwe Brauer <oub@mat.ucm.es> writes:

>     > 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 "")))
>
>
>
> Great!!!! Thanks a lot now it works. You should push that to the git
> repo (maybe other functions in gnus-registry are buggy as well?)

Good! There's no longer a separate git repo for Gnus -- it is developed
within the Emacs repository. Unfortunately this means that you won't get
the fix until it's committed to Emacs and then comes back down whatever
pipeline you use to install Emacs.

It also means I'm a wee bit more hesitant about committing directly -- I
have access, but would prefer to open a bug report and get more eyes.
I'll do that in a bit.

> BTW gnus-registry-article-marks-to-names works.
>
> Now I got really curious and would like to try gnorb with the registry.
> For this the manual says to put
>
> Add ``%ug'' somewhere appropriate in your `gnus-summary-line-format'
>
> However it does not work for me, I obtain an error. I think I sent you
> a report, I am not sure that we should discuss this here, but one the
> other hand gnus seems a good place to me.

I did get your other email, but I suppose this is a fine place to work
it out.

If you've loaded gnorb-gnus I don't see how
`gnus-user-format-function-g' could be undefined. That file contains, at
top-level, this form:


(fset (intern (concat "gnus-user-format-function-"
		      gnorb-gnus-summary-mark-format-letter))
      (lambda (header)
	(gnorb-gnus-insert-format-letter-maybe header)))

Which should do the trick.

The various Gnorb pieces are usable independently, meaning you have to
explicitly run (require 'gnorb-gnus). I'm assuming you've done that...
If it still doesn't work, would you eval the snippet above? It will have
to work then!

Eric




  reply	other threads:[~2017-02-22  0:34 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 [this message]
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

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=87poibf4gn.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).