Gnus development mailing list
 help / color / mirror / Atom feed
From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: [Article display mess up] SOLVED! (-> FAQ ???)
Date: 23 Jan 1997 12:42:06 +0100	[thread overview]
Message-ID: <byybdkhb3l.fsf@math.ethz.ch> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 23 Jan 1997 10:24:23 +0100

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> > This annotation has a "begin-glyph" property set to the group
> > icon/name. This wouldn't be a problem, BUT the gnus
> > article-fancification code does not expect this and creates
> > annotations/extents itself each one inheriting the begin-glyph
> > property.
> 
> Is there a way to avoid inheriting this begin-glyph?  Could it be
> marked as "non-inheritable" or something?

The best way would be make sure the picon annoation extent never
overlaps the headers as it should be. You could do that by making sure
one inserts the article headers BEFORE the extent.
The easiest way to do this by creating the picon annotations after the
article texts had bin inserted which is why one should put the picon
stuff in article-display-hook.

JAn


  reply	other threads:[~1997-01-23 11:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-01-17  2:28 [Article display mess up] Danny Siu
1997-01-17 10:24 ` Jan Vroonhof
1997-01-18  1:21 ` Lars Magne Ingebrigtsen
1997-01-20  8:46   ` Wesley.Hardaker
1997-01-20 11:53     ` Jan Vroonhof
1997-01-22 13:51     ` [Article display mess up] SOLVED! (-> FAQ ???) Jan Vroonhof
1997-01-23  9:24       ` Lars Magne Ingebrigtsen
1997-01-23 11:42         ` Jan Vroonhof [this message]
1997-01-24  9:16           ` Lars Magne Ingebrigtsen

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=byybdkhb3l.fsf@math.ethz.ch \
    --to=vroonhof@math.ethz.ch \
    /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).