* drag-drop bug...
@ 1999-10-15 13:54 Jeff Senn
1999-10-15 14:49 ` Dr Francis J. Wright
1999-10-15 17:59 ` Kai Großjohann
0 siblings, 2 replies; 6+ messages in thread
From: Jeff Senn @ 1999-10-15 13:54 UTC (permalink / raw)
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...
--
-Jas
----------------------------------------------------------- / / | / \ / /|
Jeff Senn 412-488-2900 voice MAYA Design Group /|/| |-/ o | /-|
Chief Technologist 412-488-2940 fax 2100 Wharton Street / | | |/ |/ |
Head of R&D senn@maya.com Pittsburgh, PA 15203 Taming Complexity
http://www.maya.com/
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: drag-drop bug...
1999-10-15 13:54 drag-drop bug Jeff Senn
@ 1999-10-15 14:49 ` Dr Francis J. Wright
1999-10-15 17:07 ` Jeff Senn
1999-10-15 17:59 ` Kai Großjohann
1 sibling, 1 reply; 6+ messages in thread
From: Dr Francis J. Wright @ 1999-10-15 14:49 UTC (permalink / raw)
Cc: ding, ntemacs-users
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: drag-drop bug...
1999-10-15 14:49 ` Dr Francis J. Wright
@ 1999-10-15 17:07 ` Jeff Senn
0 siblings, 0 replies; 6+ messages in thread
From: Jeff Senn @ 1999-10-15 17:07 UTC (permalink / raw)
Cc: ding, ntemacs-users
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_!
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: drag-drop bug...
1999-10-15 13:54 drag-drop bug Jeff Senn
1999-10-15 14:49 ` Dr Francis J. Wright
@ 1999-10-15 17:59 ` Kai Großjohann
1999-10-18 15:15 ` Jeff Senn
1 sibling, 1 reply; 6+ messages in thread
From: Kai Großjohann @ 1999-10-15 17:59 UTC (permalink / raw)
Jeff Senn <senn@maya.com> writes:
> 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 [...]
Excuse me if I'm completely off the mark here, but C-x C-k is bound to
edit-kbd-macro by default, so it is not surprising that something
surprising happens... C-x k is kill-buffer.
Hm. Assuming that this is just a typo, another alternative could be
that the current buffer was switched from under your fingers, just as
you were hitting C-x k. Hm. Can you try to watch the default buffer
offered to you closely?
kai
--
Life is hard and then you die.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: drag-drop bug...
1999-10-15 17:59 ` Kai Großjohann
@ 1999-10-18 15:15 ` Jeff Senn
1999-10-18 15:23 ` Kai Großjohann
0 siblings, 1 reply; 6+ messages in thread
From: Jeff Senn @ 1999-10-18 15:15 UTC (permalink / raw)
Cc: ding
Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> Jeff Senn <senn@maya.com> writes:
>
> > 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 [...]
>
> Excuse me if I'm completely off the mark here, but C-x C-k is bound to
> edit-kbd-macro by default, so it is not surprising that something
> surprising happens... C-x k is kill-buffer.
>
> Hm. Assuming that this is just a typo, another alternative could be
> that the current buffer was switched from under your fingers, just as
> you were hitting C-x k. Hm. Can you try to watch the default buffer
> offered to you closely?
yes - yes. typo. I meant C-x k.
As I said, I can't seem to replicate.
I just wonder whether it might not be nice if the *Group* buffer had a
kill hook so in my typing frenzy I don't accidentaly blow it
away... it does leave gnus in a rather bad state....
--
-Jas
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: drag-drop bug...
1999-10-18 15:15 ` Jeff Senn
@ 1999-10-18 15:23 ` Kai Großjohann
0 siblings, 0 replies; 6+ messages in thread
From: Kai Großjohann @ 1999-10-18 15:23 UTC (permalink / raw)
Cc: ding
Jeff Senn <senn@maya.com> writes:
> I just wonder whether it might not be nice if the *Group* buffer had a
> kill hook so in my typing frenzy I don't accidentaly blow it
> away... it does leave gnus in a rather bad state....
You can do that yourself, see the variable kill-buffer-query-functions.
kai
--
Life is hard and then you die.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1999-10-18 15:23 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-10-15 13:54 drag-drop bug Jeff Senn
1999-10-15 14:49 ` Dr Francis J. Wright
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
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).