From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: MIME composition (was: Storing the group a message has been written to)
Date: 13 Nov 1998 23:08:09 +0100 [thread overview]
Message-ID: <vafaf1vgsae.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "13 Nov 1998 19:47:12 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
>
> > (1) This is truly horrible, one should not depend on such an
> > obfuscated fact. Any suggestions for improving this?
>
> We could document it, and rename the variable to something
> reasonable.
That's a great way to remove a bug and add a feature :-) How about
gnus-command-group, to go with gnus-command-method?
There's another tiny problem: nnfolder-save-mail uses GROUP-ART-LIST
rather than GROUP-ART, which is what all the other nnchoke-save-mail
functions use. But the structure of the parameter suggests that
GROUP-ART-LIST is a more appropriate name...
And a question: I did a bit of tracing, and apparently, GROUP-ART
always contains exactly one cons cell when nnmail-cache-insert is
called. (Well it did in all of the two cases I looked at...) So I
just use the first one in the list.
> > (2) The group name is not unique. Sometimes the group name is
> > `drafts' which comes from the nndraft server, sometimes the group
> > name comes from the normal nnml server. I want to use this for
> > mail splitting. Mail splitting deals with one backend only.
> > Thus, I would need to find out whether the group concerned is from
> > that backend and to ignore it if it doesn't come from the backend
> > where mail splitting is done.
>
> Yes. The mail fetching/splitting this is going to be redone, so
> that instead of each mail backend trying to slurp in as much mail
> as possible, there should be one slurping instance that dispathes
> the mail to the backends where they should go.
>
> Should I do that next, or is MIME composition more important?
Hm. I could add a kludge which finds the right backend most of the
time. Here's a guess on finding the right server:
For each G in gnus-select-method, gnus-secondary-select-methods do:
If (gnus-method-option-p G 'respool) then:
Return G
Fi
Rof
Does this have a non-negligible probability of finding the right
server? If so, does this sound like a workable interim solution
(though solution is surely much too strong a word)?
kai
--
Life is hard and then you die.
next prev parent reply other threads:[~1998-11-13 22:08 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-11 13:02 Storing the group a message has been written to Kai.Grossjohann
1998-11-13 18:47 ` MIME composition (was: Storing the group a message has been written to) Lars Magne Ingebrigtsen
1998-11-13 21:28 ` Wes Hardaker
1998-11-13 22:18 ` Lars Magne Ingebrigtsen
1998-11-13 22:45 ` Kai.Grossjohann
1998-11-13 23:02 ` Lars Magne Ingebrigtsen
1998-11-13 23:27 ` Kai.Grossjohann
1998-11-13 23:49 ` Lars Magne Ingebrigtsen
1998-11-14 9:13 ` Kai.Grossjohann
1998-11-14 17:35 ` Lars Magne Ingebrigtsen
1998-11-14 9:14 ` Kai.Grossjohann
1998-11-14 1:00 ` Wes Hardaker
1998-11-14 1:14 ` Hrvoje Niksic
1998-11-14 2:07 ` Lars Magne Ingebrigtsen
1998-11-14 2:19 ` Hrvoje Niksic
1998-11-14 3:01 ` Lars Magne Ingebrigtsen
1998-11-14 15:34 ` Simon Josefsson
1998-11-14 17:26 ` Lars Magne Ingebrigtsen
1998-11-14 15:50 ` Hrvoje Niksic
1998-11-14 17:24 ` Lars Magne Ingebrigtsen
1998-11-16 8:31 ` Steinar Bang
1998-11-16 8:30 ` Steinar Bang
1998-11-16 14:53 ` Lars Magne Ingebrigtsen
1998-11-15 17:01 ` Wes Hardaker
1998-11-15 19:29 ` Lars Magne Ingebrigtsen
1998-11-16 8:24 ` Steinar Bang
1998-11-16 15:23 ` Wes Hardaker
1998-11-13 22:08 ` Kai.Grossjohann [this message]
1998-11-13 22:50 ` Lars Magne Ingebrigtsen
1998-11-13 22:12 ` Kai.Grossjohann
1998-11-13 22:47 ` Kai.Grossjohann
1998-11-13 22:56 ` Lars Magne Ingebrigtsen
1998-11-13 23:37 ` Kai.Grossjohann
1998-11-13 23:52 ` Lars Magne Ingebrigtsen
1998-11-13 23:36 ` Kai.Grossjohann
1998-11-13 23:51 ` Lars Magne Ingebrigtsen
1998-11-14 1:09 ` Hrvoje Niksic
1998-11-14 2:18 ` Lars Magne Ingebrigtsen
1998-11-14 15:34 ` Simon Josefsson
1998-11-14 17:36 ` Lars Magne Ingebrigtsen
1998-11-15 13:42 ` Kai.Grossjohann
1998-11-15 19:27 ` Lars Magne Ingebrigtsen
1998-11-15 21:25 ` Hrvoje Niksic
1998-11-15 22:20 ` Lars Magne Ingebrigtsen
1998-11-16 8:08 ` Hrvoje Niksic
1998-11-16 14:52 ` Lars Magne Ingebrigtsen
1998-11-15 22:12 ` Simon Josefsson
1998-11-16 5:46 ` Lars Magne Ingebrigtsen
1998-11-15 1:39 ` Kai.Grossjohann
1998-11-14 1:05 ` Hrvoje Niksic
1998-11-14 2:10 ` Lars Magne Ingebrigtsen
1998-11-16 15:11 ` Per Abrahamsen
1998-11-16 19:45 ` Edward J. Sabol
1998-11-17 2:08 ` Matt Armstrong
1998-11-17 3:08 ` Wes Hardaker
1998-11-17 5:38 ` Matt Armstrong
1998-11-17 7:45 ` Yair Friedman
1998-11-17 8:33 ` Steinar Bang
1998-11-17 12:37 ` Per Abrahamsen
1998-11-17 19:01 ` Matt Armstrong
1998-11-18 0:28 ` Lars Magne Ingebrigtsen
1998-11-18 8:16 ` Kai.Grossjohann
1998-11-18 8:36 ` Lars Magne Ingebrigtsen
1998-11-18 8:55 ` Kai.Grossjohann
1998-11-18 13:11 ` Lars Magne Ingebrigtsen
1998-11-18 13:50 ` Jan Vroonhof
1998-11-18 14:02 ` Lars Magne Ingebrigtsen
1998-11-18 18:50 ` Per Abrahamsen
1998-11-19 3:05 ` Lars Magne Ingebrigtsen
1998-11-17 12:37 ` Per Abrahamsen
1998-11-17 14:52 ` Steinar Bang
1998-11-17 17:45 ` Per Abrahamsen
1998-11-18 9:55 ` Steinar Bang
1998-11-18 18:50 ` Per Abrahamsen
1998-11-17 8:39 ` Kai.Grossjohann
1998-11-17 9:59 ` Vladimir Volovich
1998-11-17 12:18 ` Steinar Bang
1998-11-17 13:44 ` Vladimir Volovich
1998-11-17 14:50 ` Steinar Bang
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=vafaf1vgsae.fsf@ramses.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).