From: Jeff Senn <senn@maya.com>
Cc: ding@gnus.org, ntemacs-users@cs.washington.edu
Subject: Re: drag-drop bug...
Date: 15 Oct 1999 13:07:51 -0400 [thread overview]
Message-ID: <wkoge0k0wo.fsf@SNIPE.maya.com> (raw)
In-Reply-To: "Dr Francis J. Wright"'s message of "Fri, 15 Oct 1999 15:49:33 +0100"
Dr Francis J. Wright <F.J.Wright@qmw.ac.uk> writes:
> Jeff Senn wrote:
> >
> > So I just experienced a wierd bug in my [GNU Emacs 20.4.1
> > (i386-*-windows95.1111)] (running Windows 95)
...
> >
> > Then I noticed that many of my gnus (pgnus 0.95) buffers were gone!!!
> >
> > Including the *Group* buffer (and I'm sure it didn't run the various
> > hooks associated with killing the buffer)... in this case, no-harm
> > (saved by dribble); I'm glad it wasn't some buffer with an
> > important edit underway...
>
> Here's a guess for someone to shoot down. The drag-drop caused Emacs to
> garbage collect. While it was doing that, it stored the kill-buffer
> commands. When it had finished garbage collecting, it applied the
> stored kill-buffer commands and killed the top so-many buffers. If this
Hm -- possible, I guess -- although it would have been a longer GC
than I have ever seen my emacs do... and it didn't happen near the
drag-drop, it happened later when I attempted to kill the buffer.
...and I'd swear the (original) buffer I was trying to kill was still
on my screen and also _active_ at some point after I typed C-x
C-k...but I can't be entirely certain.
> guess is correct then the moral is just to be patient!
yeah...well...my fingers do get ahead of me sometimes...
--
-Jas
I've got emacs, who needs a stink'n' _mouse_!
next prev parent reply other threads:[~1999-10-15 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-15 13:54 Jeff Senn
1999-10-15 14:49 ` Dr Francis J. Wright
1999-10-15 17:07 ` Jeff Senn [this message]
1999-10-15 17:59 ` Kai Großjohann
1999-10-18 15:15 ` Jeff Senn
1999-10-18 15:23 ` Kai Großjohann
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=wkoge0k0wo.fsf@SNIPE.maya.com \
--to=senn@maya.com \
--cc=ding@gnus.org \
--cc=ntemacs-users@cs.washington.edu \
/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).