From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: message-fetch-field returns strange results
Date: Fri, 02 Apr 2004 15:43:44 +0200 [thread overview]
Message-ID: <v9vfkiwl4f.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <86brmc3ew7.fsf@doze.rz-berlin.mpg.de>
On Wed, Mar 31 2004, Jochen Küpper wrote:
> On Wed, 31 Mar 2004 14:46:27 +0200 Reiner Steib wrote:
>
> Reiner> Jesper's Loom-style picon patch. I got the behavior you
> Reiner> described too:
[...]
> If I startup Emacs/Gnus with a plain Gnus from cvs HEAD everything
> works alright (incl. using picons and bbdb). If I then evaluate the
> modified 'gnus-picon-transform-address (and gnus-picon-style) the
> problem shows up.
I found a workaround:
New optional argument to `gnus-picon-insert-glyph':
--8<---------------cut here---------------start------------->8---
(defun gnus-picon-insert-glyph (glyph category &optional nostring)
"Insert GLYPH into the buffer.
GLYPH can be either a glyph or a string."
(if (stringp glyph)
(insert glyph)
(gnus-add-wash-type category)
(gnus-add-image category (car glyph))
(gnus-put-image (car glyph) (unless nostring (cdr glyph)) category)))
--8<---------------cut here---------------end--------------->8---
Use this argument in the "(right ...)" part of
`gnus-picon-transform-address':
+ (gnus-picon-insert-glyph image category)
- (gnus-picon-insert-glyph image category 'nostring)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-04-02 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 21:33 Jochen Küpper
2004-03-29 20:11 ` Jesper Harder
[not found] ` <m3isgnpg6f.fsf-ZcDBdOENzEjP0Z7Jsv878P8+0UxHXcjY@public.gmane.org>
2004-03-30 20:46 ` Jochen Küpper
2004-03-31 12:46 ` Reiner Steib
[not found] ` <v9vfklnpzw.fsf-WZbs9ZYJ0ya4nSHvGpykACzlmkwuQ7VwhC4ANOJQIlc@public.gmane.org>
2004-03-31 21:06 ` Jochen Küpper
2004-04-02 13:43 ` Reiner Steib [this message]
2004-04-06 20:02 ` Xavier Maillard
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=v9vfkiwl4f.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).