From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: registry and the gnus-summary-line-format
Date: Wed, 22 Feb 2017 09:25:42 +0000 [thread overview]
Message-ID: <8760k24lwp.fsf@mat.ucm.es> (raw)
In-Reply-To: <87poibf4gn.fsf@ericabrahamsen.net>
> Uwe Brauer <oub@mat.ucm.es> writes:
> 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, would it be difficult to implement colors for different registries,
like red for important etc, just asking...
> 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.
Right, my gnorb init file was not complete. After the correction the
registry error is gone, I still run into difficulties but I report on
this later.
Uwe
next prev parent reply other threads:[~2017-02-22 9:25 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 [this message]
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=8760k24lwp.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).