From: John Wiegley <johnw@gnu.org>
Subject: Re: Question about copy-region-as-kill
Date: Sat, 06 Apr 2002 13:38:39 -0700 [thread overview]
Message-ID: <87k7rkmuk0.fsf@alice.dynodns.net> (raw)
In-Reply-To: <200204061732.g36HWSb19584@aztec.santafe.edu> (Richard Stallman's message of "Sat, 6 Apr 2002 10:32:28 -0700 (MST)")
>>>>> On Sat Apr 6, RMS writes:
> Text properties are part of the text. Aside from special cases
> there is no reason not to copy them.
Yet there DO exist reasons to avoid doing so, which at present force
people to resort to overlays. I think there is sufficient evidence to
show that not copying text properties in certain buffers is a good
thing.
We're talking about such a small change here (see below). I can't
believe there is a valid philosophical reason to _deny_ such
configurability, forcing an entirely different paradigm (overlays)
just to avoid the copy.
And whether these are stripped at kill or yank, I don't care. I just
don't want read-only copied around when I kill text from Eshell, and
then yank it into an e-mail message!
John
----------------------------------------------------------------------
(defvar copy-properties-on-kill t)
(make-variable-buffer-local 'copy-properties-on-kill))
(defun copy-region-as-kill (beg end)
"Save the region as if killed, but don't kill it.
In Transient Mark mode, deactivate the mark.
If `interprogram-cut-function' is non-nil, also save the text for a window
system cut and paste."
(interactive "r")
(let ((str (if copy-properties-on-kill
(buffer-substring beg end)
(buffer-substring-no-properties beg end))))
(if (eq last-command 'kill-region)
(kill-append str (< end beg))
(kill-new str)))
(if transient-mark-mode
(setq deactivate-mark t))
nil)
next prev parent reply other threads:[~2002-04-06 20:38 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 23:23 Question about copy-region-as-kill John Wiegley
2002-04-05 6:02 ` Richard Stallman
2002-04-05 21:39 ` John Wiegley
2002-04-06 7:19 ` Eli Zaretskii
2002-04-06 8:21 ` John Wiegley
2002-04-06 10:29 ` Karl Eichwalder
2002-04-06 17:46 ` Kai Großjohann
2002-04-06 18:05 ` Alex Schroeder
2002-04-07 18:50 ` Richard Stallman
2002-04-08 1:23 ` Miles Bader
2002-04-06 18:30 ` Karl Eichwalder
2002-04-06 23:03 ` Alan Shutko
2002-04-07 7:42 ` Karl Eichwalder
2002-04-08 15:53 ` Stefan Monnier
2002-04-08 21:21 ` John Wiegley
2002-04-09 9:31 ` Kim F. Storm
2002-04-09 11:03 ` Eli Zaretskii
2002-04-09 10:23 ` Miles Bader
2002-04-09 13:05 ` Kim F. Storm
2002-04-09 13:24 ` Miles Bader
2002-04-09 14:42 ` Eli Zaretskii
2002-04-10 14:24 ` Richard Stallman
2002-04-10 14:24 ` Richard Stallman
2002-04-10 16:27 ` Kim F. Storm
2002-04-11 14:53 ` Richard Stallman
2002-04-11 16:27 ` Kim F. Storm
2002-04-12 19:49 ` Richard Stallman
2002-04-12 10:36 ` Francesco Potorti`
2002-04-09 15:26 ` Per Abrahamsen
2002-04-09 21:28 ` John Wiegley
2002-04-07 3:56 ` Tak Ota
2002-04-06 15:05 ` Andreas Schwab
2002-04-06 17:32 ` Richard Stallman
2002-04-06 20:38 ` John Wiegley [this message]
2002-04-06 23:03 ` Alex Schroeder
2002-04-07 0:12 ` Colin Walters
2002-04-07 0:56 ` Miles Bader
2002-04-07 2:53 ` John Wiegley
2002-04-07 4:44 ` Colin Walters
2002-04-07 4:58 ` Miles Bader
2002-04-07 5:32 ` Colin Walters
2002-04-07 6:53 ` Miles Bader
2002-04-07 7:46 ` Colin Walters
2002-04-07 8:18 ` Alex Schroeder
2002-04-07 12:20 ` Miles Bader
2002-04-08 3:09 ` Colin Walters
2002-04-08 6:18 ` Miles Bader
2002-04-09 22:04 ` Colin Walters
2002-04-10 20:17 ` Richard Stallman
2002-04-09 12:07 ` Richard Stallman
2002-04-09 22:12 ` Colin Walters
2002-04-07 6:36 ` John Wiegley
2002-04-07 6:55 ` Colin Walters
2002-04-07 23:42 ` Richard Stallman
2002-04-08 3:14 ` Colin Walters
2002-04-09 12:07 ` Richard Stallman
2002-04-09 22:06 ` Colin Walters
2002-04-07 4:41 ` Colin Walters
2002-04-07 4:58 ` Miles Bader
2002-04-07 5:43 ` Colin Walters
2002-04-07 10:52 ` Kai Großjohann
2002-04-06 17:43 ` 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=87k7rkmuk0.fsf@alice.dynodns.net \
--to=johnw@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.