From: David Hedbor <david@hedbor.org>
Subject: BUG: Old problem resurfaced in Oort
Date: 12 Jan 2001 09:36:55 -0800 [thread overview]
Message-ID: <m3ae8wlljc.fsf@pokey.home.hedbor.org> (raw)
I updated to Oort a short time ago and noticed that the old "answer
the wrong message" bug is back. It's the problem where you enter a
large group (many ticked in my case). I press 'n' and the screen
splits. After the split, the cursor is on the wrong message so any
message related functions (R, F and so on) works on the wrong email.
Previously this was a bug isolated to XEmacs, which I'm still
using. Let me know if there's anything I can do to help the debugging
this time.
- david
P.S. I _think_ the previous fix was between r 5.7 and r 5.8 of
gnus-win.el but I'm not sure.
--
[ Below is a random fortune, which is unrelated to the above message. ]
Remembering is for those who have forgotten.
-- Chinese proverb
next reply other threads:[~2001-01-12 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 17:36 David Hedbor [this message]
2001-01-12 22:24 ` ShengHuo ZHU
2001-01-15 7:57 ` David Hedbor
2001-01-16 17:13 ` Anders Odberg
2001-01-30 18:16 ` Weird topics bug James Felix Black
2001-02-13 4:20 ` ShengHuo ZHU
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=m3ae8wlljc.fsf@pokey.home.hedbor.org \
--to=david@hedbor.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).