From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/59974 Path: news.gmane.org!not-for-mail From: Ulf Stegemann Newsgroups: gmane.emacs.gnus.general Subject: Problem with gnus-group-mark-group Date: Tue, 08 Mar 2005 17:42:04 +0100 Organization: zeitform Internet Dienste Message-ID: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: sea.gmane.org 1110385423 14026 80.91.229.2 (9 Mar 2005 16:23:43 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 9 Mar 2005 16:23:43 +0000 (UTC) Original-X-From: ding-owner+M8515@lists.math.uh.edu Wed Mar 09 17:23:42 2005 Original-Received: from malifon.math.uh.edu ([129.7.128.13] ident=mail) by ciao.gmane.org with esmtp (Exim 4.43) id 1D93tY-0007rx-OD for ding-account@gmane.org; Wed, 09 Mar 2005 17:18:49 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1D93tP-0002tt-00; Wed, 09 Mar 2005 10:18:39 -0600 Original-Received: from util2.math.uh.edu ([129.7.128.23]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1D8hme-0000t6-00 for ding@lists.math.uh.edu; Tue, 08 Mar 2005 10:42:12 -0600 Original-Received: from quimby.gnus.org ([80.91.224.244]) by util2.math.uh.edu with esmtp (Exim 4.30) id 1D8hmZ-0002ZZ-DX for ding@lists.math.uh.edu; Tue, 08 Mar 2005 10:42:07 -0600 Original-Received: from news by quimby.gnus.org with local (Exim 3.35 #1 (Debian)) id 1D8hmY-0004qv-00 for ; Tue, 08 Mar 2005 17:42:06 +0100 Original-To: ding@gnus.org Original-Path: not-for-mail Original-Newsgroups: gnus.ding Original-Lines: 22 Original-NNTP-Posting-Host: host1914.igd.fhg.de Original-X-Trace: quimby.gnus.org 1110300126 18656 146.140.8.122 (8 Mar 2005 16:42:06 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: Tue, 8 Mar 2005 16:42:06 +0000 (UTC) X-Request-PGP: http://ulf.zeitform.de/GnuPG/ulf_stegemann.key.asc X-PGP-KeyID: 8862250A OpenPGP: id=0x8862250A (short key ID); algo=17 (DSA); size=1024 (bits); created=876873600 (1997-10-15); url=http://ulf.zeitform.de/GnuPG/ulf_stegemann.key.asc Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXm27ayglb9+NOPVzIS CgNzQCM+JBPx6MK4RNzbAAACHElEQVR4nFWTMW/bMBCFKRgpVwuq0zX1ojUCwc4xImsuIJBZ XUBiV1pAcX+/7x1l2b4ESMDP7969I22OT9Wuf+VoHk9NXe8XPZflDswh9ajZ8iPLpng79Gud LTvJCt5e+60+raBW8C2lkG7kC+drq5+hq5uYUNosiymKdrev6ppgwm/f/7C3VsaYiophUNEl 51VhkOAwp2ko3U7GFvCG89pHgEndBysZQJYMhzrENN3m2hcPrqJuwjoT6zdMCShwBDfJh7EK aoL4CNCqlUXqTbGSk3pIpkUBqcyFdRlczR0M6wCfmqO98twF3VXxORXzq+sA/CPQgO2/ITgU wegVfJSA1z6RwGSM868bkGObY5xH9EqzP8dA8BdgIRgUhBBmH3RXMG9FKpw414Ck0anC0KOV ynunNcazmwEG3sfS5sZpEOe670mnOol65KYrIAAEgguBtJWDwnlYIIqCdxELm8p5LpcT4CdO tOADktc5dg1nDZ6LmfBIrWWra5M6DQFJE8I0/DGmPAZR54AMow9jTBfDHC0S7ghGqGb6pAsf IpPLAQspO1HpO8yxkqOVl9mToA+B2wunWjDziysrVDA6YzWgZHh4zXEDaw7JVTkuwG2KB1CW bExGDn7fCNJ8B9bioiCzVXk786awmTms7AJfWwEdARBbmWt5UvTmzexJOC6/gF1TBM8g85+D DovL3ICWMTs15vveFJiL7Z7Bf8+bGHgTKJ2GAAAAAElFTkSuQmCC User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.4.17 (linux) Cancel-Lock: sha1:ElJ1InAkJbO38dHGMUXJMU+uat8= X-Spam-Score: -4.9 (----) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu X-MailScanner-From: ding-owner+m8515@lists.math.uh.edu X-MailScanner-To: ding-account@gmane.org Xref: news.gmane.org gmane.emacs.gnus.general:59974 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:59974 XEmacs 21.4 (patch 17) "Jumbo Shrimp" [Lucid] (i686-pc-linux, Mule) No Gnus v0.3 I recently switched form Gnus 5.10.6 to No Gnus 0.3 and encountered a problem when hitting M-g in a summary buffer (gnus-summary-rescan-group) or the group buffer (gnus-group-get-new-news-this-group). Each M-g produces an additional group entry in the group buffer leaving the existing one(s) borked ("no group on current line" when trying to enter). I was able to identify gnus-group-mark-group as responsible for the faulty behavior. The function changed significantly since 5.10.6 and replacing No Gnus' gnus-group-mark-group with the v5.10.6 version apparently fixed the problem. Unfortunately, my lack of time (and sufficient lisp knowledge, probably) let's me hesitate to further investigate this issue. Maybe there's someone out there who knows what the reason for the described behavior is? Ulf