Gnus development mailing list
 help / color / mirror / Atom feed
From: Ulf Stegemann <ulf-news@zeitform.de>
To: ding@gnus.org
Subject: Problem with group buffer
Date: Mon, 14 May 2007 08:50:15 +0200	[thread overview]
Message-ID: <zf.upnzm47oq54.fsf@zeitform.de> (raw)

No Gnus v0.7 (14 May 2007)
XEmacs 21.4 (patch 20) "Double Solitaire" [Lucid] (i686-pc-linux, Mule)
of Mon Dec 11 2006

With the latest Gnus CVS version as of today I encounter strange
behavior of the group buffer.  It seems that the buffer does not get
updated upon certain commands.  For example `gnus-group-catchup-current'
(c in the group buffer) has no immediate visible effects (change of
face, number of unread messages).  Furthermore, after catching up a group
in the group buffer I can go back to the group's line (which appears
totally unchanged) and get a "No group on current line" error with any
operation applied to that group (select group etc.).  However, the group
buffer updates correctly upon a `gnus-group-list-groups' (l).

Another strangeness appears with changing of group levels.  Applying
`gnus-group-set-current-level' to any group in the group buffer offers
to change the level (showing the current level correctly) but entering a
number n will always result in the message "Changed level of
/group-name/ from 10 to n".  However, all this has absolutely no effect.
The level of the group is unchanged.

I could imagine that both problems have the same cause and that there
are other oddities just not discovered, yet.  Since these are rather
severe problems I wonder if anyone else has encountered these or if it
may be a local problem with my installation.


Ulf



                 reply	other threads:[~2007-05-14  6:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=zf.upnzm47oq54.fsf@zeitform.de \
    --to=ulf-news@zeitform.de \
    --cc=ding@gnus.org \
    /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).