From: Andy Eskilsson <flognat@fukt.hk-r.se>
Subject: Re: Automatic generation of split methods
Date: 19 Jun 1996 08:18:41 +0200 [thread overview]
Message-ID: <lv3f3s1flq.fsf@claymore.fukt.hk-r.se> (raw)
In-Reply-To: Mats.Lofdahl@astro.su.se's message of 18 Jun 1996 12:25:25 +0100
/ Mats.Lofdahl@astro.su.se (Mats G. Lofdahl) wrote:
|
| Why not implement splitting for the other backends as well? Then put
| split methods in the score files? And merge splitting and scoring
| interfaces?
It struck me, once in the old ancient ding gnus, I messed around with
some way to split a mailgroup with a regexp, and then switch between
the different 'partitions' in the *Summary buffer*.. Humm can't find
it now with a quick glance through the docs..
/Andy
prev parent reply other threads:[~1996-06-19 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-17 16:26 Benny Amorsen
1996-06-18 4:18 ` Lars Magne Ingebrigtsen
1996-06-18 11:25 ` Mats G. Lofdahl
1996-06-18 11:56 ` Andy Eskilsson
1996-06-18 12:42 ` Per Abrahamsen
1996-06-18 14:52 ` Andy Eskilsson
1996-06-19 6:18 ` Andy Eskilsson [this message]
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=lv3f3s1flq.fsf@claymore.fukt.hk-r.se \
--to=flognat@fukt.hk-r.se \
/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).