Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: info-gnus-english@gnu.org
Subject: Re: does anyone have a workaround for the "Hiding the thread moved us backwards, aborting!" bug yet?
Date: Sun, 23 Sep 2012 08:31:00 -0700	[thread overview]
Message-ID: <86a9wgah8r.fsf@red.stonehenge.com> (raw)
In-Reply-To: <mailman.9473.1348251542.855.info-gnus-english@gnu.org>

>>>>> "Sivaram" == Sivaram Neelakantan <nsivaram.net@gmail.com> writes:

Sivaram> On Fri, Sep 21 2012,Randal L. Schwartz Randal L. Schwartz wrote:
>> it's driving me crazy. :(

Sivaram> We're on a Gnus mailing list, which by definition is where the crazies
Sivaram> congregate (Have you seen normal email clients/MUAs, recently?).  You're not
Sivaram> out of the ordinary, here. :-)

Sivaram> And no, I have no idea of the bug or the resolution.
Sivaram>  sivaram
Sivaram>  -- 

repeat by:

(setq
  gnus-build-sparse-threads 'more
  gnus-thread-hide-subtree t
)

(which is my preferred view)

kill a (folded) thread ahead of a thread that is missing a base
article, so it's sparse.  your cursor will end up at the far right,
instead of on the left.

now kill *that* thread.  BOOM, you get shoved to the end of the buffer
and the error message above.

Before, you'd just get shoved into some weird buffer state that a ^A
would fix.  But at least you wouldn't lose context.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion

  parent reply	other threads:[~2012-09-23 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 19:10 Randal L. Schwartz
2012-09-21 18:18 ` Sivaram Neelakantan
     [not found] ` <mailman.9473.1348251542.855.info-gnus-english@gnu.org>
2012-09-23 15:31   ` Randal L. Schwartz [this message]
2012-12-24 16:09 ` Lars Ingebrigtsen

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=86a9wgah8r.fsf@red.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --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).