From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/67261 Path: news.gmane.org!not-for-mail From: Vitaly Mayatskikh Newsgroups: gmane.emacs.gnus.general Subject: Re: gnus and imap Date: Fri, 22 Aug 2008 14:30:14 +0200 Message-ID: References: <877iabwtjx.fsf@randomsample.de> <87abf51c4m.fsf@marauder.physik.uni-ulm.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1219408261 26769 80.91.229.12 (22 Aug 2008 12:31:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 22 Aug 2008 12:31:01 +0000 (UTC) Cc: ding@gnus.org To: Vitaly Mayatskikh Original-X-From: ding-owner+M15712@lists.math.uh.edu Fri Aug 22 14:31:54 2008 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1KWVnt-0003Oy-8y for ding-account@gmane.org; Fri, 22 Aug 2008 14:31:45 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1KWVmj-0008Bq-Ae; Fri, 22 Aug 2008 07:30:33 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1KWVmh-0008BU-DH for ding@lists.math.uh.edu; Fri, 22 Aug 2008 07:30:31 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1KWVmc-0004pI-CH for ding@lists.math.uh.edu; Fri, 22 Aug 2008 07:30:31 -0500 Original-Received: from fg-out-1718.google.com ([72.14.220.152]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1KWVmd-00066N-00 for ; Fri, 22 Aug 2008 14:30:27 +0200 Original-Received: by fg-out-1718.google.com with SMTP id 16so358515fgg.23 for ; Fri, 22 Aug 2008 05:30:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:subject:references :date:in-reply-to:message-id:user-agent:mime-version:content-type; bh=ZRUANfxV1h1HoASE5RrL8EHYN796JeKLH+GiCzBAp9M=; b=QY7Mdwi8Lf5OmBtfdS0BT/j9GFTnqOIKG1IesBIq2aswcGwAUwIzIR9XXIfbiY+oc+ HeG7iOwK7EH7THEY+4sRcWFn3LhJRHw5xUvbQqAI2XPkcwcWjAhMphPZgC/RkSuJgodo nUFNVG/cU5D24wXNtypvu9WxEq08WnLZQiSDM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=HsBojE8D+isP7Th6zzJmybreWkjndZotKLZrActrB4vtLc+dLQOF5r8DSti/OevGPf 1ux1GQ99sEHSyS1rkBJS1AUVJigYxO46jhganZtcitnITlWjoscwXCmAKZz68M5gHr5q sXJ8KIVgdbrBly+lJvC1CxJy8Sta6/aFbfaDc= Original-Received: by 10.86.79.19 with SMTP id c19mr774409fgb.67.1219408224859; Fri, 22 Aug 2008 05:30:24 -0700 (PDT) Original-Received: from gravicappa.englab.brq.redhat.com ( [62.40.79.66]) by mx.google.com with ESMTPS id d6sm1230560fga.2.2008.08.22.05.30.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 22 Aug 2008 05:30:17 -0700 (PDT) In-Reply-To: <87abf51c4m.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 22 Aug 2008 14:13:13 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-Spam-Score: 0.0 (/) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:67261 Archived-At: Reiner Steib writes: >> Sounds good to me. However, before you do too much work on this, and >> since this is a change in the Gnus internals, maybe someone who is more >> familiar with the code base (Reiner?) can say if this is desirable to >> do. > > Unfortunately I'm not too familiar with the backend code and I'm quite > short of free time ATM (and I'll be on holiday during most of > September). I'll be glad if you and/or other developers find time to > review and test Vitaly's patches. > > Additionally, we need to decide how to continue Gnus development, so > I'm not sure if we want to install back end changes at this time. Well, these changes will simply break everything except nnimap, so it can't be committed at the moment. Another idea is to fix active info in Gnus itself and to make it able to handle ranges of article numbers, not only one range. It doesn't require any changes in backends (unless some of them want to pass ranges of articles, like nnimap). I'm working on it currently. I hope, it will solve many problems with articles numbers. -- wbr, Vitaly