From: Dan Jacobson <jidanni@dman.ddts.net>
Cc: debian-emacsen@lists.debian.org
Subject: C-k and scolding
Date: Fri, 04 Apr 2003 04:04:04 +0800 [thread overview]
Message-ID: <87u1dgjb6h.fsf@jidanni.org> (raw)
In-Reply-To: <87znn8tdn5.fsf@pfaff.Stanford.EDU> (Ben Pfaff's message of "02 Apr 2003 20:21:02 -0800")
>> Hi all. I ran into a slight difficulty. In emacs, i realise you can
>> do C-w and C-SPC to cut tetxt from a buffer which can then be yanked
>> into a buffer with C-Y. However, if you are reviewing a buffer that
>> is read only, you cannot grab the text out in this way.
Ben> Actually, you can. It will beep at you and the text will not be
Ben> removed from the buffer, but it will still go into the kill ring.
This brings up the interesting concept of here we are having emacs
scolding us for doing something improper while at the same time if we
were to do it the proper way, it would take more keystrokes.
Moms wonder why kids just don't listen these days, etc. Youngsters
just don't seem to have respect for the law, etc.
>> So is there a command in emacs which allows you to copy a block
>> rather than cut it. Thanks. Mat.
Ben> Use M-w instead of C-w.
Take the case of a single C-k. To do this the proper way in a
read-only buffer etc. one needs to set a mark, go the end of line, and
hit M-w. Much more trouble than just a C-k while accepting the
sadomasochistic beep.
So there should be a way, just as easy as one or more C-k's, to do
what C-k does (as far as adding to the kill ring), without getting
beeped, nor without changing the file.
P.S. be sure to followup to bug-gnu-emacs@gnu.org not
debian-emacsen@lists.debian.org
--
http://jidanni.org/ Taiwan(04)25854780
next parent reply other threads:[~2003-04-03 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <73388857A695D31197EF00508B08F2980A00EEEC@ntmsg0131.corpmail.telstra.com.au>
[not found] ` <87znn8tdn5.fsf@pfaff.Stanford.EDU>
2003-04-03 20:04 ` Dan Jacobson [this message]
2003-04-04 0:18 ` C-k and scolding Ben Pfaff
2003-04-14 21:04 ` Bruce Kroeze
2003-04-17 1:14 ` decriminalize C-k in read-only buffers! Dan Jacobson
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87u1dgjb6h.fsf@jidanni.org \
--to=jidanni@dman.ddts.net \
--cc=debian-emacsen@lists.debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).