From: Norbert Koch <n.koch@delta-ii.de>
Subject: Re: Article display functions
Date: 24 Sep 1998 12:30:18 +0200 [thread overview]
Message-ID: <voogs5vm4l.fsf@apollonius.delta-ii.de> (raw)
Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de> writes:
> I vote for the single don't-do-it-if-article-is-larger-than-this variable.
I second this. Doing it the other way might get things a bit too
messy, doesn't it? Just to think about the house keeping :-)
Sorry Kai, I've hit 'R' instead of 'F', first :-/
/norbert.
--
Dr Norbert Koch, DELTA Industrie Informatik GmbH, Fellbach, Germany
A rattlesnake that doesn't bite teaches you nothing!
next reply other threads:[~1998-09-24 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-24 10:30 Norbert Koch [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-09-23 23:29 Lars Magne Ingebrigtsen
1998-09-24 10:11 ` Kai Grossjohann
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=voogs5vm4l.fsf@apollonius.delta-ii.de \
--to=n.koch@delta-ii.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).