Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Misbehaving gnus-gcc-mark-as-read while archiving to current group
Date: Tue, 12 Aug 2014 19:11:41 +0200	[thread overview]
Message-ID: <8761hxk4z6.fsf@debian.uxu> (raw)
In-Reply-To: <84sil1llk8.fsf@gmail.com>

Carlos Pita <carlosjosepita@gmail.com> writes:

> Then you can just say that the summary buffer isn't
> immediately refreshed, which doesn't feel so bad and
> is easier to understand and live with.

The summary buffer isn't refreshed automatically if it
is open and then you do something in the group buffer
that should show in the summary buffer. That's just a
general observation. If you don't have a summary
buffer, and it shows up, but the marks are
inconsistent, then that is either a misunderstanding, a
misconfiguration, or a bug - or a combination :) The
rule of bug reports is, though, that if you think or
suspect it is a bug, you should report it! Sometimes it
isn't a bug, but that's OK.

> I've reported this as a bug a number of days ago, and
> I would like to add the above remark as a followup or
> commentary to the report, but I'm not able to find
> instructions on how to do that.

Good question. There are bug tracking systems where you
can provide additional information - as in, the bug is
a Usenet thread itself, somewhat - but I don't know
what Gnus uses. Since the discussion on gnu.emacs.gnus
is ultra-on-topic (which is great), I assume that the
developers read every single line, so I don't think you
have to worry that this post of yours is lost to them.

-- 
underground experts united

  reply	other threads:[~2014-08-12 17:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 15:38 Carlos Pita
2014-08-05 22:41 ` Emanuel Berg
2014-08-12 16:28   ` Carlos Pita
2014-08-12 17:11     ` Emanuel Berg [this message]
2014-08-12 22:02       ` Carlos Pita
2014-08-12 22:25         ` Emanuel Berg

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=8761hxk4z6.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=info-gnus-english@gnu.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).