From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: [Article display mess up] SOLVED! (-> FAQ ???)
Date: 23 Jan 1997 10:24:23 +0100 [thread overview]
Message-ID: <m2g1zs4ud4.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Jan Vroonhof's message of 22 Jan 1997 14:51:31 +0100
Jan Vroonhof <vroonhof@math.ethz.ch> 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?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1997-01-23 9:24 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 [this message]
1997-01-23 11:42 ` Jan Vroonhof
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=m2g1zs4ud4.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).