Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Using 'd' in Summary buffer produces surprising results (sometimes)
Date: Mon, 01 Jul 2013 08:34:58 -0400	[thread overview]
Message-ID: <87wqpajw5p.fsf@lifelogs.com> (raw)
In-Reply-To: <87a9m8co7f.fsf@gmail.com>

On Sat, 29 Jun 2013 22:44:04 -0400 Nick Dokos <ndokos@gmail.com> wrote: 

ND> If I try to 'd' my way through a group, much of the time I get what I
ND> expect: the message is marked 'r' and the next message is shown.

ND> However, sometimes a 'd' will take me back to a previous message
ND> (usually, perhaps always, in the thread I'm reading - I don't remember
ND> any cases where it has taken me to a message in a previous thread, but
ND> I'm not sure), one that I've already read. Successive 'd's will step
ND> through all the intermediate messages until I get to a new message,
ND> where another 'd' will take me back to the same previous message as
ND> above and the whole process is repeated a few times. It usually stops
ND> when I get to the first message of the next thread. Then later on it
ND> might start again with a message in a different thread.

ND> Has anybody seen this behavior? Anybody know what causes it? Is there
ND> some way to avoid it? It does not always happen but it happens often
ND> enough to be annoying. If anybody has any suggestions about debugging
ND> this or about more information I can provide, I'd appreciate the help.
ND> The main problem is that I don't know when this will happen: next time
ND> it happens, I plan to edebug through gnus-summary-mark-as-read-forward,
ND> but I'm wondering if there is a better way to go.

I've never seen this, myself.  If possible, try to replicate it with a
bare .emacs.

Ted




  reply	other threads:[~2013-07-01 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30  2:44 Nick Dokos
2013-07-01 12:34 ` Ted Zlatanov [this message]
2013-07-09 15:45   ` Nick Dokos

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=87wqpajw5p.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).