On Tue, 19 Nov 2002 11:49:33 +0100 (Romance Standard Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote:
> On Fri, 15 Nov 2002 15:31:33 +0100 Xavier Nodet <[EMAIL PROTECTED]> wrote: > XN> Opening a group > XN> --------------- > XN> > XN> When one opens a group, the current behavior is to download *both* > XN> headers and then text for *all* messages. Again, this may be correct for > XN> a local server which the user controls, but not for the general case. > Hmm, so cclient even doesn't use XOVER? This would be dumb... There is some code in cclient that uses XOVER (in functions nntp_overview and nntp_sort_loadcache) but we never get into those functions. > The logic here is the same for all folders: we only ask for the > messages we must show on screen. But maybe it decided to download > everything because we're asking for flags? This would need to be > checked. The full text is downloaded because we need the rfc822 size. See mail_fetch_structure around line 1205. > XN> Actually, this is because c-client (as we use it, at least) insists that > XN> the exact size of the message must be known even if we are only > XN> interested in the headers. > Yes, we had the same problem with POP... > XN> I have a very simple patch, but this prevents to ever get a correct > XN> display for the size (actually, what is displayed is the size of the > XN> headers). > But with POP there is LIST which can be used to get the size -- and I'm > sure there are NNTP extensions allowing to do it as well. So, again, we > should patch cclient to use them. I guess that the problem comes from the fact that some NNTP specific functions are not called. But I do not know if this is because of a problem in c-client, or in the way we use it. Is there some documentation for c-client ? > XN> Reading a group > XN> --------------- > XN> > XN> The problem here is that the only operation that c-client handles on > XN> messages in NNTP folders is to delete a message. So when a group has > XN> been opened, new messages do not become read when the user selects them, > XN> and the only way to get rid of read messages is to answer Yes to the > XN> question asked when leaving the group: 'Do you want to mark *all* > XN> messages as read'. This actually marks them deleted, by the way. > Yes. This is not that unusual for news clients, mind you: for example, > slrn marks the read messages with 'D' flag too (I never really paid > attention to this but now I've just realized that this 'D' can't stand for > anything else but "Deleted"). OTOH, we could mask this difference at GUI > level. But this is not too important, and I guess it could be quite complicated to have some different behaviour across forlders. What is more important is that we must be able to actually do something with each message, be it 'Delete' or 'Mark unread'. But c-client somehow prevents this, and we trust it. This is the problem... Look at the beginning of MailFolderCC::SetSequenceFlag. > XN> The 'Size' column in the folder list should display the size of the > XN> messages in number of lines. My understanding is that this was planned > XN> as such, but the information is not there: while the headers of the > XN> message actually have the information, it is not available in any data > XN> structure that c-client and/or Mahogany handle. > cclient size struct does have lines field but I've never seen anything but > 0 (meaning "unknown") in it. I would have thought that it is used for NNTP > and am surprized that this is not the case. Again, the answer is in cclient > code... This seems to be in nntp_parse_overview, but again this function is never called. > XN> PS: the only thing that XNews does not handle correctly is the > XN> 'Reply-by-mail' feature > Mahogany doesn't handle it at all... There is a bug report (which I > created myself) about it though. Message -> Reply -> Reply to sender ? > XN> but if we do not eat our own food, things will not evolve... > You're right, of course. I know that Mahogany improved dramatically > (especially under Windows) since I started to use it as my only mail > client. The trouble is that slrn has (very good) scoring support and I can > hardly imagine reading news without it. But maybe I should try :-) I think so... At least, this is the only correct thing to do if you want it to evolve. But you already know it, and I'm sure you have enough work with the mail part alone... BTW, I thought that there was some support for scoring in M... And we need filters... > Anyhow, knowing what we have to fix is a good first step -- thanks for > looking at this and writing this report! You're welcome. -- Xavier Nodet "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759. ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
