From: "Dr Francis J. Wright" <F.J.Wright@qmw.ac.uk>
Cc: ding@gnus.org, ntemacs-users@cs.washington.edu
Subject: Re: drag-drop bug...
Date: Fri, 15 Oct 1999 15:49:33 +0100 [thread overview]
Message-ID: <38073EFD.E81D6224@Maths.QMW.ac.uk> (raw)
In-Reply-To: <wkk8ooohjy.fsf@SNIPE.maya.com>
Jeff Senn wrote:
>
> So I just experienced a wierd bug in my [GNU Emacs 20.4.1
> (i386-*-windows95.1111)] (running Windows 95)
>
> I don't have time to track it down at the moment, but maybe if I
> mention it, someone will notice when it happens again and catch it.
> (I can't seem to replicate it at the moment)
>
> I drag-dropped several files onto the emacs window (which worked),
> then I tried to kill (C-x C-k) the buffer that the cursor was
> in....and it was odd (violated all the Emacs expectations programmed
> in my spine and fingers) the buffer just sat there. Possibly I
> repeated the kill a couple of times. Something I did finally killed
> the buffer.
>
> 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
guess is correct then the moral is just to be patient!
Francis
next prev parent reply other threads:[~1999-10-15 14:49 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 [this message]
1999-10-15 17:07 ` Jeff Senn
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=38073EFD.E81D6224@Maths.QMW.ac.uk \
--to=f.j.wright@qmw.ac.uk \
--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).