Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike McEwan <mike@lotusland.demon.co.uk>
Subject: How's the buglist going now?
Date: 06 Mar 1998 01:32:41 +0000	[thread overview]
Message-ID: <m3soowy56u.fsf@lotusland.demon.co.uk> (raw)

Hi,
  It's a little late in the evening, but I've decided to post anyway.

  I was wondering if Lars, or anyone in the know could tell me when
expiry under the `agent' is likely to be sorted out - only I've just
done another `gnus-agent-expire' which would appear to have messed
with my .overviews - another expire sorted it out.

  Whilst I'm here, I note that in the `Newest Features' node of the
gnus manual for quassia, there is the intention to `push active file
and NOV file parsing down into C code'. This would really speed things 
up no? I've just started with C and was curious as to how this might
be easily accomplished - would the active file and/or NOV files be
passed to a C program in a buffer via the elisp `call-process'
function and the parsed output returned in another (or perhaps the
same) buffer? If I can work out what kind of parsing takes place here, 
I'd like to give it a go - some kind of high level spec would help (my 
elisp is novice too).

  I appreciate the above may be already in hand, but 'Newest Features'
does seem a rather long list and I was just interested in something
tangible I could cut my teeth on (or smash my face, perhaps).

-- 
Regards, Mike.
  

     


             reply	other threads:[~1998-03-06  1:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-06  1:32 Mike McEwan [this message]
1998-03-06  2:05 ` Hrvoje Niksic
1998-03-07 13:24 ` 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=m3soowy56u.fsf@lotusland.demon.co.uk \
    --to=mike@lotusland.demon.co.uk \
    /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).