From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: drag-drop bug...
Date: 15 Oct 1999 19:59:37 +0200 [thread overview]
Message-ID: <vafbta05wty.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Jeff Senn's message of "15 Oct 1999 09:54:41 -0400"
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.
next prev parent reply other threads:[~1999-10-15 17:59 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
1999-10-15 17:59 ` Kai Großjohann [this message]
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=vafbta05wty.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).